archive.worldofdragon.org

whoa, interesting stuff. Only a couple of days ago I managed to do a build of gcc-6809 so I may well try building this for my kit.

This is my hacked together build of a Drivewire enabled NitrosOS9 build for a D64 which pulls in the Dragon disk controller rather than the CoCo one. This is useful for transferring individual files (as opposed to making complete disk copies) from/to floppy disks and Drivewire. Thanks to Ken for poi...

Here are the disk images for the OS9 Newsgroup & PD Library I mentioned plus a couple of other bits I found lying around.

The Becker port address was the other thought that cross my mind during this process because it's not entirely clear to me how all this is managed. I thought the default address was $FF41, which moved to $FF50 when a DOS cartridge was enabled however obviously the software has to know about this as ...

On this point raised earlier by Pere: I have the file "nos9v303_d64COHR_becker.dsk" mounted as Disk0 in DriveWire Then I start XRoar without DDOS or with DDOS11C When I enter DLOAD"DOS" The screen shows the message "NITROS9 BOOT" But nothing happens on the screen, it simply hangs the computer. But ....

Hi Pere,

No rush at all.. I need to start having a play with some of the cross compilation/assembler tools, I can imagine it makes life significantly easier than being restricted to the fairly basic editing capabilities available on the old machine itself.

Cheers,

Jon.

Thanks Ken, I will have a play and see what I can break...

Question for Ken maybe... I was looking to have a play customising some Nitros-OS9 builds for the Dragon. Thus far I've checked out the repro using HG and built the Dragon & CoCo1 disk images. They all build ok but whilst the coco1 creates "native", drivewire & becker-drivewire disk images, the D64 ...

Hi Pere, It's always fun(?) when you make a minor tweak and everything collapses in a big heap.. Anyway here's my thoughts on what I think it is you are seeing: I did format a disk in my Dragon: DSKINIT1,1,80 and it created a 360K disk. When I sent it to DW4, I got a VDK that once opened with XRoar ...

robcfg wrote:Just out of curiosity, why do you need a 256 byte VDK header? Aren't the usual 12 bytes enough?

Drivewire needs everything aligned to a 256 byte boundary. The disk images themselves will of course meet that criteria but an additional 12 bytes throws it out. Hence the need to pad it out.