russ@snll-arpagw.UUCP (Russ Wertenberg) (07/11/89)
Once again the NET has the solutions.
Below are the responses with the correct solutions to the problem of vdsk.sys
allocating the wrong (an existing drives) device drive letter to the virtual
disk drive. The solution is to make sure that the device driver for your hard-
disk is the first line in your CONFIG.SYS file. It seems that the partions are
not *there* until you run the disk-manager associated with your harddisk. If
you run vdsk.sys first, it only recognizes the C: drive and therefore assigns
D: to the virtual disk. Once this is done dmdrvr.bin (the disk driver from
Ontrack computer systems) comes along and attempts to assign the partitions a
drive letter. The problem seems to be that the diskmanager does not take the
next available drive letter (as vdsk.sys does) but attempts to assign predeter-
mined drive letters to each partition. It does behave well though. If the
drive letter has already been 'used' the partition will not be mounted.
I want to thank all of you who responded with many helpful solutions. Now for
the people who pinpointed the problem:
From: Russell Herman <ames!mailrus!me.utoronto.ca!rwh>
Subject: Re: vdisk.sys problem
Organization: U of T Mechanical Engineering
Status: RO
I'm running hardware like that myself. Not using vdisk, though, the 3085
is fast enough for what I do, and I use DESQView. It sounds like vdisk isn't
finding the partitions that rmadrv.sys set up - did you load it BEFORE vdisk?
---=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=---
Russ Herman | Internet: rwh@me.utoronto.ca | University of Toronto
Comp. Sys. Mgr. | UUCP: uunet!utai!me!rwh | Dept. of Mech. Eng.
(416)978-4987 | | 5 King's College Rd.
(416)978-7753fax| | Toronto, ON M5S 1A4 Canada
Date: Sat, 8 Jul 89 17:40:25 EDT
From: Kenneth H. Lee <ames!rutgers!cunixc.cc.columbia.edu!khl>
Subject: Re: vdisk.sys problem
Newsgroups: comp.sys.ibm.pc
Organization: Columbia University Center for Computing Activities, NY, NY
I had the same problem in my AT clone. I put the VDISK device driver
after the DMDRVR device driver and everything works the way I want it
to. Each device driver looks for the next available drive letter so
you should order your drivers according to the way you want the drives
assigned on your machine.
hope this helps/k
--
Kenneth H. Lee khl@cunixc.cc.columbia.edu
Columbia University ...{topaz|rutgers}!columbia!cunixc!khl
209 Watson, 612 West 115 Street khlcu@cuvmc.bitnet
New York, NY 10025 (212) 854-8230
From: schriste@uceng.UC.EDU (steven v christensen)
Subject: Re: vdisk.sys problem
Summary: Same thing happened to me
Keywords: vdisk, dos 3.3 error
Date: 8 Jul 89 04:28:23 GMT
Organization: Univ. of Cincinnati, College of Engg.
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