Location of configmg.vxd

Hello all,
my 98se system is working fine. I had recently applied the
so-called "unofficial service pack". The system is stable.
http://exuberant.ms11.net/98sesp.html

I started looking around out of interest and I found I had two
versions of this file, one in windows\system and one in
windows\system\vmm32.
The one in vmm32 is 125,593 bytes, verson 4.10.2225
while the one in system is 125,057 bytes, version 4.10.2222

Msinfo32 says that the configmg.vxd in \windows\system\vmm32
is active. At least that's the newer one.

Why do I have a copy in windows\system ?
On the otherhand there are a load of VXD's that only
live in \windows\system

What is the rule, in general, of how/where these vxd's
live?
Thanks for any info.
Dave

See:
http://www.helpwithwindows.com/techfiles/vmm32.html

Your "unofficial service pack" apparently installed an updated one in the
Windows\System\Vmm32 folder. There is no reason whatever for there to be one in the
Windows\System folder, and I suggest you delete it.

quote
.....there may come a time, when one of the *.vxd files built into vmm32.vxd needs to
be updated, and Win9x provides a very simple means for this. Each system has a
\Windows\system\vmm32 directory. Any *.vxd file in this directory will be
automatically loaded and used during Win9X startup, instead of the one in the
vmm32.vxd file if it exists in both places. In other words files in this directory
take precedence over same files within vmm32.vxd.
/quote

I suggest you read the entire web page I linked above.
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm


"dave xnet" wrote in message
...
Hello all,
my 98se system is working fine. I had recently applied the
so-called "unofficial service pack". The system is stable.
http://exuberant.ms11.net/98sesp.html

I started looking around out of interest and I found I had two
versions of this file, one in windows\system and one in
windows\system\vmm32.
The one in vmm32 is 125,593 bytes, verson 4.10.2225
while the one in system is 125,057 bytes, version 4.10.2222

Msinfo32 says that the configmg.vxd in \windows\system\vmm32
is active. At least that's the newer one.

Why do I have a copy in windows\system ?
On the otherhand there are a load of VXD's that only
live in \windows\system

What is the rule, in general, of how/where these vxd's
live?
Thanks for any info.
Dave

On Wed, 8 Mar 2006 15:08:35 -0500, "glee"
wrote:

See:
http://www.helpwithwindows.com/techfiles/vmm32.html

Your "unofficial service pack" apparently installed an updated one in the
Windows\System\Vmm32 folder. There is no reason whatever for there to be one in the
Windows\System folder, and I suggest you delete it.

quote
....there may come a time, when one of the *.vxd files built into vmm32.vxd needs to
be updated, and Win9x provides a very simple means for this. Each system has a
\Windows\system\vmm32 directory. Any *.vxd file in this directory will be
automatically loaded and used during Win9X startup, instead of the one in the
vmm32.vxd file if it exists in both places. In other words files in this directory
take precedence over same files within vmm32.vxd.
/quote

I suggest you read the entire web page I linked above.
Thaks for the info.
At one time I actually knew this stuff. But not having touched,
98se for 3 years, and a short, unfortunate, episode with WINME,
I've been using XP almost exclusively.
I've forgotten all this good 9x stuff!

Dave

On Wed, 8 Mar 2006 15:08:35 -0500, "glee"
wrote:

See:
http://www.helpwithwindows.com/techfiles/vmm32.html

Your "unofficial service pack" apparently installed an updated one in the
Windows\System\Vmm32 folder. There is no reason whatever for there to be one in the
Windows\System folder, and I suggest you delete it.

quote
....there may come a time, when one of the *.vxd files built into vmm32.vxd needs to
be updated, and Win9x provides a very simple means for this. Each system has a
\Windows\system\vmm32 directory. Any *.vxd file in this directory will be
automatically loaded and used during Win9X startup, instead of the one in the
vmm32.vxd file if it exists in both places. In other words files in this directory
take precedence over same files within vmm32.vxd.
/quote

I suggest you read the entire web page I linked above.
glee,
I read the page, but unless I misunderstood, something
doesn't jive. For example,
if I use the device manager to display the driver details of
system device/system board,
it quite clearly says it's using
c:\windows\system\configmg.vxd version 4.10.2222
even though I have a newer version in
windows\system\vmm32\configmg.vxd

Some other factor at play?
Dave

"dave xnet" wrote in message
...
On Wed, 8 Mar 2006 15:08:35 -0500, "glee"
wrote:

See:
http://www.helpwithwindows.com/techfiles/vmm32.html

Your "unofficial service pack" apparently installed an updated one in the
Windows\System\Vmm32 folder. There is no reason whatever for there to be one in
the
Windows\System folder, and I suggest you delete it.

