ummm, just had an idea come to me …. on the super os/9 disk, when running in the os/9 environment, there are two programs in the cmds folder called cbmwrite and cbmread. I used cdmwrite to write the 0s9.d8d9 module file out onto the native part of the CBM disk which can be read on the superpet using the waterloo micro editor. I bet cbmread does the opposite …. will try it to see if i can write the files out of the os/9 environment and then use cbmread to put them back in having copied them onto an 8050 format disk - all in vice. Andy > On 23 Jun 2018, at 19:47, Andy Grady <grada719@aol.com> wrote: > > >> Maybe the OS/9 code cannot handle that it needs to access drive 8 and >> 10, instead of the probably more common 8 and 9? > > Yes, OS/9 expects unit 8 and unit 9 …. i finally managed to perform a directory listing on disk10 (8250) using the waterloo microEditor (took several attempts) but as the os/9 files are contained in a ‘rel’ file, I don’t know how to decode it.. > > I have a few os/9 programs in a large ‘rel’ file that it seems can only be read on an 8250 (confirmed in Vice) … I only have an 8050 so was hoping could use VICE to transfer across to that format. A ram disk was another thought and then switch drive types etc. > > Thank you for replying…. > > > > >> On 23 Jun 2018, at 16:53, Rhialto <rhialto@falu.nl> wrote: >> >> On Sat 23 Jun 2018 at 01:24:20 -0700, AndyG wrote: >>> Hi all >>> >>> Wondered if someone can help me out here. I am not able to to run Vice in >>> Superpet mode with 2 drive units 8050 and 8250 .... VICE only allows unit 8 >>> & 9 which is drive 0 and drive 1 ..... on a 8050 for example. >>> unit 10 & 11 are not enabled in VICE. >> >> Due to some internal limitations, a dual drive takes up 2 device >> numbers, so the first 8050 would be at device 8 and also make number 9 >> unavailable. The second 8050 (or 8250) would be device 10 and make 11 >> unavailable. That is because internally VICE only knows about 4 floppy >> images. >> >> The gtk3 settings windows in the current svn version doesn't seem to >> represent this 100% correctly yet, I see now that I'm trying that. >> I'm pretty sure this is shown correctly (but possibly somewhat >> confusingly) in the menu settings in older releases. >> >>> I want to run Super OS/9 with this configuration also - i have the relevant >>> os9.d8d9.mod module to enable multi unit capability. >>> >>> I can have one or the other but not both .... any ideas or is this a >>> limitation of Vice ? >> >> Maybe the OS/9 code cannot handle that it needs to access drive 8 and >> 10, instead of the probably more common 8 and 9? >> >>> Also, I have been working in OS/9 - on my real unit, I can create a ram disk >>> by issuing the command format /dram without any issues. in VICE when you >>> issue a Format /dram command from the os9: prompt it goes through the >>> formatting motions until it asks for the disk name ... after that it just >>> hangs. Any ideas ? >> >> There might be a bug in the 6809 code, who knows. It is only lightly >> tested, really. I briefly tried OS/9, I think, and saw it didn't crash, >> but no more. In particular the 6809 is not cycle-exact; maybe that would >> be a problem? >> >>> Cheers >>> Andy >> -Olaf. >> -- >> ___ Olaf 'Rhialto' Seibert -- Wayland: Those who don't understand X >> \X/ rhialto/at/falu.nl -- are condemned to reinvent it. Poorly. > >Received on 2018-06-23 22:00:04
Archive generated by hypermail 2.2.0.