rpbtf Jul 1 0 Jul 18, 2012 #1 TPIPE, used with parameter /simple=23 to encode a file and (as another command) /simple=24 to decode this file adds 0F (hex) at the end of the file. Windows 7 x64, TCMD 14.00.29
TPIPE, used with parameter /simple=23 to encode a file and (as another command) /simple=24 to decode this file adds 0F (hex) at the end of the file. Windows 7 x64, TCMD 14.00.29
epement Jun 70 2 Jul 18, 2012 #2 rpbtf said: TPIPE, used with parameter /simple=23 to encode a file and (as another command) /simple=24 to decode this file adds 0F (hex) at the end of the file. Windows 7 x64, TCMD 14.00.29 Click to expand... FWIW, I do not get these results with WinXP 32-bit, TCMD v14.00.29. Someone with 64-bit Win7 should test on their version. Here's my results: Code: [C:\Program Files\JPSoft\TCMD14]type updater.ini | tpipe /simple=23 | tpipe /simple=24 /output=test.me [C:\Program Files\JPSoft\TCMD14]fc /b updater.ini test.me Comparing files updater.ini and TEST.ME FC: no differences encountered HTH. Eric
rpbtf said: TPIPE, used with parameter /simple=23 to encode a file and (as another command) /simple=24 to decode this file adds 0F (hex) at the end of the file. Windows 7 x64, TCMD 14.00.29 Click to expand... FWIW, I do not get these results with WinXP 32-bit, TCMD v14.00.29. Someone with 64-bit Win7 should test on their version. Here's my results: Code: [C:\Program Files\JPSoft\TCMD14]type updater.ini | tpipe /simple=23 | tpipe /simple=24 /output=test.me [C:\Program Files\JPSoft\TCMD14]fc /b updater.ini test.me Comparing files updater.ini and TEST.ME FC: no differences encountered HTH. Eric
vefatica May 12,965 172 Jul 18, 2012 #3 On Win7/32 if I do this Code: tpipe /input=avetemp.txt /simple=23 | tpipe /simple=24 I see an unprintable at the end. If I do this Code: tpipe /input=avetemp.txt /simple=23 | tpipe /simple=24 | list /x and go to the end, that unprintable appears to be 0xFE. And if I try (nearly) Eric's test, Code: g:\tc14> type updater.ini | tpipe /simple=23 | tpipe /simple=24 /output=test.me g:\tc14> *fc /b updater.ini test.me Comparing files updater.ini and TEST.ME FC: TEST.ME longer than updater.ini A hex editor reveals 0xFE at the end.
On Win7/32 if I do this Code: tpipe /input=avetemp.txt /simple=23 | tpipe /simple=24 I see an unprintable at the end. If I do this Code: tpipe /input=avetemp.txt /simple=23 | tpipe /simple=24 | list /x and go to the end, that unprintable appears to be 0xFE. And if I try (nearly) Eric's test, Code: g:\tc14> type updater.ini | tpipe /simple=23 | tpipe /simple=24 /output=test.me g:\tc14> *fc /b updater.ini test.me Comparing files updater.ini and TEST.ME FC: TEST.ME longer than updater.ini A hex editor reveals 0xFE at the end.
Stefano Piccardi May 382 2 Jul 19, 2012 #4 I do not get these results with Win7 32-bit, TCMD v14.00.29 Code: [C:\]ver TCC 14.00.29 Windows 7 [Version 6.1.7601] [C:\]type updater.ini | tpipe /simple=23 | tpipe /simple=24 /output=test.me [C:\]fc /b updater.ini test.me Comparing files updater.ini and TEST.ME FC: no differences encountered
I do not get these results with Win7 32-bit, TCMD v14.00.29 Code: [C:\]ver TCC 14.00.29 Windows 7 [Version 6.1.7601] [C:\]type updater.ini | tpipe /simple=23 | tpipe /simple=24 /output=test.me [C:\]fc /b updater.ini test.me Comparing files updater.ini and TEST.ME FC: no differences encountered