posted 22 years ago
(better late than never!) I was searching the forum for an answer to this question because I have been experiencing the exact problem. It turned out to be related to my Zip Drive.
I recently had my operating system reinstalled and had to reconfigure all of my applications.
To make a long story short, I needed to place a disk in my Zip Drive in order for the error to disappear.
What helped completely remove the error was to give my Zip Drive a new drive letter designation. For example, changing from "E:" drive to "Y:" drive using the system tools made the problem go away without the need of putting a disk in the drive.
I know this response is several months LATE. However, I wanted to post what solved my problem in order to, hopefully, assist someone in the future.
ciao!
- Darrell