Total Commander

Currently TC stores sound settings in the registry. Can they be moved to wincmd.ini, so they can be used portably?

2m^2

Hello !

Currently TC stores sound settings in the registry. …

• I ever thought that's amazing, it's the only programme having its sounds in Windows !

…Can they be moved to wincmd.ini, so they can be used portably?

• Interesting idea… Except for deaf people… Seriously :
- Maybe some section with internal sounds, similar to the local associations one ?
- That needs some conditions, though. For instance, about the location of the sound files…

- But globally, I support !

 KR
Claude
Clo

In principle it could be done, but I did it via registry for the following reasons:
1. The user can use the standard Windows way to assign sounds
2. The standard sounds are system-specific, not portable (except if you would copy all the wav files, which is probably not allowed)

Clo wrote: - Maybe some section with internal sounds, similar to the local associations one ?

Sounds good.

Clo wrote:- That needs some conditions, though. For instance, about the location of the sound files…

I guess that it should be configurable. Just the standard TC way.

ghisler(Author) wrote:In principle it could be done, but I did it via registry for the following reasons:
1. The user can use the standard Windows way to assign sounds
2. The standard sounds are system-specific, not portable (except if you would copy all the wav files, which is probably not allowed)

Both reasons are good, but they don't negate usefulness of portable ones. There are several sets of sounds for TC that could be used portably, so the Windows' ones aren't needed.

Actually I very rarely use non-portable stuff at all. Because I change Windows every 1-2 years and installation / configuration hassles are usually not worth it. For this reason I've never had any sounds in TC, though I think they are a useful feature.

2ghisler(Author)

Good evening,

…(except if you would copy all the wav files, which is probably not allowed)

• There is no problem to copy the sounds from Window here, i.e. I copied :
E:\Windows\Media\Windows XP Erreur.wav
into some empty work dir.
- IIUC, only the writing is not allowed in <Windows> of Vista ¦ Win 7…
- And like I propose, even a local bunch of sound files could be stated as "local sounds" which could be "portable"…

 VG
Claude
Clo

Clo wrote:2ghisler(Author)

Good evening,

…(except if you would copy all the wav files, which is probably not allowed)

• There is no problem to copy the sounds from Window here, i.e. I copied :
E:\Windows\Media\Windows XP Erreur.wav
into some empty work dir.
- IIUC, only the writing is not allowed in <Windows> of Vista ¦ Win 7…
- And like I propose, even a local bunch of sound files could be stated as "local sounds" which could be "portable"…

 VG
Claude
Clo

Did you read the Windows license? IIRC it prevents moving parts of Windows to other computers.

I don't use TC portable myself so far, but I support any solution diminishing the role of the registry..

If the copying of the protected Windows sounds to a portable directory would be a problem,
I can imagine an alternative package of system sounds (free WAVs) to include in the portable version.
Although with a different content, they could even have the same name, I don't think there's a claim on that.

This could mean that in the default setting only the path should be changed, not the filename.

So long the TC don't leave any code in the registry, that's OK for portable the stuff.
Otherwise should portable used as portable, so in this case I dont need any sound when I
work with the U3 Stick on foreign PC's. Especially some kids have strange soundsets installed.
And I want to protect my ears for thd tortures.

m^2 wrote:Actually I very rarely use non-portable stuff at all. Because I change Windows every 1-2 years and installation / configuration hassles are usually not worth it. For this reason I've never had any sounds in TC, though I think they are a useful feature.

I've comprehension for your way to work with windows. So, perhaps it's possible to associate TC
to standard wave files in Windows. But please with an ini switch to throttle.

mf

To protect yourself from such sounds, just add something like

SoundDelay=36000

to the wincmd.ini. 3600 seconds would be one hour, so 36000 means that an operation would have to take 10 hours to cause a custom sound.

2Christian, thanks for the hint!

mf

Bumping this, PLEASE add an option to configure the sounds in wincmd.ini.

- Right now I can copy the whole TC folder, but even when I export the windows theme the TC sounds are usually not included.

- The license thing someone mentioned is a non-issue. It would be the user copying it, and who would give a f*ck if someone copies a sound file from one windows system to another one (which most likely has the same file). IANAL but I'm pretty sure neither microsoft nor any judge (not that such a thing would ever end up in front of one) would say that this is illegal.

- Almost no other programs use the windows dialog to configure their notification sounds. The only one I remember doing it is Visual Studio 6.

I agree that TC should be able to use INI settings over system ones. E.g. different TC installations may require different sound settings.

ghisler(Author) wrote:To protect yourself from such sounds, just add something like

SoundDelay=36000

to the wincmd.ini. 3600 seconds would be one hour, so 36000 means that an operation would have to take 10 hours to cause a custom sound.

hi
will be added the possibility to setup sounds in the portable version ?
i have my copy installed and one on my usb stick , i use on my work computer , i can't install programs
would be really usefull, because many times i use inear Headphones

thanks