|
Error Messages and Fixes #2 |
This applies to 98 and 98
March 20, 1998 http://support.microsoft.com/support/kb/articles/q139/0/63.asp
When you start Windows 95, you may receive the following error message on a blue screen:
VFAT Device Initialization Failed
A device or resource required by VFAT is not present or is unavailable. VFAT cannot continue loading. System halted.
CAUSE
This error message can occur when any one of the following conditions exists:
The Ifshlp.sys file is missing from the Windows folder.
The Config.sys file contains a line pointing to a previous version of the Ifshlp.sys file.
The following Ifshlp.sys statement was deleted from the Config.sys file after reinstalling Windows 95:
DEVICE=<DRIVE>:\<WINDOWS>\IFSHLP.SYS
where <drive> is the drive containing Windows 95 and <windows> is the Windows 95 folder.
For example, if Windows 95 is installed in the WINDOWS folder on drive C, the line will read:
DEVICE=C:\WINDOWS\IFSHLP.SYS
The [Paths] section in the Msdos.sys file is incorrect.
A Winboot.ini file from a previous incomplete installation is present in the root folder of the boot disk.
RESOLUTION
To resolve the problem, use the method in the appropriate section below.
Ifshlp.sys File Missing from Windows Folder
If the Ifshlp.sys file is missing from the Windows folder, extract a new copy of the file from your original Windows 95 disks or CD-ROM to the Windows folder.
For information about using the Extract tool, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q129605
TITLE : How to Extract Original Compressed Windows Files
Config.sys file points to Previous Version of Ifshlp.sys file
1. Restart your computer. When you see the "Starting Windows 95" message, press the F8 key, and then choose Safe Mode Command Prompt Only from the Startup menu.
2. Use any text editor (such as Edit.com) to open the Config.sys file.
3. Remove the line that loads Ifshlp.sys. (Windows 95 automatically loads this driver when you start your computer.)
4. Save and then close the Config.sys file.
5. Restart your computer.
Ifshlp.sys statement was deleted from the Config.sys file after reinstalling Windows 95
When reinstalling Windows 95, Setup will delete the Ifshlp.sys statement in the Config.sys file and not replace it. To add the Ifshlp.sys statement back to the Config.sys file, follow these steps:
1. Restart your computer. When you see the "Starting Windows 95" message, press the F8 key, and then choose Safe Mode Command Prompt Only from the Startup menu.
2. Use any text editor (such as Edit.com) to open the Config.sys file.
3. Add the following line to the Config.sys file:
DEVICE=<DRIVE>:\<WINDOWS>\IFSHLP.SYS
where <drive> is the drive containing Windows 95 and <windows> is the Windows 95 folder. For example, if Windows 95 is installed in the WINDOWS folder on drive C, add the following line:
DEVICE=C:\WINDOWS\IFSHLP.SYS
4. Save and then close the Config.sys file.
5. Restart your computer.
Incorrect [Paths] Section in Msdos.sys File
1. Restart your computer. When you see the "Starting Windows 95" message, press the F8 key, and then choose Safe Mode Command Prompt Only from the Startup menu.
2. Type the following line at the command prompt:
attrib -s -h -r msdos.sys
3. Use any text editor (such as Edit.com) to open the Msdos.sys file.
4. Verify that the following lines in the Msdos.sys file are correct
[Paths]
WinDir=<Windows>
WinBootDir=<Windows>
HostWinBootDrv=C
where <Windows> is the folder containing Windows 95. Note that if you are using disk compression software (such as DriveSpace), you must change the drive letter in the "HostWinBootDrv=" line to the drive letter of the host drive.
5. Save and then close the Msdos.sys file.
6. Type the following line at the command prompt:
attrib +s +h +r msdos.sys
7. Restart your computer.
Winboot.ini File Present in Root Folder of Boot Drive
1. Restart your computer. When you see the "Starting Windows 95" message, press the F8 key, and then choose Safe Mode Command Prompt Only from the Startup menu.
2. Delete the Winboot.ini file in the root folder of the boot drive.
3. Restart your computer.
Diagnosis:
A system gives the following Win95 boot error (happens after the initial
Win95 logo pops up, but before actually getting into the Win95
GUI):
"While initializing device IOS: Windows Protection Error. Restart system"
After this error the machine is frozen. It can be restarted in safe mode but not in normal mode
Many of the things that didn't work in solving this problem are documented below.
Try recording bootlog.txt file to see where exactly the freeze up occurs. Create a Bootlog.txt.
Try removing all the video codecs then re-intalling them
Try copying IOS related files from Reloading Windows to a New Directory.
What did work:
The problem was remedied by renaming the following file...
C:\windows\system\iosubsys\rmm.pdr
Many of the other suggestions below might also work.
Other Possible Solutions:
Check the system.ini file for incorrect entries, rem them with a ; and reboot, letting Windows 95 recreate it.
See this article.
Err Msg: "IOS Failed to Initialize" on Boot
http://support.microsoft.com/support/kb/articles/q157/9/24.asp
Stacks are reserved memory that programs use for processing hardware events. A stack overflow occurs when there is not enough space in memory to run the hardware interrupt routines. Changing the "STACKS=" line in the Config.sys file, eliminating terminate-and-stay-resident program (TSRs), and eliminating hardware conflicts are all possible corrections for this problem.
When Windows delivers an error message related to an internal stack overflow, it is because there is not enough space in memory either set aside or available to handle the calls being made to the system hardware. There are several things to consider when troubleshooting this problem:
1.The startup file Config.sys may not be properly configured for the Windows installation. Try the following values:
STACKS=64,512 ;(this is the maximum allowed)
FILES=60
BUFFERS=40
If you are using the dual-boot capabilities of Windows, the Config.sys and Autoexec.bat files may not contain the correct configuration to run Windows. When you are dual-booting between Windows 3.x and Windows, these files may not have been renamed back to Config.dos and Autoexec.dos.
Examine the Config.sys file to determine if files such as Himem.sys or Emm386.exe are being loaded from a folder other than the Windows folder. If so, boot Windows using the Safe Mode Command Prompt Only option. Rename the Config.sys file to Config.dos and the Autoexec.bat file to Autoexec.dos and the restart the computer.
2.Some TSRs may be interfering with Windows. Disable any non-boot device drivers in the Config.sys and Autoexec.bat files. If you are installing from Windows 3.x and getting a stack overflow error, check the Win.ini and System.ini files for non-Windows-based programs or drivers loading.
3.There may be an incompatible hardware configuration. Check the port and IRQ settings of the network card, sound card, and modem. Make sure that there are no COM2/COM4 or COM1/COM3 conflicts and that no devices are sharing IRQs. Disable or remove conflicting devices.
4.The computer may need a BIOS upgrade. Check the BIOS version and contact the manufacturer of your computer for information about a BIOS upgrade.
Sometimes on a bad boot you may start getting WinPopUp messages in a
Dos Window, when in fact nothing is wrong.
Disable it
Go to your Control Panel, Add/Remove Programs, Windows Setup, Accessories,
and go down to the bottom of the list. Uncheck the Winpopup.
It may or may not work for you, but I have seen it take care of problems
in the past
But..they all use AOL 2.5
I found that one user had 760 mb tied up in the AOL cache directory!!!
Never been emptied. Went back 19 months! I am confident that when I check
the other two systems this week I will find the same thing. AOL 2.5 does
not empty the cache and when set for 1, means 1gig.
Sent By: Dave Shannon
I don't know if you ever tried this but for future reference here's an option to try before reloading. Boot into safe mode and delete everything you can under device manager. If there are duplicate entries they can cause protection errors. Then boot into normal mode and run the hardware installation wizard. You won't be able to load very many things until the primary IDE controlers are loaded but once they are you should be able to load all of the device drivers. I've had this work many times.
Advanced Power Management (APM) is a wonderful energy-saving feature that many computer systems now come with. During idle periods, this feature switches your computer to suspend mode, reducing the amount of energy it consumes without completely shutting it down. But did you know that enabling this feature on a Windows 95 system causes the Windows 95 clock to lose time? When your computer switches to suspend mode, the Windows 95 clock can slow down and possibly even stop. Fortunately, APM doesn't affect the underlying system clock, so the time loss on your Windows 95 clock isn't permanent. Simply restarting your computer will restore the correct time on the Windows 95 clock. But if you have to reboot your computer to reset the clock after every suspend mode period, it's pointless to enable APM in the first place. Here's how you can keep APM enabled without stealing time from the Windows 95 clock.
Two causes, two solutions
There are two possible explanations as to why a conflict between APM and your Windows 95 clock might exist. The first is likely to apply to older computer systems. On such systems, the BIOS (basic input/output system) might be providing support only for an older version of APM. If this is the case, you should try upgrading your computer's BIOS to resolve the conflict. Your computer manufacturer should be able to provide a BIOS upgrade for your system. The second explanation for a conflict between APM and your Windows 95 clock is that you might not have installed Windows 95 APM support. If you enabled APM in your computer's CMOS (complementary metal oxide semiconductor) settings after Windows 95 was already installed, this explanation is the more likely one. In this case, you'll have to reinstall Windows 95 in order to install APM support.
Once you've installed Windows 95 APM support, check to make sure this support is enabled. To do so, right-click the My Computer icon, choose Properties, and click the Device Manager tab.
The System Properties sheet's Device Manager tab lets you verify that Windows 95 APM support is enabled.
Next, expand the System Devices branch by clicking the plus sign next to it. Then, double-click Advanced Power Management Support. In the resulting dialog box, click the Settings tab and select the Enable Power Management Support check box, if it isn't already checked. Finally, close all open dialog boxes and then click the Start button and choose Suspend.
Conclusion
If your Windows 95 clock freezes along with the rest of your system in suspend mode, you now have two possible explanations for this problem. You also have two resolutions, so you don't have to choose between saving energy and marking accurate time.
"In use by unknown device" means that something that is not plug-and-play
compatible (perhaps in your BIOS or config.sys or autoexec.bat) is using
the resource. Since it's not plug and play compatible, Windows can't tell
who is using it
When you are viewing drives in My Computer, one or more of the drives may have an incorrect icon associated with it. When you double-click the icon to view the contents of the drive, the following error message may be displayed:
Program Not Found
Windows cannot find Autorun.exe.
This program is needed for opening files of type 'File'.
You are then prompted for the location of the Autorun.exe file.
The reason is: An Autorun.inf file exists in the root folder of the drive.
To fix this: Delete or rename the Autorun.inf file in the root folder of the affected drive.
The Autorun.inf file is used with CD-ROMs to automatically run specified
programs. When a non-CD-ROM drive contains an Autorun.inf file, AutoPlay
is started when
you double-click the drive's icon. AutoPlay attempts to load Autorun.exe
(which is not present) to read the Autorun.inf file.
If the Autorun.exe file is also present in the root folder, the actions specified in the Autorun.inf file are carried out if possible.
Incorrect MS-DOS version
Enter the name of Command Interpreter (e.g., C:\WINDOWS\COMMAND.COM)
This problem can occur if SETVER.EXE is being loaded in the CONFIG.SYS
file and has a setting indicating that COMMAND.COM should look for a version
of MS-DOS earlier than 7.0.
Boot the system with the Windows 95 Startup disk and do the following:
1. Change to the WINDOWS directory by typing the following:
cd\<Windows 95 directory name>
2. Rename the SETVER.EXE file by typing the following:
ren setver.exe setver.old
3. Remove the Windows 95 Startup disk from drive A, then shut down and restart the system. (Windows 95 loads at this point.)
4. Click the Start button, point to Programs, and then click MS-DOS Prompt.
5. Change to the Windows directory by typing the following:
cd\<Windows 95 directory name>
6. Rename the SETVER.EXE file again by typing the following:
ren setver.old setver.exe
7. Remove the COMMAND.COM entry by typing the following:
setver command.com /d
8. Restart the computer to make the SETVER changes take effect.
The above procedure allows SETVER to maintain compatibility with existing MS-DOS-based applications.
When Windows 95 is installed, the new SETVER.EXE assumes the settings of the currently loaded SETVER.EXE in an effort to maintain compatibility with existing MS-DOS-based applications.
Try this: go into Control Panel, to Add remove software. Go into the Windows Setup Tab, hilight Accessories, and choose details. In there, uncheck screen savers. Press OK, then Apply.
This uninstalls your Screen Savers.
Once that is done, go back into Screen savers, and recheck it. You will need the Win95 CD to load the screen savers again. Finally, select the 3-D text SS.
This reinstalled them.
Large
Data Transfer Using WinSock Over SPX May Not Work
Windows
95 MSDLC32 Does Not Receive Broadcast Packets
Windows
Sockets Programs Using WSIPX May Not Work
WFW
TCP/IP Files May Result in Problems with Windows 95 TCP/IP
Random
Fatal Exception Errors While Running Windows 95/98
Error
Message: This program has caused a Fatal Exception 0D...
16-Bit
DMA May Cause Static or System Hang
What
Are Windows 95/98 Fatal Exception Errors
Windows
98 Hardware.txt File Online
Troubleshooting
Windows 98 Startup Problems and Error Messages
Windows
98 Hardware.txt File Don't forget your Readme files!
Windows
98 Display.txt File Don't
forget your Readme files!
Windows
98 Setup.txt File
Don't forget your Readme files!
Q135192
- Error Message: Insufficient Memory to Initialize Windows
Q128823
- No Error Message Received When Print File Is Not Created
Q118642
- Windows 95 Err Msg: Win32 Exec App Unable to Find...
Q117509
- Windows 95 Setup Err Msg: The Path Is Invalid
Q191369
- Not Enough Disk Space Error Message During Windows 98 Setup
Q135936
- Not Enough Memory to Run MS Plus! Setup
Q124177
- Application Error: SUWIN Caused an Illegal Instruction
Q135962
- Disk Tools Run by System Agent Pause for User Input
Error:
Unable to add entry to AutoCorrect due to insufficient memory.
Error:
There is insufficient memory. Save... (due to low system memory).
Error:
Out of memory starting application (due to insufficient disk space).
Error:
There is not enough available disk space to run Word (due to low space).
Error:
This program has performed an illegal operation...(due to unknown cause).
Nothing
happens when trying to print due to insufficient space in Excel 97.
Q186892
- Windows 98 Fat32ebd.txt File
Q232681
- Windows 98 Second Edition Updates Setup.txt file
Windows
98 Setup.txt File
Windows 98 Setup.txt file contains important information you should
read before you install Windows 98.
Q179756
- Windows 98 Setup.txt File
Q232018
- Windows 98 Second Edition Setup.txt File
When this error aperes then u will get a realy though time to reboot your puter (it takes around 10 to 30 min to reboot the computer). to fix this u got to add a file in the register directory. do as folows and u will get rid of the problem:
Open Notepad.exe and there u type exactly as folows
-----------------------------------------------------------------
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLE]
"EnableRemoteConnect"="N"
-----------------------------------------------------------------
2. Name the file DisbleAutoConnect.reg and store it under C:\
3. Under the START button you open RUN
4. Type DisbleAutoConnect.reg in the RUN window and then u klicks the
button Run.
5. When the system asks you if you wants to add it to the Register
you answere with klicking on the button OK ( or in some cases YES)
6. The problem is now fixed but i sugests that you reboot the computer
and takes a look! it should now reboot without any problem....
Note: I have not tried this!!
Courtesy of Thomas Stridh