Page 2 of 2

Posted: Jul 26th, 2008, 9:51 am
by oomingmak
OK, it looks like I may have spoken too soon.

Everything was working fine, but then I needed to reboot my PC. I left the external drive connected during the reboot, but when I got back to my desktop after the restart, instead of the device being detected by SafelyRemove it showed as disconnected.

I tried to reactivate the device using SafelyRemove, but nothing happened. I just got a blank dialog window.

Image



I then physically disconnected and reconnected the eSATA device and it was detected again, but when I tried to shut it down from SafelyRemove I got the following error dialog:

Image

I then closed SafelyRemove (because I wanted to try to run it again to see if this would fix the problem) but SafelyRemove would not start because there was a 'dead' copy still loaded in memory (even though there was no tray icon). So I killed the existing SafelyRemove process using task manager and then I could start SafelyRemove again. However, the dialog about locked USB processes appeared and so I was still unable to disconnect my eSATA device.

As an aside to the above problem, I think it might be a good idea to be a bit more general in the wording of error message descriptions, because it doesn't make much sense to keep having "USB" devices and processes mentioned when the device is not actually anything to do with USB at all. It's inaccurate and somewhat confusing.

I'm going to try another reboot without the device connected and see if this makes any difference.

Posted: Jul 26th, 2008, 10:07 am
by oomingmak
I have just tried rebooting with the eSATA device disconnected.

Once I had reached my desktop, I physically connected the eSATA device and it was detected by SafelyRemove. However, despite being detected, the device was still listed as disconnected (big red X on the icon). So I tried reconnecting the device and this worked fine. An explorer window opened and the device could be browsed.

However, the disconnect problem remains. Trying to stop the eSATA device still gives the USB locked process message. Repeated attempts to disconnect do not show the locked process dialog, instead you just see a flicker of the light on the external device, but nothing happens. The device remains connected.

This means that the only time I was able to get the disconnect feature to work for SATA was for the two or so hours after I first installed the 'working version' of beta 5 (before I needed to reboot). During that time all connections and disconnections worked fine. Since I had to reboot, I have not been able to get it to work in the same way again.

W2000 / IcyDock SATA Drive Bay / WinXP

Posted: Jul 28th, 2008, 12:30 am
by MattBowers
As of about a week ago, I had tried version 3.31 and 4.04.690? of USB-SR on the Win2000 Server.
It never did work correctly or consistently. So, I removed the program.
I've instructed my client to go into the hardware devices and manually "disable" the HDD. This is scary as it shows up almost exactly as the main server drive!
I then have him put in the new IcyDock SATA drive and turn it on and wait 20 seconds. Then rt click on the system and "Scan for HW changes". This brings in the new drive.
I then have him open CPanel/Admin/Computer/HDD/ and if necessary right click the drive and "import" or enable or whatever.
I then have him "explore" his way down do a data directory that changes every day to verify that the drive is for sure on.

I just went to another client with WinXP-SP2 where the USB-SR worked for several days. It had quit working ("There are no visible connected devices"). I restarted the computer and the checkdisk program ran to fix the messed up removable drive. The drive shows up and I installed version 4.04.695. I'll run it another week or two and let you know if it keeps working.

*** How about a choice when rt-click on the USB-SR tray icon that is the same as "scan for hardware changes". This could prove useful.

Thanks again.
If I ever get the program working properly anywhere, I'll actually pay for it.

Version 4.0 beta 6 released!

Posted: Jul 30th, 2008, 11:55 am
by Igor
We have recently released 4.0 beta 6. This version is intended to increase stability and performance of the program, so it mainly contains bug-fixes. See list of changes below:
+ An ability to operate surprise removal USB devices has been added
+ Command line tool is now able to "Return device back"
+ "Enhanced logging" option has been added (required only on interact with our support team)
- The program updated its internal device list once too often (it leaded
to increasing CPU load)
- Sometimes the program overloaded the system on start or on connection of a new device
- Locking processes was not displayed on Windows 2000
- Sometimes the program suggested to disable USB device (not to safely remove it)
- Sometimes an error occurred on attempt to return device back
- GUI improvements: unattractive margins in some windows has been fixed
- It was impossible to browse device from the program which is mounted as a folder and a drive letter at the same time
- The program icon did not displayed in the windows uninstall applet
- Korean language was not selected automatically on Korean locales
- The program crashed on attempt to change image name in the file choosing dialog
* Improved hot-key support

