The existence of the MSKB article and the HotFix proves that the error exists, whether everyone has encountered it or not. Added another successfully tested version to the first post, Build 4.
I am encountering problems installing builds older than 4. I will update further once I have resolved this. This applies a patch that fixes this error most of the time. However, like the Virtual PC suggestion above, this is a workaround, not a fix. My goal is to fix the problem, not work around it or "downgrade" hardware or virtual hardware to avoid it, because I use 9x systems on real hardware. The HotFix is the right way to fix it. I have a fix! Install the Windows. I installed Memphis build Good tests!
They have the same problem as Windows There may be more but they may be harder to find. Except as noted, the Memphis Versions are shown below. The first four affected files are in various Versions of Windows In some cases, increasing the size of the Windows 95 Swap File can solve problems when running Setup.
If you bypass the Startup Disk creation screen by pressing Next, create the disk as soon as you can after your update. Click the Startup Disk tab, then click Create Disk. The procedure is easy: Restart the computer. Hold down the [Ctrl] key until you see the Windows 98 Startup menu. Select Command Prompt Only. Insert a blank, formatted floppy disk into drive A.
Virus-proof the blank disk If you use disks less often, you may forget some important considerations. First, before creating the Startup Disk, scan it for viruses. Second, after creating the disk, write-protect it. Should your problem be a computer virus, setting the write-protect tab will keep the disk from becoming infected.
Windows protection error messages A protection error will occur when the operating system has trouble loading or unloading a virtual device driver VxD. These drivers may be Windows files or third-party files.
Any info would be greatly appreciated. Oh, I've also virus-scaned numerous times and defragged numerous times too. Thanks A Lot, Mongoose. Quit all running programs, restart your computer, and then try again. If the problem persists, contact your network administrator.
Related Knowledge Base Articles How to verify name resolution for NetBackup tm systems, using the "bpclntcmd" command. Was this content helpful? Yes No Rating submitted. Please provide additional feedback optional :. Cancel Submit. You are using Microsoft Internet Explorer!
0コメント