quote
....there may come a time, when one of the *.vxd files built into vmm32.vxd needs
to
be updated, and Win9x provides a very simple means for this. Each system has a
\Windows\system\vmm32 directory. Any *.vxd file in this directory will be
automatically loaded and used during Win9X startup, instead of the one in the
vmm32.vxd file if it exists in both places. In other words files in this
directory
take precedence over same files within vmm32.vxd.
/quote

I suggest you read the entire web page I linked above.
glee,
I read the page, but unless I misunderstood, something
doesn't jive. For example,
if I use the device manager to display the driver details of
system device/system board,
it quite clearly says it's using
c:\windows\system\configmg.vxd version 4.10.2222
even though I have a newer version in
windows\system\vmm32\configmg.vxd

Some other factor at play?
Dave

Yeah, that's odd. As I understand it and as the web page describes, the version in
the Vmm32 folder should be the one being loaded at startup, as files in that folder
are loaded during the boot process. A version of the file in the System folder
should not be loaded, unless I also misunderstand.

Try this....rename the version in the System folder, to configmg.vx_, then reboot,
and check the version number shown in that same location in Device Manager.
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm

On Wed, 8 Mar 2006 23:05:02 -0500, "glee"
wrote:
I read the page, but unless I misunderstood, something
doesn't jive. For example,
if I use the device manager to display the driver details of
system device/system board,
it quite clearly says it's using
c:\windows\system\configmg.vxd version 4.10.2222
even though I have a newer version in
windows\system\vmm32\configmg.vxd

Some other factor at play?
Dave

Yeah, that's odd. As I understand it and as the web page describes, the version in
the Vmm32 folder should be the one being loaded at startup, as files in that folder
are loaded during the boot process. A version of the file in the System folder
should not be loaded, unless I also misunderstand.

Try this....rename the version in the System folder, to configmg.vx_, then reboot,
and check the version number shown in that same location in Device Manager.
Glen, your hunch is right. According to device manager, it's now
using the one in the vmm32 folder after the rename.
Of course, I'm now going to check all of the vmm32 vxd
for duplicates like this just in case there's more...

Thanks for your help, it does seem most peculiar
that it works this way.
Dave

Do a google search for 'vxdfix' and find that the unofficial patch has
applied the entire VXD fix suite of seven vxd files to your machine
without your knowledge or permission. So what else did it do?

In my early days of 98 I often recommended the vxd fix, but NOT using
hot patch sources for the files like the unofficial patch does...

According to the VXD fix these two files must be located in the System
folder and not the Vmm32 folder:
vdd.vxd
vflatd.vxd

The above files won't work when placed in the Vmm32 folder, but 5 these
will:
configmg.vxd
ntkern.vxd
vcomm.vxd
vdmad.vxd
vmouse.vxd

Apparently, you've stumbled upon the default location behavior for
configmg.vxd as first loading from the System folder if there, then the
Vmm32 folder if there, and if not in either location then from the
'combined' Vmm32.vxd file itself? BTW, in the process of combining the
Vmm32.vxd file at windows installation time (first reboot), the
configmg.vxd file should have been deleted from the System folder which
means something went wrong when that was supposed to happen.

"Lee" wrote in message
oups.com...
Do a google search for 'vxdfix' and find that the unofficial patch has
applied the entire VXD fix suite of seven vxd files to your machine
without your knowledge or permission. So what else did it do?

In my early days of 98 I often recommended the vxd fix, but NOT using
hot patch sources for the files like the unofficial patch does...

According to the VXD fix these two files must be located in the System
folder and not the Vmm32 folder:
vdd.vxd
vflatd.vxd

Not according to this:

How to Repair the Vmm32.vxd:
http://www.easydesksoftware.com/news/news10.htm
quote
The file names are vdd.vxd, vflatd.vxd, and biosxlat.vxd. You can extract
each file, one at a time to the Windows\System\Vmm32 folder. This folder is
used when a vxd file needs to be added to the Vmm32.vxd file; instead of
trying to have Wininit.ini try to add the file to the Vmm32.vxd file and
risk corrupting the file, the new file can be placed here. If a file is
listed in the Vmm32Files Registry Key, Windows looks inside the Vmm32.vxd
file and in the Windows\System\Vmm32 folder for it.
/quote

Description of the Windows 95 Startup Process:
http://support.microsoft.com/kb/q174018/
quote
The real-mode virtual device driver loader checks for duplicate virtual
device drivers (VxDs) in the Windows\System\Vmm32 folder and the Vmm32.vxd
file. If a VxD exists in both the Windows\System\Vmm32 folder and the
Vmm32.vxd file, the duplicate VxD is "marked" in the Vmm32.vxd file so that
it is not loaded.
/quote
--
Glen Ventura, MS MVP Shell/User, A+


The above files won't work when placed in the Vmm32 folder, but 5 these
will:
configmg.vxd
ntkern.vxd
vcomm.vxd
vdmad.vxd
vmouse.vxd

