TCC/LE 13.0 error with long file names and quotes

Sep 28, 2011
3
0
We are trying to solve a couple of problem within a large file sytem (more than 30 milion files, more than 100,000 directories) using TCC (TCC LE 13.00.21 x64 Windows 7 [Version 6.1.7601]).

Using TCC we are running into two major problems that we cannot solve so far:

1. Errors on long file names (although the release notes state that the limitations have been removed in version 13)
- some variable functions like @filesize, @filetime and even a regular dir do not work on file names over 257 characters (including directory). The same commands do work correctly using CMD.EXE
Example (UNC path length 140 chars, file name length 120 chars):
for %i in ("{long UNC path}\*.*") echo %@attrib["%i"]
output is correct
for %i in ("{long UNC path}\*.*") echo %@attrib["%i"]
result is -1
for %i in ("{long UNC path}\*.*") *dir "%i"
TCC: (Sys) The system cannot find the file

2. File names including single quotes and back ticks ´,`,'
Since we are processing file names including blanks we have to quote file names. File names with single quotes result in "missing closing quote" messages. Setdos /x-7 would solve the problem but does not allow variable functions anymore. The only solution would be a more granular setdos disabling only single quotes and still allowing double quotes.

In the mean time we have reverted back to cmd.exe missing some functionality but being able to handle all these very "special" file names correctly.

Any ideas?
 
Sep 28, 2011
3
0
just found a typo in the post:

Example (UNC path length 140 chars, file name length 120 chars):
for %i in ("{long UNC path}\*.*") echo %@attrib["%i"]
output is correct
for %i in ("{long UNC path}\*.*") echo %@filesize["%i"]
result is -1
 
Sep 28, 2011
3
0
I have found a workaround for the back quote problem that has worked for my purposes by replacing the back quote with a question mark and using the wildcard in further commands:

for %i in (*.*) do gosub process
quit

:process
setdos /x-7
set filename=%@replace[`,?,%i]
setdos /x+7
... further processing using %filename%
return
 
Apr 1, 2013
1
0
We are trying to solve a couple of problem within a large file sytem (more than 30 milion files, more than 100,000 directories) using TCC (TCC LE 13.00.21 x64 Windows 7 [Version 6.1.7601]).

Using TCC we are running into two major problems that we cannot solve so far:

1. Errors on long file names (although the release notes state that the limitations have been removed in version 13)
- some variable functions like @filesize, @filetime and even a regular dir do not work on file names over 257 characters (including directory). The same commands do work correctly using CMD.EXE
Example (UNC path length 140 chars, file name length 120 chars):
for %i in ("{long UNC path}\*.*") echo %@attrib["%i"]
output is correct
for %i in ("{long UNC path}\*.*") echo %@attrib["%i"]
result is -1
for %i in ("{long UNC path}\*.*") *dir "%i"
TCC: (Sys) The system cannot find the file

