[Coco] HDBDOS (IDE) & MESS (Coco2)

[Juan Castro]

I use XRoar and the "Becker port" version of HDB-DOS. Then you serve the
image through the DriveWire server, which can be configured for that. Works
beautifully.

If I'm not mistaken, that can be described as paravirtualization. Am I
making sense?


On Wed, Mar 12, 2014 at 8:58 AM, Mark McDougall <msmcdoug at iinet.net.au>wrote:

> Hi all,
>
> Apologies if this info is elsewhere but a search through the last few
> years of the mailing list archives didn't give me any hints...
>
> I'm trying to run my HDBDOS (IDE) image with the Coco2 in MESS v152.
>
> So what I've done is replace the disk11.rom image with my HDBDOS image;
> that's loading fine.
>
> I then start up MESS with the -flop1 and -hard1 options specifying floppy
> and hard drive images respectively. The hard drive image I'm using is the
> one that works with my aforementioned HDBDOS image. I'm aware the RSDOS
> offset is not 'standard', but since my HDBDOS image matches my hard disk
> image, that should be OK - right?
>
> I get the HDB-DOS startup screen, and then:
>
> LBA HARD DRIVE NOT FOUND
>
> This suggests to me that the issue is perhaps not with the image itself,
> but the emulation in MESS?!? What is HDBDOS doing to 'detect' an IDE drive?
> Is it issuing an IDETIFY_DEVICE command (I seem to recall that it is). I
> couldn't see any support for that in MESS's coco_vhd.c file... maybe this
> is the issue?
>
> Regards,
>
> --
> |              Mark McDougall                | "Electrical Engineers do it
> |  <http://members.iinet.net.au/~msmcdoug>   |   with less resistance!"
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>