Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!iuvax!ndcheg!uceng!schriste
From: schriste@uceng.UC.EDU (steven v christensen)
Newsgroups: comp.sys.ibm.pc
Subject: Re: vdisk.sys problem
Summary: Same thing happened to me
Keywords: vdisk, dos 3.3 error
Message-ID: <1442@uceng.UC.EDU>
Date: 8 Jul 89 04:28:23 GMT
References: <127@snll-arpagw.UUCP>
Distribution: na
Organization: Univ. of Cincinnati, College of Engg.
Lines: 19

In article <127@snll-arpagw.UUCP>, russ@snll-arpagw.UUCP (Russ Wertenberg) writes:
> 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 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.

I also have a hard disk with DISK-MANAGER, and a VDISK. I have found that if
I put the DEVICE=VDISK.... statement after the DEVICE=DMDRVR.BIN (or what-
ever the DISK-MANAGER driver is called) everything is OK. What happens is that
both DMDRVR.BIN and VDISK.SYS grab the next drive letter.

Steven
-- 
Steven V. Christensen
U.C. College of Eng.
schriste@uceng.uc.edu