2. File names including single quotes and back ticks ´,`,'
Since we are processing file names including blanks we have to quote file names. File names with single quotes result in "missing closing quote" messages. Setdos /x-7 would solve the problem but does not allow variable functions anymore. The only solution would be a more granular setdos disabling only single quotes and still allowing double quotes.

In the mean time we have reverted back to cmd.exe missing some functionality but being able to handle all these very "special" file names correctly.

Any ideas?


I have also encountered long file name errors like:

"Error cannot delete file: cannot read form the source file or disk."
"Cannot delete file or folder. The file name you specified is not valid pr too long. Specify a different file name."

probably it is because of the Windows Explorer/FAR would fail to copy/rename/delete any pathname longer than 256 characters (Path Too Long Error).

I have read some forums on how to solve this problem and some recommend me to use Long Path Tool. I tried to use this tool and it really works. I guess this would help.
 
Similar threads
Thread starter Title Forum Replies Date
B Error in TCC/LE when succeed smoothly in native windows cmd.exe TCC/LE Support 6
T Error when trying to update TCC/LE v13.00.12 TCC/LE Support 2
G What does this error means: TCC: Unknown command "C:\Program" TCC/LE Support 13
Jesse Heines Request for TCC Date Command Custom Format Example TCC/LE Support 4
P TCC LE crashes without any info after recent windows updates TCC/LE Support 3
V TCC LE doesn't expand %~ff correctly TCC/LE Support 5
A vcvarsall.bat command not working on TCC LE command prompt TCC/LE Support 16
M DEBUG dialogs from TCC TCC/LE Support 1
Captain'Flam False condition in IF force loop exit (TCC/LE 14 64bits) TCC/LE Support 3
M How to get the number of chars, which fit in the currently displayed TCC-window? TCC/LE Support 3
M TCC/LE works with Windows Insider Skip Ahead Build 17618 TCC/LE Support 1
D Bug with TCC/LE and volumes mounted under directories TCC/LE Support 5
A TCC/LE x64 no longer works with Windows 10 Insider Preview Build 17063 TCC/LE Support 7
adam_0 TCC/LE string replacement differing from cmd.exe TCC/LE Support 3
D Incorrect icon for TCC/LE prompt here, Windows 10 TCC/LE Support 5
B Run TCC without interactive logon TCC/LE Support 0
T WAD option /u on TCC LE 13.06.77 TCC/LE Support 2
B Copy command to set timestamp not working in TCC/LE TCC/LE Support 5
R WAD TCC/LE does not set %_ffind_files TCC/LE Support 1
P Window width TCC TCC/LE Support 3
A installer for latest tcc/le isn't working TCC/LE Support 0
M Any plans for an updated TCC/LE version TCC/LE Support 16
miXza-81 Fixed There is Batch breaking bug in TCC LE (x64) TCC/LE Support 9
M Getting started with TCC/LE TCC/LE Support 3
John A TCC/LE not finding files in the c:\windows\system32\ directory? TCC/LE Support 4
Tim Rowe How to? TCC/LE colour not working with RSpec TCC/LE Support 14
R converting from NT to TCC/LE TCC/LE Support 3
jbanaszczyk [Q] How to retrieve / set current TCC/LE language TCC/LE Support 1
T C# Process.Start() never ends when starting TCC/LE process? TCC/LE Support 5
R WAD TCC LE pipe fails TCC/LE Support 6
M TCC LE x64 13.0 crash in Win 8 Pro 64-bit TCC/LE Support 0
A ftp on tcc/le TCC/LE Support 2
B What are the TCC settings that will allow maximum cmd.exe compatibility? TCC/LE Support 11
R TCC/LE attrib +/- C? TCC/LE Support 6
S Just wondering what TCC/LE 13.05.68 fixed TCC/LE Support 1
R TCC/LE steals the .btm association? TCC/LE Support 1
S Fixed TCC-LE 13.05.65 x64 "option" command tabs broken TCC/LE Support 4
rconn News TCC/LE 13.05 Released TCC/LE Support 0
F WAD Different value for %~dpfsI in TCC/LE TCC/LE Support 2
Charles Dye ? command, TCC/LE vs. supported TCC/LE Support 3
B TCC/LE prompt here TCC/LE Support 1
G Pin TCC/LE to task bar and start menu TCC/LE Support 6
jason404 A particular program that I like to use no longer works in TCC/LE TCC/LE Support 25
rconn News TCC/LE 13.04.56 Released TCC/LE Support 0
rconn News TCC/LE 13.04.55 Released TCC/LE Support 0
F Problem with TCC window colors TCC/LE Support 3
rconn News TCC/LE Version 13.03.45 Released TCC/LE Support 0
mfarah Things from the full TCC that I'd like to see in TCC/LE. TCC/LE Support 7
N how to terminate tcc/le using /h TCC/LE Support 15
rconn News TCC/LE Version 13.03.40 Released TCC/LE Support 0

Similar threads