Hi,
Does anyone remember what key should be pressed to start NitrOS-9L2 using the dual boot image?
Apparently 'Shift' prevents both systems to be loaded ...
thx in advance
pere
The MOOH memory & SPI board
Re: The MOOH memory & SPI board
I forgot too, but tracing startup, it's BREAK.
Re: The MOOH memory & SPI board
right
thanks a lot!
pere
thanks a lot!
pere
Re: The MOOH memory & SPI board
Once started this OS9L2 version from the sdcard emulated by the file "sdcard.img", issuing
free /DD the result is
15,300 sectors --> 3,916,800 bytes
12,400 sectors free
Well now it would be very interesting if we could format a new disquette somewhere
I haven't found any way to access the drives /d0 /d1 /d2 attaching empty virtual files using XRoar
The Drivewire server is started and works well when emulating a plain D64, not sure if I could
use any file from the DW4 server and read/write to it from the OS9L2 already started from the sdcard ...
Issuing 'mdir' I can see there SD0, DD, D0, D1, D2
But no W0, W1 or Wn that probably could be used for Drivewire ...
Any idea/hint will be very appreciated!
cheers!
pere
free /DD the result is
15,300 sectors --> 3,916,800 bytes
12,400 sectors free
Well now it would be very interesting if we could format a new disquette somewhere
I haven't found any way to access the drives /d0 /d1 /d2 attaching empty virtual files using XRoar
The Drivewire server is started and works well when emulating a plain D64, not sure if I could
use any file from the DW4 server and read/write to it from the OS9L2 already started from the sdcard ...
Issuing 'mdir' I can see there SD0, DD, D0, D1, D2
But no W0, W1 or Wn that probably could be used for Drivewire ...
Any idea/hint will be very appreciated!
cheers!
pere
Re: The MOOH memory & SPI board
I have been testing the other 'way' to start NitrOS-9L2 on the Dragon, that's to say using the file named
"NOS9_6809_L2_v030300_MOOH_becker.dsk" that has to be put in slot #0 on the Drivewire4 Server
and the binary: "kernel_becker.bin" to be run while calling xroar.
The result is almost the same than using the sdcard.img
The virtual file mounted in slot#0 of DW4 is considered the drive /DD
In this case I have been able to mount disks in slots #1 and #2 because I saw, using the command mdir,
that the drivers X1 and X2 were in memory.
I put an empty .VDK disk (360k) in slot #1
When I issued format /X1 I received a message saying that the hard disk in X1 was going to be formatted
with more than 15,000 sectors, so I stopped/exited the command
Next try has been putting the Tandy OS9Level II disk in slot #2
Then a did "load /x1/cmds/format" to have it in memory
And finally format /X1 but again the system said that I was going to format a hard disk (Y/N)
Ended the command and I scratched my head ... How could we 'enable' the standard drives to be used, say drive 1 and drive 2?
There is something related called D0, D1 and D2 but all of them are disabled
Any magician has the clue or any idea how to use them?
thanks beforehand
pere
"NOS9_6809_L2_v030300_MOOH_becker.dsk" that has to be put in slot #0 on the Drivewire4 Server
and the binary: "kernel_becker.bin" to be run while calling xroar.
The result is almost the same than using the sdcard.img
The virtual file mounted in slot#0 of DW4 is considered the drive /DD
In this case I have been able to mount disks in slots #1 and #2 because I saw, using the command mdir,
that the drivers X1 and X2 were in memory.
I put an empty .VDK disk (360k) in slot #1
When I issued format /X1 I received a message saying that the hard disk in X1 was going to be formatted
with more than 15,000 sectors, so I stopped/exited the command
Next try has been putting the Tandy OS9Level II disk in slot #2
Then a did "load /x1/cmds/format" to have it in memory
And finally format /X1 but again the system said that I was going to format a hard disk (Y/N)
Ended the command and I scratched my head ... How could we 'enable' the standard drives to be used, say drive 1 and drive 2?
There is something related called D0, D1 and D2 but all of them are disabled
Any magician has the clue or any idea how to use them?
thanks beforehand
pere
Re: The MOOH memory & SPI board
I don't play much with OS-9, but out of interest, how are you providing the disk interface? Is DragonDOS in a particular MPI slot, and does the NitrOS-9 build you're using need to know that up front?
Re: The MOOH memory & SPI board
The way it starts is the recommended by Tormod Volden, the bat file is that one:
The becker cart ensures connection to the Drivewire server where we have put the file containing the rest of the NitrOS-9L2
in slot #0. The filename is "NOS9_6809_L2_v030300_MOOH_becker.dsk"
The binary file that is executed in the bat file with run"kernel_becker.bin" just loads the kernel of OS9L2 and
as it does this via DW4 there is no DOS system enabled.
I was expecting that starting it, even with DW4, the disk drives (D0,D1,D2) would be enabled, but this is not the case
The only drive enabled is in fact the hard disk at slot #0 in the DW4 server as /DD!
I have tried to add to the bat file a DOS (EH4.1 and DP5.0) but in both cases the loading of the NOS9L2 failed almost at the beginning ...
Adding an MPI and putting the DOS in slot #3 and MOOH in slot #0 doesn't work either
I was hopping to use floppy disks to help testing other 2Mb modules
cheers!
pere
Code: Select all
xroar -default-machine dragon64 -machine-cpu 6309 -cart mooh -cart-becker -run kernel_becker.binin slot #0. The filename is "NOS9_6809_L2_v030300_MOOH_becker.dsk"
The binary file that is executed in the bat file with run"kernel_becker.bin" just loads the kernel of OS9L2 and
as it does this via DW4 there is no DOS system enabled.
I was expecting that starting it, even with DW4, the disk drives (D0,D1,D2) would be enabled, but this is not the case
The only drive enabled is in fact the hard disk at slot #0 in the DW4 server as /DD!
I have tried to add to the bat file a DOS (EH4.1 and DP5.0) but in both cases the loading of the NOS9L2 failed almost at the beginning ...
Adding an MPI and putting the DOS in slot #3 and MOOH in slot #0 doesn't work either
I was hopping to use floppy disks to help testing other 2Mb modules
cheers!
pere