Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

IOMEGAWARE 2.2.1 Problems

65 views
Skip to first unread message

proton

unread,
Mar 19, 2000, 3:00:00 AM3/19/00
to
After installing the new Iomegaware 2.2.1 update to my NT 4.0 system, HELL
broke loose
with all kinds of error messages with respect to drivers and services
failing to start.
After I fixed the problems, I installed Iomegaware 2.2.1 update to my second
NT workstation
(just for the HELL of it--just to see what happens)
The results were just as horrific!
Below is the procedure I used to "fix" the problems that Iomega has
generously bestowed to
all of its loyal customers.


Note:The instructions below are for a computer with the following general
configuration:
a. Windows NT 4.0 Workstation/Server service pack 5
b. PII or PIII CPU
c. PCI SCSI adapter (SIIG or Adaptec)
d. External SCSI JAZZ Drive 1 GB.
e. ATA IDE Hard Drive (no SCSI HD)
f. ASUS P2B or ABIT BE6 motherboard


Problem Description:
Version (2.2.1) of Iomgeaware performs the following for your JAZZ drive:

1. installs Zip, Click, Parallel drivers on your NT 4.0
WINNT/System32/Drivers directory
that you do not need.

Comment: The above drivers may or may not cause your SCSI peripherals to
malfunction.
(In the case of the SIIG PCI SCSI adapter, it caused the SIIG SCSI driver to
fail.

2. May attempt to change the Device status of IOMEGNT AND AIC78XX drivers
from
disabled/automatic/manual to that of BOOT.

Comment: As a result, when system boots up, the NT Service Control Manager"
reports a bevy
of service/driver error messages indicating the failure of the "ZipToA"
service
to startup, "aic78xx" and "asc" system drivers to start up, etc, etc.


Remedy: (Sould be performed only by an experienced systems administrator--er
Dude)

1. Remove the IOMEGAWARE 2.2.1 app.

2. reboot.

3. In Control Panel>>>SCSI ADAPTERS, click on drivers and remove ALL drivers
that did not
startup (Make sure they are IOMEGA related--they all begin or contain IOMEGA
attributes
SUCH AS "IOMEGA ZIP" IOMEGA CLICK!, JAZ, JET, ETC.)
If there are drivers that you are unsure about--LEAVE THEM ALONE.

2. reboot

3. In Control Panel>>>Devices>>>Startup, disable the IOMEGNT (if you have
it) device.
4. Leave the aic78xx in "BOOT" mode for now.

5. reboot

6. All error messages relating to the "ZipToA" service, "asc", "aic78xx"
should disappear.

If you have problems with your SCSI peripherals or adapter, re-install your
SCSI drivers that came with the
adapter card.

7. Re-install your earlier Iomegaware version, including any Jazz drivers
(if needed).

Comments, Notes:

A. My PII-350 with SIIG adapter would give the same errors (above) with the
aic78xx in
"BOOT", so I disabled it. Also, it did not need the NT Jazz drivers to
operate.

B. My PIII-450 with the Adaptec AHA2940, needed the aic78xx to be on "BOOT"
and also
required the re-installation of the Jazz NT drivers in the SCSI Adapters
Control panel.

C. DO NOT EVER INSTALL 2.2.1 AGAIN!

D. Personal Opinion: Its time to switch to Castlewood Orb technology!
Iomega has NO excuse for delivering this poor driver installation for
windows NT 4
systems. If this update was meant ONLY for Win2000, they did a poor job of
communicating
it to their customers.

bob bulliard

unread,
Mar 24, 2000, 3:00:00 AM3/24/00
to
I had protection fault problem with windows 98 when i initially installed
a zip drive, and the techs solution was to install iomegaware 2.2.1.

the proper way to fix the problem was to deinstall all running tasks
except for systry and explorer.and uninstall
iomegaware.then re-install iomegaware vers 1.0.
this fixed the problem...i wrote the tech back regarding the fix
and he has never written back to me with a comment about my fix..
I've never had more trouble installing a device than this one.
i'm just happy i got the zip drive free from a friend...
Hmmm...is he really a friend??
Hmmm...why did he give it to me???

i dont have too much faith in either the software or the techs

bob

this was the wrong solution... protection fault was caused


--
Posted via CNET Help.com
http://www.help.com/

0 new messages