|
Document #2066
Revision 002
General Windows 95 and 3.1x troubleshooting for Zip
This document applies to the following:
Operating System: Windows 95, 3.1x
Device
Type: Zip 100 Parallel Port, SCSI, IDE, ATAPI
Software Version: Iomega Tools
5.x
If you are using Windows 3.1x...
Windows
3.1x can be run in standard mode to determine if there is a conflicting driver
(Windows 95 uses Safe Mode). To start Windows in standard mode, type WIN /S
(Windows 3.1) or WIN /D:T (Windows 3.11) at the C:\ prompt. If Windows
is unable to run in standard mode, change the video display to standard VGA. If
Windows will still not run in standard mode, there may be a problem with the
Windows environment, contact Microsoft or re-install Windows (Iomega technicians
are unable to troubleshoot the Windows environment).
If you are using Windows 95...
Although
Windows 95 can not be run in standard mode, conflicting drivers can be found if
Windows 95 is run in MS-DOS mode). To determine if there is a conflicting
driver in Windows 95, use the following steps:
- Restart Windows in MS-DOS mode by clicking on Start
and then selecting Shut Down. From the prompt select Restart
in MS-DOS mode.
- Insert the Zip installation floppy diskette into your A:
drive and type A:Guestfollowed by the <Enter> key at the
C:\ prompt.
- Once a drive letter has been assigned, try accessing your
Zip drive.
- If you are able to access the drive and disk, there is a
conflicting driver within Windows 95.
Finding conflicting drivers...
If
the problem is resolved by running Windows 3.1x in standard mode or Windows 95
in MS-DOS Mode, there is a conflicting driver either in the WIN.INI or
SYSTEM.INI file.
To locate conflicting drivers in the WIN.INI...
- From within Windows select Start (File
in Windows 3.1x) then Run.
- In the Open box (Command Line
in Windows 3.1x) type SYSEDIT then select OK.
- Locate the WIN.INI file and remark out the Run=, Load= and
Device= lines by placing two semi-colons (;;) in front of these lines.
- Select File then Exit,
save the changes when prompted and restart Windows.
- If the problem is resolved, then there is a conflicting
driver in the WIN.INI file. Remove one set of semi-colons from either the
Load=, Run= or Device= line, restart Windows and try the drive again. If
problem is still not resolved, remove a second set of semi-colons. Once the
problem is resolved, the last set of semi-colons removed indicate the
conflicting driver.
To locate conflicting
drivers in the SYSTEM.INI...
- From within Windows select Start (File
in Windows 3.1x) then Run.
- In the Open box (Command Line
in Windows 3.1x) type SYSEDIT then select OK.
- Locate the SYSTEM.INI file and remark any .386 drivers
within the [386Enh] section by placing two semi-colons (;;) in front of any line
within the [386Enh] section that ends in .386.
- Select File then Exit, save the changes
when prompted and restart Windows.
- If the problem is resolved, then there is a conflicting
driver in the SYSTEM.INI file. Remove one set of semi-colons from one of the
.386 drivers, restart Windows and try the backup software again. If problem is
still not resolved, remove a second set of semi-colons. Once the problem is
resolved, the last set of semi-colons removed indicate the conflicting driver.
Once the conflicting driver is found, contact the manufacturer of the
driver to obtain an updated version or leave the semi-colons in front of the
conflicting driver when making backups.
If the above outline does not resolve the problem, Windows or the
backup software may be corrupt. First, delete and re-install the backup
software. If the problem is still un-resolved, it may be required to delete and
reinstall Windows. See other documents related to the problem before deleting
and reinstalling Windows.
|
