Iomega IDE Internal ZIP and ATAPI drivers

After I installed the Internal ZIP drive and changed the system driver to the IMGATAPI driver instead of the standard ATAPI driver, the event viewer logs Event Error 22 everytime I log in.  It says that the atapi and imgatapi driver are requesting the same IO even though the atapi driver isn't being used.  However, everything works except that the zip drive cannot eject a disk properly under Win NT 4.0.  I'm also using service pack 3.
mleeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

j2Commented:
Have you turned off the ATAPI driver in the controlpanel / devices?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mleeAuthor Commented:
The atapi driver is off and the iomega imgatapi driver is on according to the SCSI panel and in devices, atapi is not started.  
I read somewhere that the atapi driver will request extra irqs.
If this is true and the iomega driver is some sort of hybrid atapi and proprietary driver, maybe errors might occur.
0
mleeAuthor Commented:
The atapi driver is off and the iomega imgatapi driver is on according to the SCSI panel and in devices, atapi is not started.  
I read somewhere that the atapi driver will request extra irqs.
If this is true and the iomega driver is some sort of hybrid atapi and proprietary driver, maybe errors might occur.
0
pyramidCommented:
Remove sp3 and reinstall you zip drive then install sp3. We have had problem with zip drives and sp3
0
mleeAuthor Commented:
I recheck the control panel and sure enough, the atapi driver is not started, at least it says it isn't.  However, when I try to start it, it says the device has already been started.  What gives?  How do I test my theory switch the device option to boot without killing my system if indeed I need it?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.