[Coco] mess HD problem

[Bob Devries]

And it gets worse.....

I tried to create a new directory (we're on MESSUI0154) and CRASH CITY!

Stranger still... it doesn't happen under Linux.

I wonder if it is something to do with the location of the vhd and dsk 
files? Currently in the Program Files(X86)/mess folder.

Comments/suggestions?

Regards, Bob Devries
Dalby, QLD, Australia

P.S. Q:Why am I punishing myself? .... A:just trying to keep the brain 
in shape :)


On 5/08/2014 1:09 PM, Kip Koon wrote:
> Hi Bob!
> I'll download the latest version of MESS and run it on my Windows 7 SP1
> 64-bit laptop and see how it goes.  I'll let you know the results as soon as
> I find some room on my hard drive, download MESS, get it setup and do the
> test.
>
> 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 11:00 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] mess HD problem
>
> Hi Kip,
> I'm currently using MESSUI v0154 on Windows 8.1. I also have MESS v0152 set
> up on KUbuntu. Both exhibit the same problem.
>
> Regards, Bob Devries
> Dalby, QLD, Australia
>
>
> On 5/08/2014 12:50 PM, Kip Koon wrote:
>> Hi Bob!
>> I've never had a version of MESS with two drives.  Did you compile a
>> custom version of MESS?  I usually used the latest version of MESS
>> when I was playing around with it and it always had just one HD.
>>
>> 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 10:34 PM
>> To: CoCoList for Color Computer Enthusiasts
>> Subject: Re: [Coco] mess HD problem
>>
>> 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
>>>
>>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>