Additional and important info:
The 0 KB files are called oem**.inf where the ** are numbers.
Zee
Main Topics
Browse All TopicsGetting msgsrv32 caused a general protection fault at setupx.dll on startup. Windows 98SE. A window displaying "New hardware found" is displayed, but hangs.
Able to start is safe mode, but not in "normal" mode.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Have you just installed Win98SE?
During setup, Windows uses older Windows 3.1 versions of Setupx.dll, User.exe, Gdi.exe, and Krnl386.exe that are extracted from CD:\win98\Mini.cab. These files are only used for the "safe mode" type of 640 x 480 display DURING setup, but when the computer is then rebooted for the first time into proper Windows, these files are replaced by the correct Windows 98 versions.
Coincidentally, that first reboot would be about the time these files would be getting replaced, which is why I am wondering if this is a post-setup issue. Incorrect (ie. older) versions of these files in full normal Windows will cause such GPF's and other errors in Full or Safe Mode after Windows is installed.
I would suggest doing the following, at least just to eliminate this possibility:
1. Boot the computer to a Win98 boot floppy
2. Choose the "With CD-Rom Support" option.
3. Change drive to the CD-Rom's drive letter (will be one higher, eg. E: if it was D: in Windows) by typing the command:
E: and pressing Enter
4. change directory to the "win98" folder of the CD by typing the command:
cd win98
5. The DOS Prompt should now show E:\WIN98>
6. Type the following command:
extract /y precopy2.cab\setupx.dll /L c:\windows\system
7. Remove the boot floppy and power off, then try to reboot.
8. Any errors about the other files mentioned above will confirm my suspicion, and we can provide the names of the *.cab folders on the CD containing them so you can extract them.
It is notable that Windows 98 First Edition extracted the old file versions when the System File Checker was run, or when the Extract command was used with the switch telling it to search all *.cab files, because it found them first in Mini.cab. This was fixed in Win98SE, but could still be a problem in DOS from a Boot Floppy, hence the need to specify Precopy2.cab.
Correction:
I said (quite stupidly and obviously):
"Coincidentally, that first reboot would be about the time these files would be getting replaced".
What I meant to say was:
"Coincidentally, the hardware detection phase at first reboot would be about the time these files would be getting replaced".
Duh! :-)
Glad you got this sorted out, Gerry.
In case anybody happens upon this page, I'll correct the DOS Extract command I gave earlier. Leave a space after the name of the *.cab file to access and the file to extract from it, and not a \ as I showed originally.
extract /y precopy2.cab setupx.dll /L c:\windows\system
Business Accounts
Answer for Membership
by: blue_zeePosted on 2007-09-27 at 13:13:38ID: 19974380
Make sure you can see all files and folders.
Then check your C:\Windows\inf folder for 0 (zero) KB files and delete them ALL (the 0 KB only!).
Restart and test.
Zee