Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Updated Imogaware or patch causing error msg. on boots

Posted on 2003-11-28
8
529 Views
Last Modified: 2012-05-05
I have a Imoga zip 250 drive.  I recently purchased a new Netvista and installed the drive on it stupidly using the Imoga ware that came with the drive that was downlevel.

I noticed that winxp saw the drive as a "100" instead of a "250".
I went to Imoga's website and saw that they had new Imogaware for the drive (250-Parallel). So I down loaded it and a "patch" that they said they needed for the parallel zip box.

I uninstalled the drive in device mgr, uninstalled imogaware in the remove software and disconnected the drive and rebooted.
It was gone and so I installed the new soft ware and powered down and installed the zip drive and powered up. It came up with this message:

We are sorry if we interuped your work but the program can not find the following: Imgstart.exe, AppVer 7.002 - Mod name IOready.dll
 ModVer 4.11.93 offste 00009fb4. Followed by a dump of additional hex info.

I emailed Imoga and they said to call them. I have been trying to get a person to talk to for a couple of days. I can't stay on the phone long enought evidently or there is really no human beings working there.

Any ideas or such will be appriciated. I have removed and reinstalled in all type of combinatons and the msg still comes up on boot. The drive is now identified correctly in My Computer and Windows Explorer.

It also works ok except I am not sure if it is running as fast as it did on my old 486-win95 machine.

Thanks in advance

Papa Ray
P.S. I am not trained on the registry.
0
Comment
Question by:paparay
  • 4
  • 3
8 Comments
 
LVL 23

Expert Comment

by:slink9
ID: 9843632
I recently tried to run IOmegaware on a Win2k machine and it qouldn't run.  It probably won't run on XP either.
0
 

Author Comment

by:paparay
ID: 9844188
IOmegaware will run, but the older (driver, I guess) release in windows xp identified it as a 100mb and the new release of IOmegawre does help xp identify it as a 250mb zip. Its the message that comes up that bothers me I don't know of its importance. Its a minor thing to say "OK" but I would like to resolve it. The people at Imega won't answer my emails and the phone support is awful in that I can't stay on the phone long enough. I have tried several times. I guess they let everybody off for the holidays.

I have an idea that the old stuff is not being deleted in the registry but I don't have a clue when it comes to that area.

Papa Ray
0
 
LVL 23

Expert Comment

by:slink9
ID: 9845030
If you are only getting a message then that is better than what I got.  I was getting terminal errors and reboots.
I can't find anything relating to IOmega and XP.  I would suggest ditching the zip drive and getting a CDRW.  You will have more storage space per drive and a much cheaper price on the media.  Since a zip drive is very old technology it really isn't worth playing with.
0
The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

 

Author Comment

by:paparay
ID: 9845324
Hi, Thanks for your comments and info.

Yes, I have considered getting a CDRW, but at the moment I am not able to. I guess I will just have to live with this until I can afford a different solution.

Thanks
Papa Ray
0
 
LVL 23

Expert Comment

by:slink9
ID: 9845807
CDRWs are quite cheap now.  You can get one for as little as $40 if you keep an eye on the Staples and CompUSA ads.  Probably even less.
0
 

Accepted Solution

by:
paparay earned 0 total points
ID: 9872392
I finally got Iomega support. We cleaned out the registry by hand of all Iomega. We then reinstalled with the latest IOware and drivers.

The boot up error is gone but windows insists on identifing it as a "100" zip drive instead of a "250". But the drive works ok.

So this request for help is terminated. I repaired (with Iomega) the offending error message.

Papa Ray
0
 

Author Comment

by:paparay
ID: 9909500
Please close this question as being unsolved by outside help. Solved by user with question.
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Most of the time we are in fix when all of sudden our systems behave weirdly.  Such problems cost time and effort... so it's best to take some preventive actions so that we can avoid such issues or overcome such problems more easily. Preventive M…
Today, still in the boom of Apple, PC's and products, nearly 50% of the computer users use Windows as graphical operating systems. If you are among those users who love windows, but are grappling to keep the system's hard drive optimized, then you s…
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.

789 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question