I hope I’m not getting boring by sending too many inquiries. Truly speaking, I’ve found this site to be the most helpful and useful on the net. I’m afraid I’ll again raise the famous issue of Windows boot problems. My first boarding dealt with the same issue. I received several suggestions by experts on Computing.net and had tried them all, including Bootlog Analyzer to see the delays, disabling Windows startup sounds, installing StartupCop, etc.. But I’m still facing the same problem. My computer, which is running Win98 SE, SOMETIMES freezes when Windows is loading. Now a new problem has lately appeared: When starting Windows, it SOMETIMES reboots by itself !!!! I visited http://www.easttexaschat.com/_tips/VxD_drivers.htm and found that a “Win 98 Bug with Generic VxD Drivers” could be the problem that makes Windows hang up, and the proposed Tip said the following: “Locate the Win98_47 and Win98_48 CAB files. The default location is: C:\Windows\options\cabs. However, some OEMs do not install them on your drive because of the space consumed. Extract vcomm.vxd, vdd.vxd, vflatd.vxd, vdmad.vxd, vmouse.vxd, configmg.vxd, and ntkern.vxd to \WINDOWS\SYSTEM directory. Close Windows Reboot Use the above sequence to check the same device, it should now be: C:\Windows\System\configmg.vxd. And no more instances of vmm32.vxd!” But I failed to locate the “Win98_47 and Win98_48 CAB files ….. the default location is: C:\Windows\options\cabs……”. I used for this purpose Windows Explorer and the Find Files or Folder option, but similar folder was found. Can you please tell me how to locate the above mentioned folder, and whether this “Tip” is functional ?? I avail myself of this opportunity to renew to all computer experts my highest consideration. MAK

If they are not in the directory specified they will be on your 98 CD - in the win98 directory. And yes, this tip will probably work. Good luck.

First of all if your computer is not a factory direct you won't find the above mentioned: C:\windows\options\cab. This means, is your computer a: Dell, Gateway, Compaq, HP? And is there any chance it was ever formatted not using the "easy quick restore disks"? If it was, you won't find those files. Best best is to follow Response #1. Get your hands on a win98 CD and look in the win98 folder on the CD. Other than that not sure what other help can be provided to you. If you would give us a little more information about your pc, other than: ["My computer, which is running Win98SE"]... well then maybe we could provide a litte better direction to head you in for the information you seek. Hope you understand.

Here's the link from http://www.speedguide.net that explains how to do what you're doing: http://www.speedguide.net/Windows/win_bugs.shtml If the Windows 98 files have been installed on your hard drive, go into Windows Explorer root directory and look for a WIN98 folder or something similar to that. If it's there, open it and you'll see a list of CAB files. If the Windows 98 files are not on your hard drive, fire up your Windows 98 CD and browse to the WIN98 folder, then copy that folder into the root directory. From now on, whenever you have need to extract or copy some Windows 98 files, just browse to or type in C:\WIN98.

It's an Urban Legend. Even the originator now admits that he was wrong. There is no BUG in windows, with missing vxd files. If you wish to confirm, don't use the inane, and incorrect logic due to not understanding the architecture, and reboot with a boot log enabled. AND, by following the instructions to reload these vxds from the CABs or windows CD, can screw up your system, since these may be OLD files you are reloading, that will clobber newer files, installed as a result of a windows update.

First of all, THANK you very much for the attention given to my inquiry. But I’m m afraid things are getting rather confusing for me with these inconsistent opinions about “Win 98 Bug with Generic VxD Drivers” could be the problem that makes Windows hang up. While (Roc), (Terri) and (Frank Lavallee) recommended the tip mentioned above, (Hmmm)’s response stressed that “reloading these vxds from the CABs or windows CD, can screw up my system, since these may be OLD files you are reloading, that will clobber newer files, installed as a result of a windows update.” I also visited http://www.speedguide.net/Windows/win_bugs.shtml as recommended by Frank Lavallee. It also said there’s a Bug in Win 98 VxDs. Now a beginner like myself will certainly get confused: Is there any risk of reloading these VxDs …. Could you please explain !!! If the Bug really exists and I want to copy the CAB files, how to copy that folder into the root directory ?? Besides, my PC is not a factory direct, i.e. it’s not a Dell, Gateway, Compaq, HP? However, the following details may better explain the computer I’m using: - Operating system: Windows 98 SE - CPU : AMD-K6 II (500 MHz) - Physical memory (RAM): 128 MB – Cache memory: 512 k - FIC PAG-2130 motherboard with integrated TRIDENT AGP video card (8 MG). - Award Module BIOS v4.51PG, Version SB411 – HD: 15 GB Again, your attention to my inquiry is highly appreciated.

See the last question on this site. http://members.home.net/revolutn/vxdfaq.html This is the guy who originated this "infamous" fix, who now admits that the files "really aren't missing", BUT he still recommends loading them to stop blue screens. (no logic here). As noted above, if you run a boot log, you will see that all of the vxdst that this "fix" copies, are actually being loaded already. This started on Win95 with a gross misunderstanding of how VMM32.vxd worked. These files REALLY aren't on the harddrive. They are part of VMM32.vxd. However, these files can be "overridden" if a file of the same name exists in \windows\system\vmm32. It is this mechanism that MS uses, in the event that one of the VMM32 files requires updating. As pointed out by Hmmm, if you reload one of these from the WinCD (or CABs), and the file already exists (due to an update), in this directory, you will be replacing it by an old, outofdate file. Some people swear that this "fix" solves BDODs, but if it does, it has nothing to do with bugs or missing files. In regard, to the freeze at startup, browse to \windows\applog (hidden directory), and delete all files. If you use startup cop and disable ALL programs, does it still freeze?