You can download version 4.0 beta 6 here:
http://safelyremove.com/usbsafelyremovesetupbeta.exe

Posted: Jul 30th, 2008, 12:13 pm
by Igor
oomingmak wrote:OK, it looks like I may have spoken too soon.

Everything was working fine, but then I needed to reboot my PC. I left the external drive connected during the reboot, but when I got back to my desktop after the restart, instead of the device being detected by SafelyRemove it showed as disconnected.
Hi Oomingmak,
Thanks a lot for your detailed descriptions!

Some of the problems that you mentioned above have been fixed in beta 6 (e.g., blank dialog window, "dead" second copy). But we haven't made any changes in our stopping mechanism, so your main problem = - inability to disconnect your device, may still be in the program.

Could you download the beta 6 version, try to stop your device and then send us bug-report from the program (Main menu -> Help -> Report a bug. In the displayed dialog, please, enter your name on the forum and short description of the problem).I tried to reactivate the device using SafelyRemove, but nothing happened. I just got a blank dialog window.

Re: W2000 / IcyDock SATA Drive Bay / WinXP

Posted: Jul 30th, 2008, 12:40 pm
by Igor
MattBowers wrote: As of about a week ago, I had tried version 3.31 and 4.04.690? of USB-SR on the Win2000 Server.
It never did work correctly or consistently.
Matt, I recommend you to try the latest beta 6 - it was significantly improved over version beta 5. Also I'd ask you to let us know a little bit more detailed what certain problems you experiences with the program, in case if you have these problem with beta 6.
MattBowers wrote: I then have him put in the new IcyDock SATA drive and turn it on and wait 20 seconds. Then rt click on the system and "Scan for HW changes". This brings in the new drive.
*** How about a choice when rt-click on the USB-SR tray icon that is the same as "scan for hardware changes". This could prove useful.
We will consider adding an item "Scan for hardware changes" to the right-click menu if we find it necessary. However, USB Safely Remove must detect any new hot-plug devices automatically. Can you ask your client to install the latest beta version of USB Safely Remove and see if it is detect the drive after it is turned on, or not?
MattBowers wrote: I just went to another client with WinXP-SP2 where the USB-SR worked for several days. It had quit working ("There are no visible connected devices"). I restarted the computer and the checkdisk program ran to fix the messed up removable drive. The drive shows up and I installed version 4.04.695. I'll run it another week or two and let you know if it keeps working.
Yes, let us know please.

Bug report has been sent

Posted: Aug 21st, 2008, 10:38 pm
by oomingmak
Igor wrote:Could you download the beta 6 version, try to stop your device and then send us bug-report from the program (Main menu -> Help -> Report a bug. In the displayed dialog, please, enter your name on the forum and short description of the problem).
Beta 6 has been downloaded and installed.

I rebooted my system before installing SafelyRemove just to make sure that the system was fresh. My external Hard Drive enclosure was already connected while booting Windows.

I opened SafelyRemove and opted to show all devices (because my eSATA device was not visible by default). I then hid my fixed (internal) SATA hard drives because they are never hot-swapped and so I don't need them on the SafelyRemove menu. Then I tried to safely remove my eSATA device using the appropriate entry on the SafelyRemove tray icon. It failed, even on the very first attempt.

I tried the menu a couple more times, but it didn't make any difference.

