| Advanced
windows troubleshooting |
| |
|
|
|
| |
| .... |
[win
95] DriveSpace
errors
|
When
you perform a DriveSpace
operation that requires
Windows 95
to restart, Windows 95 may
be unable to restart in
mini-Windows mode,
causing the operation to
fail. You may receive an
error message similar
to one of the following
messages, or your computer
may stop responding
(hang).
-
DrvSpace caused a General
Protection Fault in module
W31SPACE.EXE
- DrvSpace caused a Page
Fault in module W31SPACE.EXE
- Error Loading PROGMAN.EXE
- Error Loading GDI.EXE
Error Loading USER.EXE
- Error loading VGA.DRV
- Cannot start Windows in
standard mode
- Segment load failure in
W31space.exe
- Standard
Mode:
Bad
fault
in MSDos
Extender
|
|
|
Problem Source
This
problem can occur if the
files in the hidden Failsafe.drv
folder or the
Mini.cab file in the Windows\System folder are
damaged. These files are
required for Windows 95 to restart in mini-Windows
mode.
|
|
| |
Solution To
resolve this problem,
follow these steps:
1. Restart your computer at
an MS-DOS prompt. To do so, press the
F8
key when you see the "Starting
Windows 95" message, and then choose
Command
Prompt Only from the Startup
menu.
2.
Copy the Autoexec.bat
and Config.sys
files from the hidden Failsafe.drv folder on the physical boot drive
(usually either drive C or the host for drive
C if drive C is compressed) to to
the root directory of drive C,
replacing the files that are already there.
To
copy the files, type the
following commands
copy
<drive>:\failsafe.drv\autoexec.bat
c:\ /y
copy <drive>:\failsafe.drv\config.sys
c:\ /y where
is
the physical
boot drive. For more refer
to the command
reference for using
DOS.
3.
Remove the Failsafe.drv
folder from the physical
boot drive (usually
either drive C or the
host for drive C if drive
C is compressed). To do
so,
type the following command
at an MS-DOS command prompt
deltree <drive>:\failsafe.drv
where is the physical
boot drive.
(If the deltree gives
you "bad command or file
name" as in more recent
version of windows, then
use the del
command.")
|
|
|
Important
note:
The Failsafe.drv folder may
contain drivers necessary
for
troubleshooting if this procedure
does not correct the problem.
You should
copy the Failsafe.drv folder
and all its contents to another
drive or folder
before deleting it.
4. Copy the Mini.cab file from your
original Windows 95 disks or CD-ROM to
the Windows\System
folder.
NOTE: The Mini.cab file is located on
disk 1 of the standard 3.5-inch Windows 95 disks, or
in the Win95 folder on the Windows 95 CD-ROM. You
can copy this file using Windows Explorer or the COPY
command.
You do not need to use the
EXTRACT command with this
file.
If
you are using Microsoft Plus!
for Windows 95 and you do
not have
access to your original Windows
95 disks or CD-ROM, you can
extract the
Mini.cab file from the Microsoft
Plus! disks or CD-ROM. The
Mini.cab file is
located in the Plus_2.cab
file on the CD-ROM, or in
the Plus_1.cab file on
|
|
| |
| .... |
Cannot Start Windows 95 After
Using the SYS
|
Command
SYMPTOMS When you use the SYS
command to replace the
windows 95 system files on your
hard disk, the Msdos.sys file
may not
be replaced, or may be replaced
with an incomplete Msdos.sys file
that
contains only the text ";SYS."
If
the existing Msdos.sys file on
your hard disk is damaged and
is not
replaced by the SYS command, or
if the existing Msdos.sys file
is replaced
with an incomplete Msdos.sys file,
Windows 95 may boot only to a
command prompt the next time you
start Windows 95. If the existing
Msdos.sys file is not damaged
and is not replaced by the SYS
command,
|
|
| |
Problem
source
If
the SYS command (Sys.com) included
with Windows 95 determines that
the existing Msdos.sys file
is from MS-DOS version 6.22
or earlier, it replaces the
existing Msdos.sys file with
an incomplete Msdos.sys file
that contains only the text
";SYS." If the SYS command
is unable to determine that
the existing Msdos.sys file
is from MS-DOS version 6.22
or earlier, it assumes that
the file is a valid Windows
95 Msdos.sys file and does
not replace it.
|
|
| |
Solution
To
work around this issue, manually
rebuild the Msdos.sys file on
your hard
disk so that it includes the location
of your Windows folder and the
Windows
95 system files. To do so, follow
these steps:
1.
Remove the system, hidden,
and read-only attributes from
the msdos.sys file in the
root folder of the boot drive.
To do so, type the following
command at the command prompt
attrib
-s -h -r <drive>:\msdos.sys
where is the physical
boot drive.
NOTE: If drive C is compressed and is
currently mounted, the Msdos.sys file is located on the
host drive for drive C. If drive C is not compressed or
is not
currently
mounted, the Msdos.sys file is
located on drive C.
2.
Rename the Msdos.sys file using
the following command,
ren <drive>:\msdos.sys
msdos.xxx
where <drive>
is the physical boot drive.
3. Use any editor (such as Edit.com)
to create a new Msdos.sys file
that contains the following text:
|
|
| |
[Paths]
WinDir=<drive>:\<windows>
WinBootDir=<drive>:\<windows>
HostWinBootDrv= <bootdrive>
where <drive> is
the drive containing the Windows
folder, <windows>is the
Windows folder, and
<bootdrive> is the physical
boot drive.
NOTE:
You can also add an [Options]
section to the Msdos.sys file
with
additional settings to personalize
the boot process. For example,
if you
installed Windows 95 on drive
C in a folder named Windows and
drive C is
not compressed, the Msdos.sys
file should contain the following
lines: |
|
| |
[Paths]
WinDir=C:\WINDOWS
WinBootDir=C:\WINDOWS
HostWinBootDrv=C
[Options] BootGUI=1
;
;Some
programs on this system expect the Msdos.sys file to be
at least
;1024 bytes in length;
hence, the following lines create
an Msdos.sys
;file that is greater than 1024
bytes in length. These lines are
not
;needed for Windows 95
to boot or run.
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxa
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxb
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxc
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxd
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxe
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxf
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxg
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxh
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxi
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxj
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxk
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxl
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxm
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxn
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxo
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxp
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxq
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxr
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxs
4.
Save and then close the Msdos.sys
file.
5.
Restart your computer.
|
|
| |
Explanations
When
you use the SYS command to replace
the Windows 95 system files
on your hard disk, the SYS command
replaces the existing Msdos.sys
file only if it determines that
the file is from MS-DOS version
6.22 or earlier. To determine
if the Msdos.sys file is from
MS-DOS version 6.22 or earlier,
the SYS command checks to see
if the first byte in the file
is 0x3Bh, 0xE9h, or 0xEBh. These
hexadecimal values indicate
that the file is a binary file
and that it is likely a invalid
Windows 95 Msdos.sys file.
|
|
| |
This
logic is intended to prevent the
SYS command from replacing a valid
Windows 95 Msdos.sys file. However,
when the SYS command replaces the
existing Msdos.sys file, it replaces
the file with an Msdos.sys file
that contains only the text ";SYS."
Creating an Msdos.sys file without
a [Paths] section is appropriate
when you are replacing the Windows
95 system files on a floppy disk,
because the location of the Windows
folder may not be the same on the
computer used to create the bootable
floppy disk and the computer on
which the floppy disk is used. Creating
an Msdos.sys file without a [Paths]
section is not appropriate when
you are replacing the system files
on a hard disk, but the SYS command
cannot distinguish between a floppy
disk and a hard disk. |
|
| |
If
the first byte in the existing
Msdos.sys file is not one of the
hexadecimal values listed above,
the SYS command assumes that the
file is a valid Windows 95 Msdos.sys
file and does not replace it.
Therefore, if the existing Msdos.sys
file is an ASCII text file, or
if it is damaged (and the first
character in the file does not
happen to be one of the hexadecimal
values listed above), the file
is not replaced.
|
|
| |
| .... |
Slow to shutdown SYMPTOMS
|
When
you shut down or use the Suspend/Resume
feature in Windows 95 or Windows
95 OEM Service Release 2 (OSR2)
and you are connected to a network,
the shutdown, suspend or resume
may seem to take a long time.
Problem
Source
This
behavior can occur if LM Announce
messages are being generated.
Solution
To resolve this issue, follow
these steps:
1.
In Control Panel, double-click
Network.
2. Click File And Print Sharing
For Microsoft Networks, and then
click Properties.
3. In the LM Announce box, click
No.
4. Click OK.
5. When you are prompted, restart
the computer.
|
|
| |
| .... |
Why
does my computer
lockup?
|
This
can be caused by one or both of
two suspects
1: software or
2: hardware.
If
you have a piece of software that
gives you problems run scandisk
and defrag then reinstall the
program, then if you still have
problems contact the manufacture
they will be the best place to
start. If they cannot help you
then don't use it, return it to
where you got it, get another
program .
TIP:
If you have a hardware problem
it will usually show up in more
than one program. For example:
If your sound card (or any piece
of hardware) will work in one
program but it will not work in
another your hardware is probably
OK check the software, but if
your hardware will not work in
any program then it is suspect.
|
|
| |
| .... |
Error Message Err Msg:
|
Explorer
Caused a Divide Error in Module
Shell32.dll SYMPTOMS When you
try to open an icon in Windows
95 (particularly, the My Computer,
Microsoft Exchange Inbox, Recycle
Bin, or Control Panel icon) you
may receive the following error
message:
Explorer:
This program has performed an
illegal operation and will be
shutdown.
If
you click the Details button,
the following information is displayed:
EXPLORER caused a divide error
in module SHELL32.DLL at 0137:7fe1402f.
|
|
| |
Problem
Source
This
error may be caused by a combination
of the following conditions: The
horizontal spacing for icons is
set too high or set to 0. You
are using a video resolution of
640 x 480. The taskbar is placed
at the left or right edge of the
screen, and has been expanded
to larger than the default size.
Solution
To
correct this problem, use any
one of the following methods:
Decrease the horizontal icon spacing.
To do so, follow these steps:
1.
Use the right mouse button to
click an empty area on the desktop,
and then click Properties on the
menu that appears.
2. On the Appearance tab, click
Icon Spacing (Horizontal) in the
Item box, and then decrease the
value in the Size box to value
greater than 0.
3. Click OK.
Change
the video resolution so that it
is greater than 640 x 480. To
do so, follow these steps:
1.
Use the right mouse button to
click an empty area on the desktop,
and then click Properties on the
menu that appears.
2. On the Settings tab, move the
Desktop Area slider one notch
to the right.
3. Click OK.
1. Decrease the size of the taskbar.
2. Move the taskbar
from the left
or right edge
of the screen
to the top or
bottom of the
screen.
|
|
| |
| .... |
Fatal exception Error Messages
|
When
you attempt to start Windows or
an application inside of Windows,
you may encounter errors similar
to the following:
A
fatal exception YYYY has occurred
at xxxx:xxxxxxxx
Fatal
exception errors are codes returned
by a program in the following
cases:
1
Access to an illegal instruction
has been encountered
2 Invalid data or code has been
accessed
3 The privilege level of an operation
is invalid When any of these occur,
the processor returns an exception
to the operating system, which
in turn is handled as a Fatal
Exception Error.
In
many cases the exception is non-recoverable
and the system must either be
restarted or shutdown, depending
upon the severity of the error.
In the following example of a
Fatal Exception error A fatal
exception YYYY has occurred at
xxxx:xxxxxxxx the YYYY; represents
the actual processor exception
from 00 to 0F. The xxxx:xxxxxxxx
represents the enhanced instruction
pointer to the code segment and
the 8-bit address is the actual
address where the exception occurred.
Windows does not cause these errors,
but has the exception handling
routine for that particular processor
exception, which displays the
above message.
|
|
| |
If
a Windows 95 file or program gets
overwritten or corrupted use Windows
95 to fix it, Run Setup.exe from
wherever you installed it (CD-ROM
or floppies) and select "Custom"
and "Restore Windows files that
are changed or corrupted" if asked.
|
|
| |
|
|
|
|
 |
|
