Total Commander

"usb flash drive cannot be stopped just now" says windows if that drive is open in totalcmd.

d wrote:"usb flash drive cannot be stopped just now" says windows if that drive is open in totalcmd.

Just change the drive, other than USB drive, before quit.

Best wishes,
Eugen

Just change the drive, other than USB drive, before quit.

I always wondered why people keep answering with the "problem" instead of with the "solution" (especially since currently there is no solution)?

Should I point out that "this works in explorer ™"?

roentgen wrote:

Just change the drive, other than USB drive, before quit.

I always wondered why people keep answering with the "problem" instead of with the "solution" (especially since currently there is no solution)?

Should I point out that "this works in explorer ™"?

2roentgen

First, it's about "drive open in totalcmd" not in explorer.
2nd, explanation: because TC use USB stick, Window$ can't stop the process.

No directory (folders) from USB stick, must be present into any folder tabs in Total Commander before you can stop the process.
Of course, with TC running.

If you wish, I can explain in Romanian for you, for better understanding.


Best wishes,

roentgen wrote:

Just change the drive, other than USB drive, before quit.

I always wondered why people keep answering with the "problem" instead of with the "solution" (especially since currently there is no solution)?

Should I point out the difference between a problem and a workaround for this problem, especially since Eugen explained how to work around the problem?

Karl

2eugensyl
2karlchen
Ohh, this is the second level: TC flaws praised as features. OK, I give up

2eugensyl

If you wish, I can explain in Romanian for you, for better understanding.

No thanks, crappy english is just fine

roentgen wrote:Ohh, this is the second level: TC flaws praised as features.

You are twisting the facts! A workaround is a workaround. No-one praised TC inside this thread at all.

OK, I give up

Do not make promises which you do not intend to keep.

Karl

Eugensyl wrote:No directory (folders) from USB stick, must be present into any folder tabs in Total Commander before you can stop the process.

Not really confirmed.

Telling from my own experience, I can tell Windows to unload the USB stick (RunDll32.exe shell32.dll,Control_RunDLL hotplug.dll) even if in one of the TC tabs a USB folder is still being displayed. This tab, however, must not be the currently active tab.

Anyway, the question is more or less like this:

• You tell Windows to unload the USB stick. Windows tells you it is being blocked.
• Does this mean TC receives a Windows message telling it to release the USB stick, but TC viciously ignores the Windows message?
• Does this mean TC never receives such a message at all, so it cannot know it should release the USB stick?
• Does Windows even bother to find out which programme is blocking the stick?

roentgen wrote:Should I point out that "this works in explorer ™"?

This is not really amazing, because the file manager "Explorer" is the same "Explorer" which you tell to unload the stick. And Explorer has a pretty good chance of knowing it is blocking the stick and of unblocking it automatically.

The unanswered question is if TC has got a chance of knowing that "unload USB stick" has been requested?
This question can very likely only be answered by Christian Ghisler, the programm author.

[Added]
So far this thread has been somewhat on the line: TC vs. Explorer. Here is something to show it is not that easy:
Open cmd.exe, change to the USB drive, F: in my case. Switch back to the SysTray, right-click the USB icon and select "Remove hardware safely".
You will get the same error message as quoted by user "d".
Result: The USB stick cannot be safely removed.
Reason: cmd.exe is blocking the USB drive. (And it is MS cmd.exe that comes with Windows.)
Repeated the same procedure using IrfanView and used its open dialogue to navigate to the stick and open a folder (no picture loaded). Result: The USB stick cannot be safely removed.

Conclusion:
Things may not be as easy as some people seem to assume.
We still cannot tell for sure if TC has got a chance of switching away from the USB stick as soon as Windows receives an unload request.
Apparently cmd.exe cannot do so. Irfanview would not do so either.
[/Added]

Karl

2d

Have you tried these settings:

http://madsenworld.dk/tcmd/usb-1.png
and
http://madsenworld.dk/tcmd/usb-2.png

Open cmd.exe, change to the USB drive, F: in my case. Switch back to the SysTray, right-click the USB icon and select "Remove hardware safely".
You will get the same error message as quoted by user "d".

Let's jump to [MY] conclusions: TC didn't go further than cmd.exe in functionality

Conclusion:
You deliberately ignore any evidence that might indicate it may not be TC's fault.

Karl

karlchen wrote:Conclusion:
You deliberately ignore any evidence that might indicate it may not be TC's fault.

No, I'm the kind that says: if one can do it - so can I. That assumes that Ghisler has at least 1% interest regarding the reported problems, which isn't always the case.

I'm sure (someone please confirm/deny this) that neither TC, nor cmd.exe, nor any other application (other that Explorer itself) is notified that user wants to disconnect USB from the Safely Remove Hardware tray icon. So, as karlchen pointed out, it's possible that it's not TC's fault.

Hmm... I'm no programming expert but this looks like enough: DBT_DEVICEQUERYREMOVE, part of WM_DEVICECHANGE

MSDN says:

The system broadcasts the DBT_DEVICEQUERYREMOVE device event to request permission to remove a device or piece of media.

but it seems that TC and the likes actively deny this.


Something that looks like a real example: Processing a Request to Remove a Device


// rant: damn... I had to use google again

[mod]Moved to the English forum.

Hacker (Moderator)[/mod]