Search found 89 matches
- Thu Apr 09, 2015 7:27 pm
- Forum: Dragon General
- Topic: FUZIX
- Replies: 6
- Views: 3373
Re: FUZIX
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.
- Fri Apr 03, 2015 3:55 pm
- Forum: Uploads
- Topic: NitrOS9 V3.3.0 for DragonDos and Drivewire
- Replies: 8
- Views: 5803
Re: NitrOS9 V3.3.0 for DragonDos and Drivewire
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...
- Fri Apr 03, 2015 3:48 pm
- Forum: Uploads
- Topic: OS9 PD library, Prolog, 5.25" disks
- Replies: 2
- Views: 2546
Re: OS9 PD library, Prolog, 5.25" disks
Here are the disk images for the OS9 Newsgroup & PD Library I mentioned plus a couple of other bits I found lying around.
- Sat Mar 28, 2015 10:21 am
- Forum: Dragon General
- Topic: Dragon OS9 with drivewire support
- Replies: 47
- Views: 17494
Re: Dragon OS9 with drivewire support
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 ...
- Fri Mar 27, 2015 12:35 pm
- Forum: Dragon General
- Topic: Dragon OS9 with drivewire support
- Replies: 47
- Views: 17494
Re: Dragon OS9 with drivewire support
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 ....
- Wed Mar 25, 2015 8:28 pm
- Forum: Dragon General
- Topic: Dragon OS9 with drivewire support
- Replies: 47
- Views: 17494
Re: Dragon OS9 with drivewire support
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.
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.
- Wed Mar 25, 2015 8:26 pm
- Forum: Uploads
- Topic: NitrOS9 V3.3.0 for DragonDos and Drivewire
- Replies: 8
- Views: 5803
Re: NitrOS9 V3.3.0 for DragonDos and Drivewire
Thanks Ken, I will have a play and see what I can break...
- Wed Mar 25, 2015 2:02 pm
- Forum: Uploads
- Topic: NitrOS9 V3.3.0 for DragonDos and Drivewire
- Replies: 8
- Views: 5803
Re: NitrOS9 V3.3.0 for DragonDos and Drivewire
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 ...
- Wed Mar 25, 2015 1:54 pm
- Forum: Dragon General
- Topic: Dragon OS9 with drivewire support
- Replies: 47
- Views: 17494
Re: Dragon OS9 with drivewire support
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 ...
- Tue Mar 24, 2015 9:10 pm
- Forum: Dragon General
- Topic: Dragon OS9 with drivewire support
- Replies: 47
- Views: 17494
Re: Dragon OS9 with drivewire support
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.robcfg wrote:Just out of curiosity, why do you need a 256 byte VDK header? Aren't the usual 12 bytes enough?