Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
05850 Core Major Always Feb 16, 2015, 20:30 Feb 24, 2015, 00:49
Tester Robert Gault View Status Public Platform MESS (Official Binary)
Assigned To Resolution Open OS Windows XP
Status [?] Acknowledged Driver
Version 0.158 Fixed in Version Build Normal
Fixed in Git Commit Github Pull Request #
Summary MESS-specific 05850: coco3dw1: Difficult to classify but problem with NitrOS-9 on .vhd in Drivewire
Description When you mount a .vhd drive in Drivewire which has a NitrOS-9 section and a Disk Basic section, you should be able to first read the Disk Basic drives and if one is a NitrOS-9 boot disk, use it to boot NitrOS-9. You can access the Disk Basic "drives" but then not the NitrOS-9 section.

There are two ways to do this. If the Disk Basic offset in hdbdw3bc3.rom is $000000 and the drive o9ffset in Drivewire is $5A000, then you can read/write to the Disk Basic "drives" on the .vhd. If the ROM has the $5A000 offset and Drivewire an $00000 offset, you can still read/write the Disk Basic "drives" but not the NitrOS-9 section.
If both offsets are $00000, and you mount a boot disk .dsk in Drivewire, then NitrOS-9 will boot.

My guess is that the ROM offset is always active even when the ROM is not being used in coco3dw1 emulation.
Steps To Reproduce You will need a .vhd drive which has a Becker Drivewire boot disk in the Disk Basic section and NitrOS-9 installed in the OS-9 section. With Drivewire having a $00000 offset, start coco3dw1 emulation and POKE&HD938,5:POKE&HD939,&HA0. You will be able to access all the Disk Basic "drives" on the .vhd. Now try to boot from the appropriate "drive".
If you start coco3 or coco3h emulation and mount the hdbdw3bc3.rom in the cart slot and proceed as above, you can boot NitrOS-9. So something in the coco3dw1 emulation vs coco3 or coco3h emulation is causing the problem.
Additional Information
Github Commit
Flags
Regression Version
Affected Sets / Systems coco3dw1
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
1
User avatar
No.11468
Robert Gault
Tester
Feb 16, 2015, 20:38
I forgot to mention that when you start mess.exe from a command window, on exit from emulation the above bug gives a
coco_dwsock.c: beckerport_device::read() buffer underrun