NitrOS-9 on Dragon 32 (unmodded)
NitrOS-9 on Dragon 32 (unmodded)
Not awful amounts of memory left for applications though, mfree reports 1+27 pages.
(The reason the screen is b/w is because my S-video output is still WIP.)
Re: NitrOS-9 on Dragon 32 (unmodded)
Hah, brilliant. So is there any useful stuff you can get done with what's left?
ISTR OS-9 mostly putting its stuff at the top of RAM, so that must have taken some juggling.
ISTR OS-9 mostly putting its stuff at the top of RAM, so that must have taken some juggling.
Re: NitrOS-9 on Dragon 32 (unmodded)
Well, since I am involved in NitrOS-9 maintenance/development it is already useful for me to be able to boot up on real hardware and run a few system tools, and to test DriveWire and other things that cannot be fully tested in an emulator. I can imagine some fun things like remote terminal server should be possible. But I don't know yet of any useful applications that fit. If "useful" is valid in this context
It should be possible to optimize NitrOS-9 to leave a bit more free space. For instance are some boot and init modules stuck in memory after booting. And of course having some of it resident on a ROM cartridge would help a lot.
In fact there was not much juggling needed, basically a one-liner change to load the boot track below 32K. It only maps memory up to the boot track anyway. I also changed the boot screen VDU location from $8000 to $0400 so that instead of watching the ROM, I can see the guts of NitrOS-9 while it is booting.
[EDIT: added disk image and updated patch]
It should be possible to optimize NitrOS-9 to leave a bit more free space. For instance are some boot and init modules stuck in memory after booting. And of course having some of it resident on a ROM cartridge would help a lot.
In fact there was not much juggling needed, basically a one-liner change to load the boot track below 32K. It only maps memory up to the boot track anyway. I also changed the boot screen VDU location from $8000 to $0400 so that instead of watching the ROM, I can see the guts of NitrOS-9 while it is booting.
[EDIT: added disk image and updated patch]
- Attachments
-
- nitros9-d32.diff.zip
- (999 Bytes) Downloaded 448 times
-
- nos9d32dw.zip
- contains nos96809l1v030209d32_dw.dsk
- (182.85 KiB) Downloaded 439 times
Last edited by tormod on Sat Mar 15, 2014 12:01 pm, edited 2 times in total.
Re: NitrOS-9 on Dragon 32 (unmodded)
Hahaha Cool
Also should be useful for testing the 80 column board OS9 drivers Can't use an emulator for that.
I believe that using an 80 column board you can get a couple more free pages, since the VDG memory is freed.
You still won't be able to run basic09, but at least the format command should work.
And I thought memory was tight with NitrOS9 and 64K!
Also should be useful for testing the 80 column board OS9 drivers Can't use an emulator for that.
I believe that using an 80 column board you can get a couple more free pages, since the VDG memory is freed.
You still won't be able to run basic09, but at least the format command should work.
And I thought memory was tight with NitrOS9 and 64K!
-
- Posts: 45
- Joined: Tue Jul 23, 2013 3:26 pm
Re: NitrOS-9 on Dragon 32 (unmodded)
a stock dragon 32 ? It says Dragon 64 on boot screen
Re: NitrOS-9 on Dragon 32 (unmodded)
Yes, stock. Blame the poor NitrOS-9 hardware detection It is actually the coco2 build (which defines the module/driver selection), with the d64 port flag set (which defines the Dragon keyboard translation and not much else). So after applying the patch, run "make dsk PORTS=coco2".
-
- Posts: 45
- Joined: Tue Jul 23, 2013 3:26 pm
Re: NitrOS-9 on Dragon 32 (unmodded)
This is cool but I'm afraind there isn't much ram for anything can you format a disk ?
The dragon 64 message is hard coded in the SysGo I guess. Need to create a specific one for dragon32.
The dragon 64 message is hard coded in the SysGo I guess. Need to create a specific one for dragon32.
Re: NitrOS-9 on Dragon 32 (unmodded)
Well, the NitrOS-9 format command is 4KB of code (that is half the size of the entire HDBDOS...) and needs a 11KB data segment, so that is not the easiest of tasks.
The displayed machine name when sysgo is running comes from init.asm. I am not planning an official d32 port yet though, unless by popular demand
The displayed machine name when sysgo is running comes from init.asm. I am not planning an official d32 port yet though, unless by popular demand