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.win95.filediskmanage/br
>>
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.mspx
>>>
>>>
>>> "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.mspx
>>>>>
>>>>>
>>>>> "Bill in Co." <not_really_here@earthlink.net> wrote in message
>>>>> news:Ozb7eu4UFHA.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)