I then immediately sent a bug report as you suggested. I included my forum name and a URL link to this thread in the message (so that you know that it's a continuation of the problems mentioned here).

The Bug report was sent today at 23:32 BST (i.e. British Summer Time: GMT + 1).
Let me know if you did not receive the bug report and I'll attempt to send another one (or send the report to you by email instead).

Re: Bug report has been sent

Posted: Aug 24th, 2008, 7:45 am
by Igor
oomingmak wrote: Beta 6 has been downloaded and installed.

I rebooted my system before installing SafelyRemove just to make sure that the system was fresh. My external Hard Drive enclosure was already connected while booting Windows.

I opened SafelyRemove and opted to show all devices (because my eSATA device was not visible by default). I then hid my fixed (internal) SATA hard drives because they are never hot-swapped and so I don't need them on the SafelyRemove menu. Then I tried to safely remove my eSATA device using the appropriate entry on the SafelyRemove tray icon. It failed, even on the very first attempt.

I tried the menu a couple more times, but it didn't make any difference.

I then immediately sent a bug report as you suggested. I included my forum name and a URL link to this thread in the message (so that you know that it's a continuation of the problems mentioned here).

The Bug report was sent today at 23:32 BST (i.e. British Summer Time: GMT + 1).
Let me know if you did not receive the bug report and I'll attempt to send another one (or send the report to you by email instead).
oomingmak, thank you for the report!
Unfortunately, now the program cannot help you in stopping your device. It's really locked by Windows and the program cannot manage it. Perhaps Windows uses it as a drive for system restore (it can be changed in the My Computer's settings) or something else.

System restore

Posted: Aug 24th, 2008, 1:28 pm
by oomingmak
Igor wrote:oomingmak, thank you for the report!
Unfortunately, now the program cannot help you in stopping your device. It's really locked by Windows and the program cannot manage it. Perhaps Windows uses it as a drive for system restore
Hi Igor. Thanks for your reply.

If you look at my earlier posts in this thread you will see that I'm using Windows 2000. Windows 2000 does not have any system restore feature (Windows XP was the first Windows OS to have system restore).

Therefore, system restore can not be the cause of the problem here.

Re: System restore

Posted: Aug 26th, 2008, 8:34 am
by Igor
oomingmak wrote:
Igor wrote:oomingmak, thank you for the report!
Unfortunately, now the program cannot help you in stopping your device. It's really locked by Windows and the program cannot manage it. Perhaps Windows uses it as a drive for system restore
Hi Igor. Thanks for your reply.

If you look at my earlier posts in this thread you will see that I'm using Windows 2000. Windows 2000 does not have any system restore feature (Windows XP was the first Windows OS to have system restore).

Therefore, system restore can not be the cause of the problem here.
oomingmak, I'm sorry for the delay with the response!

Yes, I know that you uses Windows 200, just forget that there is no System Restore feature.

Could you look at these recommendations: http://seagate.custhelp.com/cgi-bin/sea ... faqid=5094
especially step 2 - to disable "Recycle Bin" for your drive (don't know if these settings exists in Windows 2000).

Posted: Dec 6th, 2008, 6:50 pm
by ognised
Can USBSR cut the power of any devices which will be stop ???

Posted: Dec 11th, 2008, 1:30 pm
by Igor
ognised wrote:Can USBSR cut the power of any devices which will be stop ???
In next versions we will try to implement this feature

Trial USB Safely Remove v4.0.9.760

Posted: Dec 25th, 2008, 7:32 pm
by buyd
Trial USB Safely Remove v4.0.9.760

Subj: Vista Ultimate sp1. No file explorers runned. Special disk driver not installed, its a simply ext. 2.5' usb NTFS 320gb drive.
http://rapidshare.com/files/176735283/avz_sysinfo.zip.html

Image

не могу отключить диск ни одной кнопкой
can not stop the drive to any button :/

logon as admin

Re: Trial USB Safely Remove v4.0.9.760

Posted: Jan 4th, 2009, 5:16 pm
by Igor
buyd wrote:Trial USB Safely Remove v4.0.9.760

Subj: Vista Ultimate sp1. No file explorers runned. Special disk driver not installed, its a simply ext. 2.5' usb NTFS 320gb drive.
http://rapidshare.com/files/176735283/avz_sysinfo.zip.html

Image

не могу отключить диск ни одной кнопкой
can not stop the drive to any button :/

logon as admin
Hello Buyd,
Thank you for the note and sorry for the delay with the response.

We will try to fix this problem in one of future versions. Now we do not have neither a solution nor a workaround for this issue.