[Coco] mess HD problem
Bob Devries
devries.bob at gmail.com
Mon Aug 4 22:34:15 EDT 2014
Hi all,
I used the "devs" utility, and found that the "static mem" pointer for
both H0 and H1 are the same at $6900, but DD is $7900. My guess is that
this should not be so. Each device should have its own static memory.
I wonder if emudsk.dr should be recompiled to work correctly with two
hard disks?
If I remember correctly, each RBF driver should have the correct number
of drives set in the source.
Regards, Bob Devries
Dalby, QLD, Australia
On 5/08/2014 12:02 PM, Kip Koon wrote:
> Hi Bob!
> Have you tried issuing the "chx /dd/cmds" and "chd /dd" commands to get
> control back?
>
> Kip Koon
> computerdoc at sc.rr.com
> http://www.cocopedia.com/wiki/index.php/Kip_Koon
> http://computerpcdoc.com/
>
>
> -----Original Message-----
> From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of Bob Devries
> Sent: Monday, August 04, 2014 9:22 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: [Coco] mess HD problem
>
> Hi all,
>
> does anyone here use MESS with two hard disk (VHD) images?
>
> I'm seeing some odd behaviour here. This shows up in both the linux and
> windows versions.
>
> It seems that NitrOS9 forgets the current working directory and execution
> directory. When that happens, nothing that I do will work; even typing
> /DD/CMDS/<insert filename here> will not work, and gives error 216.
>
> I'm not sure, but I *think* it's related to having two VHD images mounted.
> everything appears to work fine with just one VHD. Is this a mess problem,
> or NitrOS9? I'm using the latest version of NitrOS9.
>
> My VHD images are identical in size, but not, of course, contents. Both are
> ~120MB.
>
> Regards, Bob Devries
> Dalby, QLD, Australia
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>
More information about the Coco
mailing list