Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!lll-winken!snll-arpagw!russ
From: russ@snll-arpagw.UUCP (Russ Wertenberg)
Newsgroups: comp.sys.ibm.pc
Subject: vdisk.sys problem
Summary: vdisk allocates wrong (already used) disk
Keywords: vdisk, dos 3.3 error
Message-ID: <127@snll-arpagw.UUCP>
Date: 6 Jul 89 17:58:37 GMT
Reply-To: russ@snll-arpagw.UUCP (Russ Wertenberg)
Distribution: na
Organization: Sandia National Labs, Livermore, CA
Lines: 26

I have encountered a baffling error on several PC's that we have been using
at work.  These machines use a MINI-386/387 20mhz motherboard (32 bit 386, 387,
and Chips & Technologies chip set), which uses PC-DOS 3.30, and has an 80 Mb
Seagate harddisk which is running DISK-MANAGER version 3.30.  The BIOS is 
Phoenix 80386 ROM BIOS PLUS 1.10 02 and each machine has 2 Mb of interleaved 
memory on the motherboard (384 k of which is set aside for shadow).

The problem we encounter is when we attempt to create a virtual disk in extended
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
to normal as one might expect, and harddisk data has not been corrupted.  I have
a similar system which is running a 286/287 20mhz and version 3.20 of DISK-
MANAGER and this problem does not occur.

Has anyone else run across a similar problem?  Anyone found a fix or have a
suggestion for fixing the virtual disk drive assignment problem?

If enough are interested, I will post a summary.

Thanks in advance,
			Russ