Sign in with
Sign up | Sign in
Your question

a VxD load failure, and related questions...

Last response: in Windows 95/98/ME
Share
Anonymous
May 8, 2005 3:05:55 AM

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

I was just playing around with my system (which is working fine right now),
and found out something interesting that I hope somebody can explain to me
(I haven't found a good explanation yet in my searches so far):

I noticed in a Bootlog.txt file (I made it create one) that ndis2.vxd
"loadfailed", so I thought I'd "help it along" by putting a copy of
ndis2.vxd in the windows\system\vmm32 folder. After bootup, it blue
screened, and I had to restore the registry (and remove that copied file).

What am I missing here? I don't get it - first, why putting that file in
there would hurt anything, and second, why ndis2.vxd is showing up as
loadfailed in the boot log. (It apparently is not being incorporated into
vmm32.vxd either, I gather)
Anonymous
May 8, 2005 5:20:47 AM

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

Load Failures Listed in the Bootlog.txt File
http://support.microsoft.com/?kbid=127970
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm
http://www.microsoft.com/communities/conduct/default.ms...


"Bill in Co." <not_really_here@earthlink.net> wrote in message
news:o zb7eu4UFHA.3056@TK2MSFTNGP14.phx.gbl...
> I was just playing around with my system (which is working fine right now),
> and found out something interesting that I hope somebody can explain to me
> (I haven't found a good explanation yet in my searches so far):
>
> I noticed in a Bootlog.txt file (I made it create one) that ndis2.vxd
> "loadfailed", so I thought I'd "help it along" by putting a copy of
> ndis2.vxd in the windows\system\vmm32 folder. After bootup, it blue
> screened, and I had to restore the registry (and remove that copied file).
>
> What am I missing here? I don't get it - first, why putting that file in
> there would hurt anything, and second, why ndis2.vxd is showing up as
> loadfailed in the boot log. (It apparently is not being incorporated into
> vmm32.vxd either, I gather)
>
>
Anonymous
May 8, 2005 5:46:15 AM

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

Thanks Glen. Looks like I was trying to force it to load a VxD with no
supporting hardware (if I'm reading that right - I have no network card)

I have noticed one other anomoly. The last two times I reinstalled
windows, mrci2.vxd was located in the \windows\system\vmm32 subdirectory,
but I don't have it in there now. Why, I have no idea. Do you know why
(or does anybody)?

For some strange reason, it doesn't appear necessary THIS time.

glee wrote:
> Load Failures Listed in the Bootlog.txt File
> http://support.microsoft.com/?kbid=127970
> --
> Glen Ventura, MS MVP Shell/User, A+
> http://dts-l.org/goodpost.htm
> http://www.microsoft.com/communities/conduct/default.ms...
>
>
> "Bill in Co." <not_really_here@earthlink.net> wrote in message
> news:o zb7eu4UFHA.3056@TK2MSFTNGP14.phx.gbl...
>> I was just playing around with my system (which is working fine right
now),
>> and found out something interesting that I hope somebody can explain to
me
>> (I haven't found a good explanation yet in my searches so far):
>>
>> I noticed in a Bootlog.txt file (I made it create one) that ndis2.vxd
>> "loadfailed", so I thought I'd "help it along" by putting a copy of
>> ndis2.vxd in the windows\system\vmm32 folder. After bootup, it blue
>> screened, and I had to restore the registry (and remove that copied
file).
>>
>> What am I missing here? I don't get it - first, why putting that file
in
>> there would hurt anything, and second, why ndis2.vxd is showing up as
>> loadfailed in the boot log. (It apparently is not being incorporated
into
>> vmm32.vxd either, I gather)
Related resources
Anonymous
May 8, 2005 4:40:25 PM

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

Have a look here:
http://groups-beta.google.com/group/microsoft.public.wi...

MVP Jeff Richards (who is a bit smarter than me ;) ) writes that MRCI2.vxd is the
MS-DOS 6.22 Drivespace protected mode compression driver. Take a look at that
thread.
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm
http://www.microsoft.com/communities/conduct/default.ms...


"Bill in Co." <not_really_here@earthlink.net> wrote in message
news:ez2zEI6UFHA.1044@TK2MSFTNGP10.phx.gbl...
> Thanks Glen. Looks like I was trying to force it to load a VxD with no
> supporting hardware (if I'm reading that right - I have no network card)
>
> I have noticed one other anomoly. The last two times I reinstalled
> windows, mrci2.vxd was located in the \windows\system\vmm32 subdirectory,
> but I don't have it in there now. Why, I have no idea. Do you know why
> (or does anybody)?
>
> For some strange reason, it doesn't appear necessary THIS time.
>
> glee wrote:
> > Load Failures Listed in the Bootlog.txt File
> > http://support.microsoft.com/?kbid=127970
> > --
> > Glen Ventura, MS MVP Shell/User, A+
> > http://dts-l.org/goodpost.htm
> > http://www.microsoft.com/communities/conduct/default.ms...
> >
> >
> > "Bill in Co." <not_really_here@earthlink.net> wrote in message
> > news:o zb7eu4UFHA.3056@TK2MSFTNGP14.phx.gbl...
> >> I was just playing around with my system (which is working fine right
> now),
> >> and found out something interesting that I hope somebody can explain to
> me
> >> (I haven't found a good explanation yet in my searches so far):
> >>
> >> I noticed in a Bootlog.txt file (I made it create one) that ndis2.vxd
> >> "loadfailed", so I thought I'd "help it along" by putting a copy of
> >> ndis2.vxd in the windows\system\vmm32 folder. After bootup, it blue
> >> screened, and I had to restore the registry (and remove that copied
> file).
> >>
> >> What am I missing here? I don't get it - first, why putting that file
> in
> >> there would hurt anything, and second, why ndis2.vxd is showing up as
> >> loadfailed in the boot log. (It apparently is not being incorporated
> into
> >> vmm32.vxd either, I gather)
>
>
Anonymous
May 8, 2005 5:12:34 PM

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

Thanks, Glen. I just read the thread.

I have no use of Drivespace (and I have*never* used it - to my knowledge),
so I'm scratching my head wondering how it ever got installed in that
\system\vmm32 subdirectory before.

(Maybe some software, unbeknownst to me, installed that driver, in those
earlier installations)

glee wrote:
> Have a look here:
>
http://groups-beta.google.com/group/microsoft.public.wi...
owse_frm/thread/1c1766b71a6f9678/5cdaa1dedf828c40?q=what+is+mrci2&rnum=2&hl=
en#5cdaa1dedf828c40
>
> MVP Jeff Richards (who is a bit smarter than me ;) ) writes that MRCI2.vxd
is
> the MS-DOS 6.22 Drivespace protected mode compression driver. Take a
> look at that thread.
> --
> Glen Ventura, MS MVP Shell/User, A+
> http://dts-l.org/goodpost.htm
> http://www.microsoft.com/communities/conduct/default.ms...
>
>
> "Bill in Co." <not_really_here@earthlink.net> wrote in message
> news:ez2zEI6UFHA.1044@TK2MSFTNGP10.phx.gbl...
>> Thanks Glen. Looks like I was trying to force it to load a VxD with no
>> supporting hardware (if I'm reading that right - I have no network card)
>>
>> I have noticed one other anomoly. The last two times I reinstalled
>> windows, mrci2.vxd was located in the \windows\system\vmm32
subdirectory,
>> but I don't have it in there now. Why, I have no idea. Do you know
why
>> (or does anybody)?
>>
>> For some strange reason, it doesn't appear necessary THIS time.
>>
>> glee wrote:
>>> Load Failures Listed in the Bootlog.txt File
>>> http://support.microsoft.com/?kbid=127970
>>> --
>>> Glen Ventura, MS MVP Shell/User, A+
>>> http://dts-l.org/goodpost.htm
>>> http://www.microsoft.com/communities/conduct/default.ms...
>>>
>>>
>>> "Bill in Co." <not_really_here@earthlink.net> wrote in message
>>> news:o zb7eu4UFHA.3056@TK2MSFTNGP14.phx.gbl...
>>>> I was just playing around with my system (which is working fine right
now),
>>>> and found out something interesting that I hope somebody can explain to
>> me
>>>> (I haven't found a good explanation yet in my searches so far):
>>>>
>>>> I noticed in a Bootlog.txt file (I made it create one) that ndis2.vxd
>>>> "loadfailed", so I thought I'd "help it along" by putting a copy of
>>>> ndis2.vxd in the windows\system\vmm32 folder. After bootup, it
blue
>>>> screened, and I had to restore the registry (and remove that copied
>> file).
>>>>
>>>> What am I missing here? I don't get it - first, why putting that
file in
>>>> there would hurt anything, and second, why ndis2.vxd is showing up as
>>>> loadfailed in the boot log. (It apparently is not being incorporated
>> into
>>>> vmm32.vxd either, I gather)
Anonymous
May 8, 2005 7:22:18 PM

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

I dunno....I do have mrci2.vxd there on this system, but this is an upgrade from
Win95B. Perhaps it's time to track down Jeff Richards and ask him, as he seems more
knowledgeable on the subject?
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm
http://www.microsoft.com/communities/conduct/default.ms...

"Bill in Co." <not_really_here@earthlink.net> wrote in message
news:eydNmHAVFHA.628@TK2MSFTNGP09.phx.gbl...
> Thanks, Glen. I just read the thread.
>
> I have no use of Drivespace (and I have*never* used it - to my knowledge),
> so I'm scratching my head wondering how it ever got installed in that
> \system\vmm32 subdirectory before.
>
> (Maybe some software, unbeknownst to me, installed that driver, in those
> earlier installations)
>
> glee wrote:
> > Have a look here:
> >
> http://groups-beta.google.com/group/microsoft.public.wi...
> owse_frm/thread/1c1766b71a6f9678/5cdaa1dedf828c40?q=what+is+mrci2&rnum=2&hl=
> en#5cdaa1dedf828c40
> >
> > MVP Jeff Richards (who is a bit smarter than me ;) ) writes that MRCI2.vxd
> is
> > the MS-DOS 6.22 Drivespace protected mode compression driver. Take a
> > look at that thread.
> > --
> > Glen Ventura, MS MVP Shell/User, A+
> > http://dts-l.org/goodpost.htm
> > http://www.microsoft.com/communities/conduct/default.ms...
> >
> >
> > "Bill in Co." <not_really_here@earthlink.net> wrote in message
> > news:ez2zEI6UFHA.1044@TK2MSFTNGP10.phx.gbl...
> >> Thanks Glen. Looks like I was trying to force it to load a VxD with no
> >> supporting hardware (if I'm reading that right - I have no network card)
> >>
> >> I have noticed one other anomoly. The last two times I reinstalled
> >> windows, mrci2.vxd was located in the \windows\system\vmm32
> subdirectory,
> >> but I don't have it in there now. Why, I have no idea. Do you know
> why
> >> (or does anybody)?
> >>
> >> For some strange reason, it doesn't appear necessary THIS time.
> >>
> >> glee wrote:
> >>> Load Failures Listed in the Bootlog.txt File
> >>> http://support.microsoft.com/?kbid=127970
> >>> --
> >>> Glen Ventura, MS MVP Shell/User, A+
> >>> http://dts-l.org/goodpost.htm
> >>> http://www.microsoft.com/communities/conduct/default.ms...
> >>>
> >>>
> >>> "Bill in Co." <not_really_here@earthlink.net> wrote in message
> >>> news:o zb7eu4UFHA.3056@TK2MSFTNGP14.phx.gbl...
> >>>> I was just playing around with my system (which is working fine right
> now),
> >>>> and found out something interesting that I hope somebody can explain to
> >> me
> >>>> (I haven't found a good explanation yet in my searches so far):
> >>>>
> >>>> I noticed in a Bootlog.txt file (I made it create one) that ndis2.vxd
> >>>> "loadfailed", so I thought I'd "help it along" by putting a copy of
> >>>> ndis2.vxd in the windows\system\vmm32 folder. After bootup, it
> blue
> >>>> screened, and I had to restore the registry (and remove that copied
> >> file).
> >>>>
> >>>> What am I missing here? I don't get it - first, why putting that
> file in
> >>>> there would hurt anything, and second, why ndis2.vxd is showing up as
> >>>> loadfailed in the boot log. (It apparently is not being incorporated
> >> into
> >>>> vmm32.vxd either, I gather)
>
>
Anonymous
May 9, 2005 2:56:33 AM

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

Bill,

If you have DRVSPACE.BIN or DBLSPACE.BIN files in the root check
the Msdos.sys file for:
DBLSpace=1
DRVSpace=1
Change the values to 0 (zero)
If those BIN files are found in the root then the entries are made
in the Msdos.sys file. It would use some memory even though
compression is not setup.

I have the files in the root even though I have never used
compression.

Regards,

Bill Watt
Computer Help and Information http://home.ptd.net/~bwatt/
______________________________________

On Sun, 8 May 2005 13:12:34 -0600, "Bill in Co."
<not_really_here@earthlink.net> wrote:

>Thanks, Glen. I just read the thread.
>
>I have no use of Drivespace (and I have*never* used it - to my knowledge),
>so I'm scratching my head wondering how it ever got installed in that
>\system\vmm32 subdirectory before.
>
>(Maybe some software, unbeknownst to me, installed that driver, in those
>earlier installations)
>
>glee wrote:
>> Have a look here:
>>
>http://groups-beta.google.com/group/microsoft.public.wi...
>owse_frm/thread/1c1766b71a6f9678/5cdaa1dedf828c40?q=what+is+mrci2&rnum=2&hl=
>en#5cdaa1dedf828c40
>>
>> MVP Jeff Richards (who is a bit smarter than me ;) ) writes that MRCI2.vxd
>is
>> the MS-DOS 6.22 Drivespace protected mode compression driver. Take a
>> look at that thread.
>> --
>> Glen Ventura, MS MVP Shell/User, A+
>> http://dts-l.org/goodpost.htm
>> http://www.microsoft.com/communities/conduct/default.ms...
>>
>>
>> "Bill in Co." <not_really_here@earthlink.net> wrote in message
>> news:ez2zEI6UFHA.1044@TK2MSFTNGP10.phx.gbl...
>>> Thanks Glen. Looks like I was trying to force it to load a VxD with no
>>> supporting hardware (if I'm reading that right - I have no network card)
>>>
>>> I have noticed one other anomoly. The last two times I reinstalled
>>> windows, mrci2.vxd was located in the \windows\system\vmm32
>subdirectory,
>>> but I don't have it in there now. Why, I have no idea. Do you know
>why
>>> (or does anybody)?
>>>
>>> For some strange reason, it doesn't appear necessary THIS time.
>>>
>>> glee wrote:
>>>> Load Failures Listed in the Bootlog.txt File
>>>> http://support.microsoft.com/?kbid=127970
>>>> --
>>>> Glen Ventura, MS MVP Shell/User, A+
>>>> http://dts-l.org/goodpost.htm
>>>> http://www.microsoft.com/communities/conduct/default.ms...
>>>>
>>>>
>>>> "Bill in Co." <not_really_here@earthlink.net> wrote in message
>>>> news:o zb7eu4UFHA.3056@TK2MSFTNGP14.phx.gbl...
>>>>> I was just playing around with my system (which is working fine right
>now),
>>>>> and found out something interesting that I hope somebody can explain to
>>> me
>>>>> (I haven't found a good explanation yet in my searches so far):
>>>>>
>>>>> I noticed in a Bootlog.txt file (I made it create one) that ndis2.vxd
>>>>> "loadfailed", so I thought I'd "help it along" by putting a copy of
>>>>> ndis2.vxd in the windows\system\vmm32 folder. After bootup, it
>blue
>>>>> screened, and I had to restore the registry (and remove that copied
>>> file).
>>>>>
>>>>> What am I missing here? I don't get it - first, why putting that
>file in
>>>>> there would hurt anything, and second, why ndis2.vxd is showing up as
>>>>> loadfailed in the boot log. (It apparently is not being incorporated
>>> into
>>>>> vmm32.vxd either, I gather)
>
Anonymous
May 9, 2005 2:56:34 AM

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

Bill Watt wrote:
> Bill,
>
> If you have DRVSPACE.BIN or DBLSPACE.BIN files in the root check
> the Msdos.sys file for:

I don't have those (and don't want em on my machine, either!)
(and, no, they're not in Msdos.sys)

> DBLSpace=1
> DRVSpace=1
> Change the values to 0 (zero)
> If those BIN files are found in the root then the entries are made
> in the Msdos.sys file. It would use some memory even though
> compression is not setup.
>
> I have the files in the root even though I have never used
> compression.

Wonder how you got them? Maybe you installed the disk compression tools
as an option in windows setup (or added it in later). Or maybe third
party software did it. (?)

> Regards,
>
> Bill Watt
> Computer Help and Information http://home.ptd.net/~bwatt/
> ______________________________________
>
> On Sun, 8 May 2005 13:12:34 -0600, "Bill in Co."
> <not_really_here@earthlink.net> wrote:
>
>> Thanks, Glen. I just read the thread.
>>
>> I have no use of Drivespace (and I have*never* used it - to my
knowledge),
>> so I'm scratching my head wondering how it ever got installed in that
>> \system\vmm32 subdirectory before.
>>
>> (Maybe some software, unbeknownst to me, installed that driver, in those
>> earlier installations)
>>
>> glee wrote:
>>> Have a look here:
>>>
>>
http://groups-beta.google.com/group/microsoft.public.wi...
>>
owse_frm/thread/1c1766b71a6f9678/5cdaa1dedf828c40?q=what+is+mrci2&rnum=2&hl=
>> en#5cdaa1dedf828c40
>>>
>>> MVP Jeff Richards (who is a bit smarter than me ;) ) writes that
MRCI2.vxd is
>>> the MS-DOS 6.22 Drivespace protected mode compression driver. Take a
>>> look at that thread.
>>> --
>>> Glen Ventura, MS MVP Shell/User, A+
>>> http://dts-l.org/goodpost.htm
>>> http://www.microsoft.com/communities/conduct/default.ms...
>>>
>>>
>>> "Bill in Co." <not_really_here@earthlink.net> wrote in message
>>> news:ez2zEI6UFHA.1044@TK2MSFTNGP10.phx.gbl...
>>>> Thanks Glen. Looks like I was trying to force it to load a VxD with
no
>>>> supporting hardware (if I'm reading that right - I have no network
card)
>>>>
>>>> I have noticed one other anomoly. The last two times I reinstalled
>>>> windows, mrci2.vxd was located in the \windows\system\vmm32
subdirectory,
>>>> but I don't have it in there now. Why, I have no idea. Do you
know
>>>> why (or does anybody)?
>>>>
>>>> For some strange reason, it doesn't appear necessary THIS time.
>>>>
>>>> glee wrote:
>>>>> Load Failures Listed in the Bootlog.txt File
>>>>> http://support.microsoft.com/?kbid=127970
>>>>> --
>>>>> Glen Ventura, MS MVP Shell/User, A+
>>>>> http://dts-l.org/goodpost.htm
>>>>> http://www.microsoft.com/communities/conduct/default.ms...
>>>>>
>>>>>
>>>>> "Bill in Co." <not_really_here@earthlink.net> wrote in message
>>>>> news:o zb7eu4UFHA.3056@TK2MSFTNGP14.phx.gbl...
>>>>>> I was just playing around with my system (which is working fine right
>>>>>> now), and found out something interesting that I hope somebody can
>>>>>> explain to me (I haven't found a good explanation yet in my searches
so
>>>>>> far):
>>>>>>
>>>>>> I noticed in a Bootlog.txt file (I made it create one) that ndis2.vxd
>>>>>> "loadfailed", so I thought I'd "help it along" by putting a copy of
>>>>>> ndis2.vxd in the windows\system\vmm32 folder. After bootup, it
blue
>>>>>> screened, and I had to restore the registry (and remove that copied
>>>>>> file).
>>>>>>
>>>>>> What am I missing here? I don't get it - first, why putting that
file
>>>>>> in there would hurt anything, and second, why ndis2.vxd is showing up
as
>>>>>> loadfailed in the boot log. (It apparently is not being incorporated
>>>>>> into vmm32.vxd either, I gather)
Anonymous
May 9, 2005 4:24:05 AM

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

Bill in Co. wrote:

> Thanks, Glen. I just read the thread.
>
> I have no use of Drivespace (and I have*never* used it - to my knowledge),
> so I'm scratching my head wondering how it ever got installed in that
> \system\vmm32 subdirectory before.
>
> (Maybe some software, unbeknownst to me, installed that driver, in those
> earlier installations)

MRCI2.vxd gets installed as part of the following:
Win98(FE&SE) Optional Components - System Tools - [Disk] Compression Tools.

I think that if you install this, that the option disappears from the
list so you can't uninstall it again.

I'm guessing that on earlier installs you probably choose to install
this (or did one of the standard installs), but that this time you did a
custom install and now knew that you had no use for DriveSpace and
choose to leave it unchecked.
Or, like you said, perhaps you installed some 3rd party software that
automatically forced the install of this Win98 Optional Component.

> glee wrote:
>
>>Have a look here:
>>
>
> http://groups-beta.google.com/group/microsoft.public.wi...
> owse_frm/thread/1c1766b71a6f9678/5cdaa1dedf828c40?q=what+is+mrci2&rnum=2&hl=
> en#5cdaa1dedf828c40
>
>>MVP Jeff Richards (who is a bit smarter than me ;) ) writes that MRCI2.vxd
>
> is
>
>>the MS-DOS 6.22 Drivespace protected mode compression driver. Take a
>>look at that thread.

>>>
>>>I have noticed one other anomoly. The last two times I reinstalled
>>>windows, mrci2.vxd was located in the \windows\system\vmm32
> subdirectory,
>>>but I don't have it in there now. Why, I have no idea. Do you know
> why
>
>>>(or does anybody)?
>>>
>>>For some strange reason, it doesn't appear necessary THIS time.
>>>

--
Please followup in newsgroup.
E-mail address is invalid due to spam-control.
Anonymous
May 9, 2005 4:24:06 AM

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

.... et al. wrote:
> Bill in Co. wrote:
>
>> Thanks, Glen. I just read the thread.
>>
>> I have no use of Drivespace (and I have*never* used it - to my
knowledge),
>> so I'm scratching my head wondering how it ever got installed in that
>> \system\vmm32 subdirectory before.
>>
>> (Maybe some software, unbeknownst to me, installed that driver, in those
>> earlier installations)
>
> MRCI2.vxd gets installed as part of the following:
> Win98(FE&SE) Optional Components - System Tools - [Disk] Compression
Tools.
>
> I think that if you install this, that the option disappears from the
> list so you can't uninstall it again.

> I'm guessing that on earlier installs you probably choose to install
> this (or did one of the standard installs), but that this time you did a
> custom install and now knew that you had no use for DriveSpace and
> choose to leave it unchecked.

I nearly always use "custom" in my installs, and never installed those disk
compression tools. (Never have used them, and never will use them - am
dead set against them, and always have been)

> Or, like you said, perhaps you installed some 3rd party software that
> automatically forced the install of this Win98 Optional Component.

I think that's probably what happened.

>> glee wrote:
>>
>>> Have a look here:
>>>
>>
>>
http://groups-beta.google.com/group/microsoft.public.wi...
>>
owse_frm/thread/1c1766b71a6f9678/5cdaa1dedf828c40?q=what+is+mrci2&rnum=2&hl=
>> en#5cdaa1dedf828c40
>>
>>> MVP Jeff Richards (who is a bit smarter than me ;) ) writes that
MRCI2.vxd
>>
>> is
>>
>>> the MS-DOS 6.22 Drivespace protected mode compression driver. Take a
>>> look at that thread.
>
>>>>
>>>> I have noticed one other anomoly. The last two times I reinstalled
>>>> windows, mrci2.vxd was located in the \windows\system\vmm32
subdirectory,
>>>> but I don't have it in there now. Why, I have no idea. Do you
know
>>>> why
>>
>>>> (or does anybody)?
>>>>
>>>> For some strange reason, it doesn't appear necessary THIS time.
>>>>
>
> --
> Please followup in newsgroup.
> E-mail address is invalid due to spam-control.
Anonymous
May 9, 2005 5:37:13 AM

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

On Sun, 8 May 2005 22:20:28 -0600, "Bill in Co."
<not_really_here@earthlink.net> wrote:

>Bill Watt wrote:
>> Bill,
>>
>> If you have DRVSPACE.BIN or DBLSPACE.BIN files in the root check
>> the Msdos.sys file for:
>
>I don't have those (and don't want em on my machine, either!)
>(and, no, they're not in Msdos.sys)
>
>> DBLSpace=1
>> DRVSpace=1
>> Change the values to 0 (zero)
>> If those BIN files are found in the root then the entries are made
>> in the Msdos.sys file. It would use some memory even though
>> compression is not setup.
>>
>> I have the files in the root even though I have never used
>> compression.
>
>Wonder how you got them? Maybe you installed the disk compression tools
>as an option in windows setup (or added it in later). Or maybe third
>party software did it. (?)

They are dated 1998 and 1999 so I must have upgraded and just chose
everything. I can't think of a third party app that may have been
responsible. Also I have never formatted and re-installed since
before Win 3.1 so I could have acquired them anytime.

BTW this is what MRCI2.VXD does. :-)
MS Real Time Compression Interface (DriveSpace) Virtual Device.
DRVSPACX.VXD passes memory pointers to raw data, not the actual file
location, to MRCI2.VXD which performs the actual data compression.
MRCI2.VXD then passes the compressed data back to DRVSPACX.VXD.
DRVSPACX.VXD hands the file to the IOS subsystem which then writes
the file to disk.

From MS File Information, part of MS Management Console.

Regards,

Bill Watt
Computer Help and Information http://home.ptd.net/~bwatt/
!