Apparently, you've stumbled upon the default location behavior for
configmg.vxd as first loading from the System folder if there, then the
Vmm32 folder if there, and if not in either location then from the
'combined' Vmm32.vxd file itself? BTW, in the process of combining the
Vmm32.vxd file at windows installation time (first reboot), the
configmg.vxd file should have been deleted from the System folder which
means something went wrong when that was supposed to happen.

On 9 Mar 2006 00:28:28 -0800, "Lee" wrote:

Do a google search for 'vxdfix' and find that the unofficial patch has
applied the entire VXD fix suite of seven vxd files to your machine
without your knowledge or permission. So what else did it do?

In my early days of 98 I often recommended the vxd fix, but NOT using
hot patch sources for the files like the unofficial patch does...

According to the VXD fix these two files must be located in the System
folder and not the Vmm32 folder:
vdd.vxd
vflatd.vxd

The above files won't work when placed in the Vmm32 folder, but 5 these
will:
configmg.vxd
ntkern.vxd
vcomm.vxd
vdmad.vxd
vmouse.vxd

Apparently, you've stumbled upon the default location behavior for
configmg.vxd as first loading from the System folder if there, then the
Vmm32 folder if there, and if not in either location then from the
'combined' Vmm32.vxd file itself? BTW, in the process of combining the
Vmm32.vxd file at windows installation time (first reboot), the
configmg.vxd file should have been deleted from the System folder which
means something went wrong when that was supposed to happen.
Well I found another one.
ios.vxd - What's the proper location ? I take it this is NOT
part of vmm32.vxd.
I had this on my system:
ios.vxd in options\cabs 2223
ios.vxd in iosubsys 2223
ios.vxd in system\vmm32 2225

I looked in device manager primary IDE controller
driver details and saw that the version in options\cabs was
loaded. I renamed this file and rebooted. Now, the iosubsys was
being used. I renamed this and rebooted. Now the ios.vxd in vmm32
was being used, which is the newest.
But doesn't this file really belong in iosubsys?
Does it matter?
Dave

I find IOS.vxd is NOT mentioned in any Registry key, not even in...
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\VMM32Files
....So, it isn't one of the files in my VMM32.vxd.

Other than an older version in an Installation .cab, I find IOS.vxd to be ONLY in the folder C:\WINDOWS\SYSTEM\VMM32. It is version 4.10.2222. You apparently have updated beyond that.

It shows up in Device Manager as a driver for the Floppy & Hard Disk Controllers. I always thought it did that by virtue of it's inclusion in the folder C:\WINDOWS\SYSTEM\VMM32. However, by your experience, I guess it could be in any auto-run location, & it will install itself properly.

BUT...

| I had this on my system:
| ios.vxd in options\cabs 2223
| ios.vxd in iosubsys 2223
| ios.vxd in system\vmm32 2225

....I DOUBT the one in options\cabs could have installed. That isn't an auto-install location! You mean... C:\Windows\Options\Cabs? Those are just backups in there, with a purpose. Pointing SFC (System File Checker) to that folder for the purpose of retrieving a backup-- will get the one in the root & not go into a .cab for an older version.


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"dave xnet" wrote in message ...
| On 9 Mar 2006 00:28:28 -0800, "Lee" wrote:
|
| Do a google search for 'vxdfix' and find that the unofficial patch has
| applied the entire VXD fix suite of seven vxd files to your machine
| without your knowledge or permission. So what else did it do?
|
| In my early days of 98 I often recommended the vxd fix, but NOT using
| hot patch sources for the files like the unofficial patch does...
|
| According to the VXD fix these two files must be located in the System
| folder and not the Vmm32 folder:
| vdd.vxd
| vflatd.vxd
|
| The above files won't work when placed in the Vmm32 folder, but 5 these
| will:
| configmg.vxd
| ntkern.vxd
| vcomm.vxd
| vdmad.vxd
| vmouse.vxd
|
| Apparently, you've stumbled upon the default location behavior for
| configmg.vxd as first loading from the System folder if there, then the
| Vmm32 folder if there, and if not in either location then from the
| 'combined' Vmm32.vxd file itself? BTW, in the process of combining the
| Vmm32.vxd file at windows installation time (first reboot), the
| configmg.vxd file should have been deleted from the System folder which
| means something went wrong when that was supposed to happen.
| Well I found another one.
| ios.vxd - What's the proper location ? I take it this is NOT
| part of vmm32.vxd.
| I had this on my system:
| ios.vxd in options\cabs 2223
| ios.vxd in iosubsys 2223
| ios.vxd in system\vmm32 2225
|
| I looked in device manager primary IDE controller
| driver details and saw that the version in options\cabs was
| loaded. I renamed this file and rebooted. Now, the iosubsys was
| being used. I renamed this and rebooted. Now the ios.vxd in vmm32
| was being used, which is the newest.
| But doesn't this file really belong in iosubsys?
| Does it matter?
| Dave