fcassia wrote:How nice...
Safelyremove tells me that explorer is accesing the drive (actually, the only "access" is a FOLDER VIEW of drive h:\somedir open.
So I see the "process" and I say "ok, I'll let safelyremove kill it", and it proceeds to KILL THE WHOLE DESKTOP (instead of closing the folder view), so... the desktop never comes back. I'm left with the applications already open and that's it.
1. Is this working as intended?
2. If it's going to kill the whole desktop and it never comes back (XP SP2 here, FWIW), why not show a warning of some kind?
3. Why not close the folder view, rather than the whole desktop
4. Why does the "scanning" trying to find the process which is accessing the drive take so darn long? I'd use WinXP's built-in util, it takes about the same time to tell me it can't unplug the device.
Thank you very much for the suggestions. First of all you should rather close programs manually than terminate them via our program. In case of explorer.exe there is no any problems - just restart explorer (push Win+R key combination, type "explorer" in the dialog and push "OK"), but if you have running Microsoft Word document and you terminate it from our program you can lose your data.
Next, about your suggestions:
1. Yes, because the explorer.exe is a system application that handles all desktop, taskbar and "explorer folders".
2. Good idea. We can add this behaviour in one of the next versions. BTW, there was a warning before program killed explorer. Did you see it?
3. Because "the folder view" is just a part of big application - "explorer.exe", like for example our options dialog is a part of USB Safely Remove.
4. How long does it take to make full scanning on your computer?