I continue to have problems with Opus 9, when using my many USB drives.
When I am finished using a USB drive, I do the following.
Before exiting Opus 9, I switch the focus to one of my internal drives, such as C. If I try use XP's "Safely Remove Hardware" feature, and select the USB drive in quresstion, I always get a message that "The device cannot be stopped, as a program using it".
So I shut down Opus 9, but the same error message comes up for the USB drive. So I then also right-click on the Opus icon in the lower right taskbar, and click on "exit" there. Still the same error message.
This doesn't happen on other machines I have, which use other file managers.
If you've exited Opus and still get an error saying the drive is in use, why are you blaming Opus?
Opus can't be keeping the drive in use if it isn't running. i.e. If you still get the error but dopus.exe isn't in Task Manager (ignore dopusrt.exe) then it's not Opus locking the drive.
Are you using Tortoise SVN? The TSVNCache.exe process is notorious for locking random folders/drives if you just access them. That includes drives which don't have Subversion repositories on them.
I had to write a script which kills TSVNCache.exe before ejecting any drives after I got sick of killing it manually myself.
I'm not using SVN. Actually I never heard of it so I did a Google search. And after reading that result, I still didn't really know what is was
The reason I felt it was Opus that was not releasing the USB drive, was that there was nothing else running, that I knew of, other than startup and service activities. And Opus had jsut been run.
So I ran an exhaustive series of tests, and the drive seemed to release fine via the "safely remove hardware", even when Opus or Windows Explorer had the focus on it..
Then I had another thought. I use a program called "Folder Sync" for all my backup activities. It runs via plain text scripts. So I then ran it, and when it finished, it shut down. But apparently it must be leaving something which still had its claws into my USB drive, which was the target in this situation.
So I apologize. I was incorrect in thinking that Opus was the culprit. I know the developer of that software, and I intend to contact him with that information.
