QEMM 8.0
Allan Smith
Internet Explorer CD from Microsoft UK does not like QEMM 8.0
W 95 and QEMM 8.0 qworking fine - long time
Installed IE 3.02 - now crashes on start - error is
While initialising device IOS:
Windows Protection Error 14
Any one got any suggestions or work arounds
All I could do was remove QEMM from CONFIG
Allan Smith
John J. Felczak
Allan Smith <all...@thad.demon.co.uk> wrote in article
<33B971...@thad.demon.co.uk>...
Here are some things to try.
----------------------------------------------------------------------------
-----------
TAN 41604: While Initializing Device IOS, a Windows Protection Error
Occurred.
QEMM 97 DOS v9.0 USA
Title: While Initializing IOS, a Windows Protection Error Occurred
The information in this document refers to:
- QEMM, version(s) 8.0x, 9.0x
SYMPTOM: After you install QEMM and reboot, you get an error message
while the computer is trying to load Windows 95 that says:
While initializing device IOS
A Windows Protection Error occurred.
You need to restart your computer.
CAUSE: There are several different possible causes for this particular
problem:
1. The Mscmouse.com driver by Mouse Systems may be loaded in your
Autoexec.bat file, or Gui.exe may be loaded from the "load=" line in the
Win.ini
file. For more information about this problem, go to
http://www.microsoft.com/kb/articles/q143/0/53.htm
2. You may be loading Smartdrv.exe in the Config.sys or Autoexec.bat under
Windows 95B. The functionality of Smartdrv.exe is built into Windows 95;
therefore, place an 'REM ' in front of the statements loading
Smartdrv.exe. For
more information about this problem, go to
http://www.microsoft.com/kb/articles/q157/9/24.htm
3. You may have a Quantum Bigfoot hard disk which requires a BIOS upgrade
to work properly with Windows 95B. For more information about this
problem,
go to http://www.microsoft.com/kb/articles/q164/6/66.htm
4. Your motherboard CMOS may be configured to store information at the
15M-16M break point. If you have more than 16 Megabytes of memory on
your system, a 'hole' is created in your extended/expanded memory. This
can
cause difficulties for programs which agressively scan that area.
5. You may have a conflict with a device loading in upper memory.
RESOLUTION: To work around the problem, do the following:
1. If your situation matches any of the first three, go to the web site
indicated and
you will find information to resolve your problem.
2. If your situation sounds like cause #4, or you are uncertain, you
should refer
to your computer's manual and find out how to modify your system's CMOS
settings. Disabling the feature which loads information at the 15M-16M
level will
correct the problem.
3. If your situation sounds like cause #5, or you have tried using the
solutions
from causes 1-4, your problem can be resolved by excluding a region of
upper
memory. Refer to the file 'Exclude.tec' located in your QEMM/Technote
directory to work around the problem.
Hope this helps.
John J. Felczak
behe...@ni.net
"The more I know Windows, the more I love DESQview!"