+F6 to move now dings after pressing ok

[Blight]

v8.5 final 64bit on Windows 7 64bit:

I get a system "ding" after pressing the ok button when moving files between folders on the same drive using the F6 keyboard macro.

Is it intentional? any way to disable it?

[GordonAShumway]

I'm having this exact same issue with 8.5 final 64 bit on Windows 7 also. A little annoying as I prefer Total Commander to be "silent" as I use it lightly during audio recording work. I held off installing/running any of the 8.5 series until it went final.

Under Configuration --> Options --> Misc, there's a "Custom Sounds" menu at the bottom and "Configure" button. Under Windows 7, it tells me to consult the Control Panel --> Sounds and Multimedia in Windows. Sure enough, there is a dedicated "Total Commander" section there. However, I previous turned off all sounds shown there by setting them to "nothing". The 8.5 upgrade kept these, but the F6 "move" still results in the "ding".

Also, is the download link to versions at ghisler DOT com SLASH amazons3.php messed up, description-wise? For the 32-bit, as I write this, it reads "Windows 95 up to Windows 8.1, 32-bit AND 64-bit!", same as "64-bit+32-bit combined". I think that first link should read "ONLY 32-bit"?

[white]

Also, is the download link to versions at ghisler DOT com SLASH amazons3.php messed up, description-wise? For the 32-bit, as I write this, it reads "Windows 95 up to Windows 8.1, 32-bit AND 64-bit!", same as "64-bit+32-bit combined". I think that first link should read "ONLY 32-bit"?

No, this is correct. Total Commander 32-bit runs fine on Windows 64-bit.

[GordonAShumway]

No, this is correct. Total Commander 32-bit runs fine on Windows 64-bit.

Ah, I see. I do know that 32-bit applications run fine on Windows 64-bit. The way the page is worded, I thought the comment was referring to what the build was that you're getting at the download link - a full-text explanation to the clickable download link, so it didn't make sense that the same exact phrase wording for the 32 and 64 together was present as the 32-bit alone version. I see now what the convention means.

[pantantrolla]

Under Configuration --> Options --> Misc, there's a "Custom Sounds" menu at the bottom and "Configure" button. Under Windows 7, it tells me to consult the Control Panel --> Sounds and Multimedia in Windows. Sure enough, there is a dedicated "Total Commander" section there. However, I previous turned off all sounds shown there by setting them to "nothing". The 8.5 upgrade kept these, but the F6 "move" still results in the "ding".

I have solved putting any sound in windows settings sounds / section total commander, apply, and then put back nothing, and does not "ding"

On windows 8.1 64bits, and totalcmd 64 bits

sorry for my English

[ghisler(Author)]

I do not get this ding/beep either, but I have some ideas what might be causing it.

[GordonAShumway]

I do not get this ding/beep either, but I have some ideas what might be causing it.

Is it anything in TC's .INI file that might be responsible? I've had the same .INI file for an eternity, moving through various versions, so I can check it for something specific or remove a line in it if you have an idea. Or, I can search for a registry key value if it's more a Windows sound association thing.

I didn't try pantantrolla's fix yet as I'll let the symptom persist for a bit in case anyone wants a fix to be tested out or a setting checked.

[Dalai]

@GordonAShumway: You can always check if it's in the default settings without even touching your wincmd.ini:

Code: Select all

totalcmd.exe /i="%temp%\fresh.ini"

If the problem exists with default settings you don't need to dig any further in this direction. If it is, well, then you should compare your wincmd.ini with the default one.

Regards
Dalai

EDIT: Typo

[GordonAShumway]

Great suggestion, Dalai. I did as you said pointing to a fresh INI that TC would create the first time, and this time, low and behold, no sound resulted with the F6 "Move" action.

I then exited TC and launched it as normal, with my old familiar INI (I confirmed it's using it, and it wasn't modified at any time). Low and behold, also no sound this time. The Windows sounds for TC were unaffected by utilizing the new INI, so my thought was one factor that had changed is that I had powered off and consequently rebooted for the overnight and daytime today.

Not sure if 8.5 simply needed a reboot after the install or it's something else. If anyone else here is experiencing this issue still and hasn't rebooted, try that. Maybe just coincidence.

[Cosmin3]

TC version: 8.5 final 32 bit.
OS: Windows XP SP3 x86 latest updates
wincmd.ini: from 8.01, never had such problem.
AV (maybe it's important): Eset Smart Security 7

I hear the default beep only when moving files on the same partition, not when moving to another partition or drive.
Closing TC, renaming wincmd.ini to wincmd.ini.org and starting TC again doesn't solve the problem.
Trying with fresh.ini, still doesn't work.
Rebooting + fresh.ini still no. Also disabling Eset SS.

Except disabling the default beep in Sounds, what else can I do?
Thank you for any suggestion.

Regards, Cosmin


LE: curious, the forum wouldn't let me to enter the entire text at once, saying I have URLs. I had to add portion by portion by editing it...

[GordonAShumway]

I spoke too soon my post above - found the beep returned this morning, but as Cosmin3 points out, it's only when the file is moving to the same drive/partition. That wasn't the scenario consistently in yesterday's tests I had run as I was trying the F6 action in a few different ways (same/alternate drive).

Pantantrolla's technique described above worked perfectly for me, though: I picked any sound in Windows' own management for the "Total Commander" section, for any one given event, "Preview"ed it by hitting play, then reverted it back to nothing like all the other "TC" section events there. That was enough to get the ding suppressed.

[ghisler(Author)]

There is a workaround to the problem:
1. Go to menu
Configuration - Options - Misc
2. Tick "Only play for long operations
3. Set a high value, e.g. 120 seconds

[Cosmin3]

Yes, it worked
Thank you.

Regards,
Cosmin

[ghisler(Author)]

This has been fixed in TC 8.51 beta 1, please confirm!

If there isn't any reply to this thread within the next 7 days, I will move it to fixed bugs.