> 1. and 2. solved, but I would suggest to give the user some kind of indicator whether the disk is 'catalogued'.
Thanks for the tip, will think about it.
> 14 minutes later, forced eject w HotSwap -> windows error: 'The device WDC WD20EARS-00MVWB0 cannot be uninstalled right now because the device requested a system restart'
> drive disappears from drive list in device manager and from the HoSwap drive list
> drive still showing up in HDS drive list
> clicked on "update disk information" in HDS -> no change
If this happens, then the disk drive is still present in the system. Please check Windows Disk Management: probably that would show the disk drive (even if it is no longer displayed in the device manager, as it is about to remove - but still present).
In this case yes, Hard Disk Sentinel also still "see" the drive and display it as a present disk drive.
> drive doesn't show up in the list of offline drives either
While the disk drive is present in the system, it is not in the list of "offline drives", it is normal.
> terminated HDS, start program again -> drive is still listed like before (!)
It is completely normal and expected - as the disk drive is still in the system: then Hard Disk Sentinel (as expected) still detects and shows it.
> physically ejected that drive, 2 seconds later it disappeared from the HDS list
Yes, it is normal: when the disk drive really removed, HDS noticed the change of the configuration and then the disk disappear.
> drive is now listed (with the comment field used as 'label') in the list of offline drives, great!
Yes of course, as expected: its state previously saved - but until the drive is physically present (listed in the main window) the list of offline drives do not show it.
> inserted drive again (without system restart) -> seconds later it shows up in HDS drive list
Yes, it is expected.
> drive c is now highlighted, on my first try I highlighted the fresh inserted drive
> ejected via hotswap program -> no error from hotswap, drive disappears immediately from HDS, great!
Yes, this is expected to happen.
> I want to stress the different behaviour: If the drive to be ejected is selected in HDS it will give the "in use error" from windows, if any non removable
drive is selected, it works like expected.
HDS does not "use", does not "keep" any drive used, regardless of which drive is selected in HDS.
> Yes, that's exactly
what I mean. Who is to blame then ...?
> Could it be possible that if you call certain system calls in windows (gather disk information) the OS does the locking anyway, whether you intent to or not?
Hard Disk Sentinel periodically detects the status information. By default, this happens once per every 5 minutes (and you can control at Configuration -> Advanced Options page, if you move the Detection Frequency slider).
The detection is usually a question of milliseconds - so if you are "lucky" to try the safe remove exactly during that, then yes, it is possible that the drive is "locked". But there is very small chance for that.
Between two consecutive detections, Hard Disk Sentinel does not "lock" the drive and does not access it, exactly to prevent removal-problems.
> Quote from the HotSwap homepage regarding 'device locking':
Yes, this is completely normal and known.
For example, antivirus software or something else (eg. Windows indexing service, defragmentation, etc...) can perform background activity - and can "lock" the drive, for example if it wants to know if there is a new file saved, file modified etc...
An open Explorer window or Total Commander window or similar can also "lock" the partition as they designed to show/react immediately when a file modified/saved.
But Hard Disk Sentinel does not do that - this is why I wrote that it performs no locking in general.
> I hope you don't mind that I invited the author of HotSwap to participate in this thread, maybe this makes two indispensable programs even better.
No problems at all, exactly the opposite
Hopefully together we'll also have some ideas, thoughts.