Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!agate!eos!aurora!woody
From: woody@aurora.uucp (Wayne Wood)
Newsgroups: comp.sys.ibm.pc
Subject: Re: vdisk.sys problem
Keywords: vdisk, dos 3.3 error
Message-ID: <4271@eos.UUCP>
Date: 7 Jul 89 17:48:43 GMT
References: <127@snll-arpagw.UUCP>
Sender: news@eos.UUCP
Reply-To: woody@aurora.UUCP (Wayne Wood)
Distribution: na
Organization: NASA Ames Research Center, California
Lines: 26

In article <127@snll-arpagw.UUCP> russ@snll-arpagw.UUCP (Russ Wertenberg) writes:
>memory.  The harddisk is currently partitioned into 3 27Mb divisions (c:, d:, &
>e:) and when we attempt to implement vdisk.sys in extended memory it assigns
>the virtual disk to D:!!  This is obviously not good.  The harddisk information
>on drives C and E are still fully accessible, but any attempt to use access the
>harddisk drive D fails (you just get the virtual disk as you might guess).
>
>Removing the driver statement from CONFIG.SYS with a reboot returns the system

theoretically [ha ha] the vdisk.sys driver allocates a drive number 
corresponding to one above the last *recognized* physical drive [at least it
does on my version of DOS 3.1].  but it may not realize that the partitions
on your hard disk are there.  therefore [impressive hand-waving here] it
is not truly recognizing the virtual drives [partitions] on your hard-disk.

check the last drive parameter in your config.sys and raise it to [say]
g.  the default is f [i believe].

THIS WORKED FOR ME...YOUR MILEAGE MAY VARY.  TRY IT AT YOUR OWN RISK!

-- woody
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%   ...tongue tied and twisted, just an earthbound misfit, I...            %%
%%   -- David Gilmour, Pink Floyd                                           %%
%%   woody@aurora.arc.nasa.gov %% my opinions,like my mind,are my own       %%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%