The help file for @getdir does not mention that the title must be in quotes if it has spaces. Not consistent with other @get... It seems the returned folder is quoted if necessary regardless if the first argument is quoted. Also a null path is allowed if there is a title. The dialog does not...
I tried three times to download the takcommand.pdf for version 25 from the dowload tab. My pdf reader said there was a error in the file. It would be nice to have the pdf file
I tried several times to download takecommand.pdf from JPSoft.com. Each time my pdf reader said the file was corrupted. Is this supposed to be the help file for 25? Sometimes having the PDF file is useful.
I have never used setdos /g. The @int was applied to the result of an @eval anyway so the arithmetic symbols should have been consistant. The @int works fine on ver 19 20 just fine and had been working for ver 21 until that last update. The problem seems there. Sorry you cannot duplicate it...
I never used setdos /g and I know that @int changed with the update to build 63. The batch file I used it in worked differently after the update. I didn't notice right away as the data was sent to a log file.
I, of course, had to immediately go to build 63 of TC21. Because this is the latest version, I cannot see the fix list for the various builds. I did notice the following problem with the above mentioned numeric functions: @int appears to do nothing and all three r seem to ignore a comma...
On W7 there seems to be a problem with PSUBST. After using it to assign a:, the following message appeared then I tried to unassign it
:\howard\working>psubst/d a:
TCC: (Sys) The specified program requires a newer version of Windows.
"SYSTEM\CurrentControlSet\Control\Session Manager\DOS...
Here is what the manual says for the command:
Usage:
The settings dialogs that are available will depend on your Windows version. The list below is for Windows 10.
I tried every dialogname for wsettings in Windows 7 and everyone gave an error message like:
TCC: (Sys) "ms-settings:about.
The command seems to work fine in Windows 10
The wshortcut command with the /t option appears to set the File explorer correctly but gives and error message in Windows...
You know I didn't care about what it reported before but this is from the v21 documentation on both _WINVER, and the VER command:
Updated Internal Variables:
_WINVER - Now returns the actual Windows version for Windows 7 / 8 / 10 instead of the Windows default API results (i.e., "10.0" instead...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.