Internal Associations bug?

[Boofo]

I'm not sure if this is a bug or not but I don't get the drop down for any of these extensions other than the CMD one. The rest run like normal, but with CMD is will give me a drop down menu like it should. Am I doing something wrong or is this a bug of some sort?

Code: Select all

Filter8=*.bat;*.cmd;*.inf;*.reg;*.vbs
Filter8_open=*
Filter8_Open with &EditPlus=""%PROGRAMFILES%\EditPlus 3\editplus.exe" "%2""
Filter8_Open with &Lister=""%COMMANDER_PATH%\TOTALCMD.EXE" /S=L "%1""
Filter8_Open with &Notepad2=""D:\Software\Notepad2\Notepad2.exe" "%1""
Filter8_Run (Sys)=%comspec% /c "%1"
Filter8_Run (TCC)=""%PROGRAMFILES%\JPSoft\TCMD10\tcc.exe" /c "%1""

[fenix_productions]

2Boofo
No problems here.

I think this is related to:
http://www.ghisler.ch/board/viewtopic.php?t=23644

Shortly: you might have different filters defined for mentioned extensions already. In such case only the first rule will be handled. Internal Associations are not perfect yet

[Boofo]

2fenix_productions,

I checked them all and the only one I had defined already was INF. I removed that one. The CMD file still gives me the drop down but the BAT file automatically runs when I click on it. It seems like the external association takes over for BAT files.

[ghisler(Author)]

Indeed exe, com, bat and lnk files are treated differently than other files: The default verb cannot be overridden via internal associations, and additional context menu items are shown only in the internal context menu (cm_contextmenuinternal). While the former is intentional so the user doesn't accidentally disable programs by defining a *.* internal association, the later is not intentional - it's probably a side effect of the former. Unfortunately there isn't enough time now to fix that before the release of TC 7.5, but I will try to find a solution for the next version.

[Boofo]

Thanks, Christian.

[eugensyl]

Indeed exe, com, bat and lnk files are treated differently than other files...

Sorry, cmd is not included? I mean is not the same as bat?


Extension <<.bat>> was replaced with <<.cmd>> in NT version.

Explanation are here:
CMD.exe is the NT/XP equivalent of Command.com in previous operating systems. The older 16 bit command processor command.com is supplied to provide backward compatibility for 16 bit DOS applications. For example command.com will fail to set %errorlevel% after certain commands.

To ensure that a batch file will not run if accidentally copied to a Windows 95/98 machine you should use the extension .CMD rather than .BAT in NTFS systems.

The COMSPEC environment variable will show if you are running CMD.EXE or command.com .

[ghisler(Author)]

No, cmd files are currently not treated separately, but I will consider it.

[eugensyl]

No, cmd files are currently not treated separately, but I will consider it.

Thanks!

[Boofo]

I like that CMD files work in the menu drop down.

[StatusQuo]

cmd files are currently not treated separately, but I will consider it.

Thanks - support.