[Coco] mess HD problem

[Kip Koon]

Hi Bob!
Oops, I didn't register your question about VCC.  You can use EmuDsk to
access /h0 as you have been doing.  You also can install the ide.dll file
into MPI Slot 1 and that will give you a Glenside IDE Controller with an IDE
Master and IDE Slave virtual Hard drives as well as IDE Config.  VCC 1.43b
installs without the Glenside IDE Controller in the MPI Slot 1.  Initially
Slot 1 is empty.  The IDE.dll file should be in the VCC 1.43b folder with
the rest of the files VCC needs to run.  I hope this is clear to you.

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:43 PM
To: CoCoList for Color Computer Enthusiasts
Subject: Re: [Coco] mess HD problem

Hi Kip,
Which version of VCC allows the use of more than one VHD? The version I'm
using (1.43b) doesn't.

I checked the source code of emudsk.dr, and it correctly sets the DRVMEM for
two drives. I'll study the code to see if there's anywhere that the wrong
memory area is used.

Robert Gault, have you any experience with this?

Regards, Bob Devries
Dalby, QLD, Australia

On 5/08/2014 12:27 PM, Kip Koon wrote:
> Hi Bob!
> That is very interesting?!?  If your cmds directory is /dd/cmds then 
> I'm not sure what's going on.  Though it's not the same as MESS, I've 
> run VCC with two or even three VHD files mounted and as far as 
> NitrOS-9 is concerned I have not had any problems once I realized I 
> had to copy an existing vhd file and reformat it if I wanted another 
> vhd file mounted in another drive.  You can't create vhd files using 
> Drivewire because there is an incompatibility and I'm not sure if you 
> can do it at all in VCC.  I hope this helps.  Take care my friend.
>
> 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:13 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] mess HD problem
>
> Hi Kip,
>
> yes, I tried "chd /dd" and that works, but "chx /dd/cmds" does not.
> replacing /dd with /h0 or /h1 doesn't work either.
>
> 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