ZIP DRIVE DOES NOT REFRESH WHEN CHANGING DISKS

I wonder if the "auto insert notification" hash in your CD-ROM might be unchecked....... and for some reason might affect "removeable" media?

Are you removing the disk by the eject button on the drive, or by right-clicking the drive in Explorer and choosing Eject?  I think that pressing the Eject button doesn't notify the OS that you've ejected the disk.  The other workaround for this is to go to My Computer or the window where the drive contents are showing and press F5 possibly to refresh the screen (or View/Refresh from the menu).  Did you install the IomegaWare from Iomega's website (www.iomega.com)?

-d

I have tried both the eject button and right clicking and the results are the same.  Refreshing the screen using view-refresh or F5 yields the same results.  Even doing a DIR at a MSDOS prompt shows the same thing.

Hmm have you or some esle set up some permission restrictions? When you say the drive works fine does that mean you can access the disk that is in it at startup and move files back and forth from it? Is this a ZIP 100 or a different model?


The Crazy One

I have administrator priveleges on this machine.  Yes, I can access the disk at startup and move files back and forth.  It is only when I change disks that the problem occurs.  Prior to installing this 250MB internal zip drive, I had a 100MB parallel port one that did the same thing.  

I suspect this doesn't apply to your case but it may be worth looking into.
http://support.microsoft.com/support/kb/articles/Q154/0/94.ASP

See this MS KB article:
http://support.microsoft.com/support/kb/articles/Q159/4/56.asp

There is a jumper on the back of the drive that needs to be set to enable "media status notification".

-d

Hi,

This should solve your problem.

The same happens to me....

...the directory listing does NOT update (refresh)
This is most likely caused by having multiple Zip Disks each of which has the same Volume Name as another disk. Take each disk, and change the Volume name.

This can be done as follows
Go to the desktop
double click "My Computer",
right click on the Zip Disk drive letter (with the disk inserted in the drive).
from the pop-up menu select "Properties" , the properties window will open.
Enter in the "Label" text box a name for the disk (8 characters or less)
Click the Apply button, then click the OK button, the window will close


Cheers,

T.

No, renaming does not solve the problem.

kingsferry:

Did you try the suggestion from the MS KB article I posted? You may also need to update/reinstall your ServicePack if your atapi.sys is the incorrect version.

-d

I think your disks are being mounted incorrectly...  I saw this once when I had Zips, but now I've forgotten the solution...  The problem was that the file system daemon thinks that they are fixed disks instead of removeable disks.  As I recall, it has to do with the way they were first fdisked and formatted...?  Argh, I'm really hoping that someone else has seen this and actually remembers.  Roadwarrior or jhance, ever see this or know what I mean?

good luck,
magarity

DOGZTAR....I haven't tried the jumper yet but I will as soon as I finish my work today.

magarity:
The article I posted refers to this in the text, it says the jumper must be set to allow it to recognize that the disk was ejected.  Interesting.  Also, it appears that there is a difference between an ATAPI Zip and an IDE Zip...I always thought they were the same thing.  Guess not.

kingsferry:
Hope it works for you!  It seems to describe the exact problem you're experiencing.

-d

Hi,

I experienced the problem using windows 95 - as a solution I also defragged and ran scandisk on the disks - this may solve your problem.

Cheers,

T.

DOGZTAR:  Unfortunately, the jumper did not work.  After installing it and starting the machine, when I doubleclick the drive icon a pop-up window says "Incorrect Parameter".

LYONST:  Running scandisk destroys the data on the zipdisks.

One more comment,  This seems to be an intermittent problem.  When I re-booted yesterday afternoon, it seemed to work fine and showed the correct contents of each disk I inserted.  This morning, it didn't (even used the same zipdisks to test it). ARRRRRGH!!!!!

Have you verified that the disk is not protected? Right-click it from My Computer, then choose Properties.  Then go to Protect and ensure the Protection is removed.

I think I asked this previously, but are you using the latest version of the IomegaWare software?

Have you tried upgrading the BIOS on your Intellistation?  What is the model type (listed at TYPE on the front/side of the system, it should be 4 numbers - 3 characters, i.e. 6123-AB4)?  If you will provide that, I will find you the current BIOS upgrade and see if there is a known issue with Zip drives that is fixed through BIOS.  Alot of problems with hardware weirdness on IBM machines are fixed with BIOS upgrades.

-d

COMPUTER TYPE:  IBM Intellistation M-PRO 6889-14U

Dogztar:  The bios upgrade seems to have cleared things up.  I will test it out more rigorously tomorrow and hopefully this problem is over.   Thanks!!!

Glad to hear it kingsferry!

-d

Hello everyone,

This question has been open for quite awhile. I am going to allow feedback from the questioner and experts. If it is not resolved, I will delete or accept an answer based on the info I have been given. Experts, feel free to offer input. I will monitor this question for a period of 5-7 days and come back and evaluate.  

I reserve the right to disallow any comments that may not have a direct conclusion

Thank you,
ComTech
Community Support Moderator

*Question Author, please return and resolve this question.

Any news kingsferry?  How did the testing go?

-d

Thanks Dogztar!  Sorry for the delay in getting back.