WatchUer wrote:Haven't I told you that I also use relative paths for plugins in wincmd.ini's [ListerPlugins] section? If I edit the wincmd.ini to change the TConsole's full path to relative path like:TConsole=.\plugins\TConsole.wfx then the TConsole won't work.
True... all other plugins work this way (EventLog too ) but TConsole not.
To have the ini in the same directory as the wincmd.ini, you need to implement the *SetDefaultParams function (FsSetDefaultParams, ListSetDefaultParams or PackSetDefaultParams). This function is new in TC 5.51 and tells the plugin where to store the its ini. You can either use the suggested ini file name (it may be shared by other plugins, so use an unique section name), or override it with your own ini name.
GREAT! It supports DBCS.
bug report:
As you know, the command "cm_ExecuteDOS" can run cmd.exe and open a new console window, but it can't work when TConsole is running.
Shanny wrote:GREAT! It supports DBCS.
bug report:
As you know, the command "cm_ExecuteDOS" can run cmd.exe and open a new console window, but it can't work when TConsole is running.
[face=courier]Got this error trying to add TConcole 1.0.0.8 to plugins list on NT4SP6a:
Error loading plugin file!
The plugin probably needs some DLLs missing on your system.
And actually it doesn't work for me on w2kSRV and XPPro too (with wincmd.ini stored in %SYSTEMROOT% or in %COMMANDER_PATH% and loaded by "/I=" command line parameter) though at least I can add it to plugins list %). Any ideas?[/face]
I have PSAPI.DLL v.5.00.2134.1 in my %SystemRoot%\System32.
V> W2K & XP - I have no idea right now. And without batch file
V> it works?
No. I use two TC installation on that machines, from HDD and from JetFlash sometimes, HDD one use wincmd.ini from %SystemRoot% and both don't work with TConsole.