VWYN32.VXD or VWIN32.VXD bootup problem??
I've got a VERY strange problem.
THIS HAPPENED BEFORE AND AFTER A COMPLETE
FORMAT AND REINSTALL!!!!
of Windows95B(fat32), Windows complains
that the registry or system.ini has a reference to VWYN32.VXD, but this VXD file
isn't there (C:\WINDOWS\system\VMM32\VWYN32.VXD. In fact, there are only four
*.VXD files in that directory, and none of
them is VWYN32.VXD. I searched system.ini and the registry and there is no reference to VWYN32.VXD. There is a reference to VWIN32.VXD, which is awful close, in
VMM32 somewhere in the registry. VWIN32.VXD
doesn't exist on the machine either. I tried
deleting the registry reference to VWIN32.VXD, but this didn't change anything.
I'm trying to find out what VWYN32.VXD is.
The machine operates fine except for having
to a hit continue on every boot....
I have that file on my system in the registry under Current User/Software/Microsoft/Windows
/Explorer/Doc Find Spec MRU, but nowhere else
Don't know what else to tell you, just thought I would let you know where it's supposed to be. Actually, you could rename system.ini and win.ini with different extensions from DOS and reinstall WIN. Maybe that will correct it.
Dean, I found those files references in two locations on my machine, 1 st under current user/ and then under key user/ in the registry
Thank you very much for your replies.
I'm assuming that you guys have actually
found VWYN32.VXD, not VWIN32.VXD, which
is in every system, I assume. If so,
does VWYN32.VXD actually exist on your
drive somewhere? Would you be willing to
e-mail me a copy of your VWYN32.VXD?
Again, thanks for your help.
I've got it fixed now. I did find a reference in the registry- it was in
Services\VxD\VWYN32 ... within that there
was a reference like *vwyn32
I delted that entry and all fixed!!
I wasn't finding it searching the registry
before, because I was searching for vwyn32.vxd.
It remains to be learned what in the world
vwyn32.vxd, especially as my above postees
have found references in the registry with
no actual file on the machine. Also very
strange since the problem occured on a
CLEAN FORMAT AND INSTALL of 95. I think
the error showed on the first reboot during
installation. I had read somewhere that
someone thought this error had to do with
FAT32, and that some versions of Win95
don't work perfectly with FAT32. (Of course
I know that 'a' version 95 doesn't support it, but these people meant that some versions
of 95 2.xxx have problems with FAT32.
Many thanks to Susan and Marc. Fixing the
problem came down to searching the registry
without the .vxd.
Actually, there was one further oddity.
After fixing the problem, we went to install
Office97 Pro. It gave all kinds of error
messages about vxds and refused to install
(including something about vmm32.vxd or vwyn32.vxd, I'm not sure which, since I didn't do it myself.)
I tried reinstalling office again after
rebooting. No problem that time and all
I have problems presently with some *vxd files like vcache, vfat, vflatd and many others when I tried to boot up Win95 overclocked to 450. Only in this situation the system complained about those virtual drivers.
Also although the files were indeed mentioned in the system.ini section [386Ehn] they were not anywhere in the system. Very strange for me.
I have downloaded those files but Win95 mentioned others and did not boot up.
When I ran the system at 400 or 420 it boots up normally.
Hope someone can put to light on these virtual drivers stuff.
New Security Features Planned for Firefox 4
Another Laptop Theft Exposes 21K Patients' Data
Oracle Hits to Road to Pitch Data Center Plans
Microsoft Preps Array of Windows Patches
Microsoft Nears IE9 Beta With Final Preview
Simplified Analytics Improve CRM, BI Tools
Android Passes RIM as Top Mobile OS in 2Q
VMware Updates Hyperic System Management
File Monitoring Key to Enterprise Security
LinkedIn Snaps Up SaaS Player mSpoke