Ultra TC Editors 6.42 Final
Moderators: Hacker, petermad, Stefan2, white
Download Ultra TC Editors 5.53
What's new in version 5.53
==================
Main Menu Editor
------------------
[-] Windows Vista: Vertical scroll bar in the right panel was partially visible.
[*] The program icon changed.
Start and Directory Menu Editor
--------------------------------
[+] New parameter %A added to the default parameters list.
[-] Cannot delete any item refer to non exist extended command.
[-] Windows Vista: Vertical scroll bar in the menu panel was partially visible.
History Editor
---------------
[-] Windows Vista: Vertical scroll bar in the right panel was partially visible.
Configuration Editor
---------------------
[+] Status bar shows if target section is redirected or not. (redirected section mark with ">>>")
[+] Status bar shows actual TC ini file name.
[-] If the option 'Read keys listed in the data file only' checked, some descriptions are lost after saving the data file.
[-] Press Enter key after editing a value, cause beep sound.
[-] Windows Vista: Vertical scroll bar in the right panel was partially visible.
Hotkeys Editor
---------------
[-] Windows Vista: Vertical scroll bar in the right panel was partially visible.
[*] The program icon changed.
What's new in version 5.53
==================
Main Menu Editor
------------------
[-] Windows Vista: Vertical scroll bar in the right panel was partially visible.
[*] The program icon changed.
Start and Directory Menu Editor
--------------------------------
[+] New parameter %A added to the default parameters list.
[-] Cannot delete any item refer to non exist extended command.
[-] Windows Vista: Vertical scroll bar in the menu panel was partially visible.
History Editor
---------------
[-] Windows Vista: Vertical scroll bar in the right panel was partially visible.
Configuration Editor
---------------------
[+] Status bar shows if target section is redirected or not. (redirected section mark with ">>>")
[+] Status bar shows actual TC ini file name.
[-] If the option 'Read keys listed in the data file only' checked, some descriptions are lost after saving the data file.
[-] Press Enter key after editing a value, cause beep sound.
[-] Windows Vista: Vertical scroll bar in the right panel was partially visible.
Hotkeys Editor
---------------
[-] Windows Vista: Vertical scroll bar in the right panel was partially visible.
[*] The program icon changed.
-
- Junior Member
- Posts: 5
- Joined: 2008-04-17, 10:31 UTC
Directory Menu Editor Limit 199
Hello,
unfortunately the Editor has the old TC-restriction that the Directory Menu cannot contain more than 199 items. That has been solved with TC in version 7.?. It would be nice if this restriction (a message box appears) will be removed from Ultra TC Editors.
Thanks!
unfortunately the Editor has the old TC-restriction that the Directory Menu cannot contain more than 199 items. That has been solved with TC in version 7.?. It would be nice if this restriction (a message box appears) will be removed from Ultra TC Editors.
Thanks!
Re: Directory Menu Editor Limit 199
You can remove this limit as follow:Brat.Hering wrote:Hello,
unfortunately the Editor has the old TC-restriction that the Directory Menu cannot contain more than 199 items. That has been solved with TC in version 7.?. It would be nice if this restriction (a message box appears) will be removed from Ultra TC Editors.
Thanks!
1- Run any text editor program (e.g. Notepad) and open the program INI file "ultra tc editors.ini"
2- Create the key StartMenuMaxItems under [DirectoryMenuEditor] or [StartMenuEditor] section.
3- Set the key StartMenuMaxItems value to desired number (say 500)
4- restart Directory Menu Editor
I was trying to make a manual TC installation for U3 (a special USB stick) but I noticed that unfortunately, Ultra TC Editors do not recognise the necessary variables.
TC 7.04a for U3 (the official version distributed by Ghisler here: http://www.ghisler.com/usbinst.htm) now uses variables like %U3_DEVICE_EXEC_PATH% and %U3_APP_DATA_PATH% (these are universal for any U3 application) but Ultra TC Editors had trouble operating with these variables. (Seems that %COMMANDER_PATH% does not work in 7.04a for U3.)
It seems that %U3_DEVICE_EXEC_PATH% refers to a directory in the system drive's Documents and Settings\Profile Name\Application Data\U3 directory (a temporary one created when the U3 stick is launched) and %U3_APP_DATA_PATH% refers to TC's data directory, which stays on the U3 stick during the session. This means that Totalcmd.exe and Wincmd.ini are in different directories and on different drives during the session (and depending on the session, these locations can be very different on different computers).
Basically it is possible to manually set TC Editors to operate from the U3 stick but it is impossible to tell them where TC's files are.
Is there any chance to improve this?
TC 7.04a for U3 (the official version distributed by Ghisler here: http://www.ghisler.com/usbinst.htm) now uses variables like %U3_DEVICE_EXEC_PATH% and %U3_APP_DATA_PATH% (these are universal for any U3 application) but Ultra TC Editors had trouble operating with these variables. (Seems that %COMMANDER_PATH% does not work in 7.04a for U3.)
It seems that %U3_DEVICE_EXEC_PATH% refers to a directory in the system drive's Documents and Settings\Profile Name\Application Data\U3 directory (a temporary one created when the U3 stick is launched) and %U3_APP_DATA_PATH% refers to TC's data directory, which stays on the U3 stick during the session. This means that Totalcmd.exe and Wincmd.ini are in different directories and on different drives during the session (and depending on the session, these locations can be very different on different computers).
Basically it is possible to manually set TC Editors to operate from the U3 stick but it is impossible to tell them where TC's files are.
Is there any chance to improve this?
#68776 Personal Licence
If Ultra TC Editors couldn't auto find TC's files, it ask the user to browse for Wincmd.ini and wcx_ftp.ini then save these files path in "ultra tc editors.ini" to use them next time it run. What happen with you?andres992 wrote:Basically it is possible to manually set TC Editors to operate from the U3 stick but it is impossible to tell them where TC's files are.
Unfortunately I don't have a U3 stick to test.
Yes, Ultra TC Editors ask for the files but...
The problem is that a U3 stick is used mostly temporarily (usually to run programs on another computer), and it may create different folders every time. It is very difficult for the ordinary user to know where exactly are the files used by TC for the ongoing session.
For example, in one session, U3 could create the EXEC folder for TC in
C:\Documents and Settings\ProfileName1\U3\F9C45380-822A-434b-B70E-5024AE551E68\Exec\totalcmd.exe
while the Data files (all inis) remain on the stick, e.g.
J:\System\F9C45380-822A-434b-B70E-5024AE551E68\Data\wincmd.ini
On another computer at a different time, the Profile Name will most probably change (e.g. ProfileName2 instead of ProfileName1), as will the U3 Drive letter (e.g. D instead of J).
U3 can manage its settings perfectly because at the end of the session, all files (e.g. wincmd.ini) changed during the session will be checked and saved back to the U3 stick.
The main problem is that totalcmd.exe and wincmd.ini are on different (changeable) drives, and TC for U3 itself uses the default U3 variables like %U3_APP_DATA_PATH% and %U3_DEVICE_EXEC_PATH%, but Ultra TC Editors cannot recognise these variables.
If I save one wincmd.ini location in the Ultra Editors ini file (let's say the one on J), then next time when U3 acts as drive D, Ultra Editors will still not find the correct wincmd.ini. Therefore, I cannot use the same hard path next time but it is necessary to use U3 (or other equivalent) relative variables for the path. %COMMANDER_PATH% does not work since totalcmd.exe and wincmd.ini are on different drives (and even TC for U3 does not use the %COMMANDER_PATH% variable in wincmd.ini but uses the U3 variables).
The normal practice would be to keep the Ultra TC Editors folder on the stick, in the TC Data directory. In my previous example, that would be something like
J:\System\F9C45380-822A-434b-B70E-5024AE551E68\Data\Tools\TCEditors\
(but it could be another drive letter in a different session, depending on the computer).
EDIT: In fact, it would even be helpful if TC Editors could always use the path (and retain that path in the ini file):
utceditors:\..\..\
As this is the path where wincmd.ini is actually located in my case (and the location of totalcmd.exe is not needed anyway because restarts of TC in the case of U3 are better done manually).
The problem is that a U3 stick is used mostly temporarily (usually to run programs on another computer), and it may create different folders every time. It is very difficult for the ordinary user to know where exactly are the files used by TC for the ongoing session.
For example, in one session, U3 could create the EXEC folder for TC in
C:\Documents and Settings\ProfileName1\U3\F9C45380-822A-434b-B70E-5024AE551E68\Exec\totalcmd.exe
while the Data files (all inis) remain on the stick, e.g.
J:\System\F9C45380-822A-434b-B70E-5024AE551E68\Data\wincmd.ini
On another computer at a different time, the Profile Name will most probably change (e.g. ProfileName2 instead of ProfileName1), as will the U3 Drive letter (e.g. D instead of J).
U3 can manage its settings perfectly because at the end of the session, all files (e.g. wincmd.ini) changed during the session will be checked and saved back to the U3 stick.
The main problem is that totalcmd.exe and wincmd.ini are on different (changeable) drives, and TC for U3 itself uses the default U3 variables like %U3_APP_DATA_PATH% and %U3_DEVICE_EXEC_PATH%, but Ultra TC Editors cannot recognise these variables.
If I save one wincmd.ini location in the Ultra Editors ini file (let's say the one on J), then next time when U3 acts as drive D, Ultra Editors will still not find the correct wincmd.ini. Therefore, I cannot use the same hard path next time but it is necessary to use U3 (or other equivalent) relative variables for the path. %COMMANDER_PATH% does not work since totalcmd.exe and wincmd.ini are on different drives (and even TC for U3 does not use the %COMMANDER_PATH% variable in wincmd.ini but uses the U3 variables).
The normal practice would be to keep the Ultra TC Editors folder on the stick, in the TC Data directory. In my previous example, that would be something like
J:\System\F9C45380-822A-434b-B70E-5024AE551E68\Data\Tools\TCEditors\
(but it could be another drive letter in a different session, depending on the computer).
EDIT: In fact, it would even be helpful if TC Editors could always use the path (and retain that path in the ini file):
utceditors:\..\..\
As this is the path where wincmd.ini is actually located in my case (and the location of totalcmd.exe is not needed anyway because restarts of TC in the case of U3 are better done manually).
#68776 Personal Licence
Sorry for the long explanation in the previous post. Maybe it was unnecessary. It seems that Configuration Editor may indeed find the ini files even at present.
It also seems that my problem arises from ultra tc editors.ini instead. I have there the entry:
and the file tc_data.cedf is located in the same dir as the Configuration Editor but still when I open the Configuration Editor, I get the error message "Cannot find data file! Please open one to continue".
Is it possible to use the variable "utceditors:\" in the ini file?
It also seems that my problem arises from ultra tc editors.ini instead. I have there the entry:
Code: Select all
StartUpDataFile=utceditors:\tc_data.cedf
Is it possible to use the variable "utceditors:\" in the ini file?
#68776 Personal Licence
2andres992
Try to use an environment variable to specify the path of Wincmd.ini and wcx_ftp.ini e.g.
you can also use variable for StartUpDataFile but unfortunately this variable will replaced with the true path when closing Configuration Editor
Main Menu Editor, Start and Directory Menu Editor and Hotkey Editor require to know the commander path in order to work properly (they needs the file Totalcmd.inc which is located inside commander path) but I don't know how to get it as far as %Commander_Path% cannot be used for U3 stick
Try to use an environment variable to specify the path of Wincmd.ini and wcx_ftp.ini e.g.
Code: Select all
[Common]
; used by all editors
UserDefinedWincmd=%U3_APP_DATA_PATH%\wincmd.ini
[ConfigurationEditor]
; used by Config Editor
UserDefinedWcxftp=%U3_APP_DATA_PATH%\wcx_ftp.ini
Main Menu Editor, Start and Directory Menu Editor and Hotkey Editor require to know the commander path in order to work properly (they needs the file Totalcmd.inc which is located inside commander path) but I don't know how to get it as far as %Commander_Path% cannot be used for U3 stick
This did not work (Configuration Editor said it could not find wcx_ftp.ini). EDIT: Only first time, now it seems to work. (This entry must be under [Configuration Editor], otherwise Configuration Editor creates a new wcx_ftp.ini in C:\Windows\ts4242 wrote:Try to use an environment variable to specify the path of Wincmd.ini and wcx_ftp.ini e.g.Code: Select all
[Common] ; used by all editors UserDefinedWincmd=%U3_APP_DATA_PATH%\wincmd.ini [ConfigurationEditor] ; used by Config Editor UserDefinedWcxftp=%U3_APP_DATA_PATH%\wcx_ftp.ini
It seems that, after all, TC Editors find wincmd.ini and wcx_ftp.ini even without any user-defined lines in the TC Editors ini file. It would be nice though if the following ini lines would work:
Code: Select all
UserDefinedWincmd=utceditors:\..\..\wincmd.ini
UserDefinedWcxftp=utceditors:\..\..\wcx_ftp.ini
This entry seems to be the main problem now. TC Editors indeed seem to find the TC ini files without any specific instructions but when opening the Configuration Editor, I still always get the error message that data file was not found. At the same time, TC Configuration Editor then points me directly to the right directory where the data file actually is and asks me to open the file.you can also use variable for StartUpDataFile but unfortunately this variable will replaced with the true path when closing Configuration Editor
Is it possible to add an option that the utceditors:\ variable can be used in ini files (as well as the \..\ option to go one directory up) and an option that StartupDataFile will not be changed upon closing Configuration Editor?
Or, is it possible to add a startup parameter for the correct data file, e.g.
Code: Select all
%U3_APP_DATA_PATH%\Tools\TCEditors\Configuration Editor.exe /data=%U3_APP_DATA_PATH%\Tools\TCEditors\Data Files\tc config data english.cedf
Code: Select all
%U3_APP_DATA_PATH%\Tools\TCEditors\Configuration Editor.exe /data=utceditors:\Data Files\tc config data english.cedf
I discovered that %COMMANDER_PATH% still partially works. Namely, %COMMANDER_PATH% correctly points to the directory where totalcmd.exe is (totalcmd.inc is also there but wincmd.ini and Wcxftp and the Menu file are not in that directory).Main Menu Editor, Start and Directory Menu Editor and Hotkey Editor require to know the commander path in order to work properly (they needs the file Totalcmd.inc which is located inside commander path) but I don't know how to get it as far as %Commander_Path% cannot be used for U3 stick
In summary: History Editor works (but it seems that it cannot use any command line or ini switches). Configuration Editor works too but asks for the missing data file (and pointing me exactly to the directory where that data file is, asking to open it). For the Configuration Editor, ini file lines with variables seem not to work. As the menu file is, for an unknown reason, in a third directory (packed on the U3 stick), I decided that changing the menu with TC Editors would probably not work anyway. Still, History Editor and Configuration Editor are my main interests.
So, basically, the only problem remaining is Configuration Editor not finding the data file on its own.
#68776 Personal Licence
When you run an editor from TC, it can get the current wincmd.ini from the variable %Commander_INI%andres992 wrote:It seems that, after all, TC Editors find wincmd.ini and wcx_ftp.ini even without any user-defined lines in the TC Editors ini file.
This is a bug and I will fix it next release!andres992 wrote:and an option that StartupDataFile will not be changed upon closing Configuration Editor?
Try add a button to TC toolbar to run Configuration Editor and in the command field pass your startup data file as follow:andres992 wrote:So, basically, the only problem remaining is Configuration Editor not finding the data file on its own.
Code: Select all
"Ultra_TC_Editors_Path\Configuration Editor.exe" "%U3_APP_DATA_PATH%\tc config data english.cedf"
Thank you! The data file problem is solved. The solution you proposed for the button worked but since I use a user command in usercmd.ini, the following worked too:
(the quotes in the cedf path turned out to be important).
Now I can confirm that History Editor and Configuration Editor can be used from U3 and are functioning well.
As for other configuration editors, I did not test them. Since the TC menu file is kept on the U3 stick at all times in a different directory, using Menu Editor would probably require a remake of the TC U3 package and putting the menu file to the data path.
Code: Select all
[em_Configuration_Editor]
menu=TC Configuration Editor
cmd=%U3_APP_DATA_PATH%\Tools\TCEditors\Configuration Editor.exe "%U3_APP_DATA_PATH%\Tools\TCEditors\Data Files\tc config data english.cedf"
Now I can confirm that History Editor and Configuration Editor can be used from U3 and are functioning well.
As for other configuration editors, I did not test them. Since the TC menu file is kept on the U3 stick at all times in a different directory, using Menu Editor would probably require a remake of the TC U3 package and putting the menu file to the data path.
#68776 Personal Licence