Incorrect temporary path to external un-RAR application

[byblo]

It seems TC 9.51 is sending to the external application parameter the subfolder too for a temporary extracted file, when it is supposed not doing it.
This happens only with the disabled TC's option: Packer\"Use internal un-RAR if possible"

For instance:
app.exe "c:\temp\_tc\folder\test.txt" instead of "c:\temp\_tc\test.txt"


Here is a simple rar file containing a text file into a folder for quick testing:

Code: Select all

MIME-Version: 1.0
Content-Type: application/octet-stream; name="folder.rar"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="folder.rar"

UmFyIRoHAQCFRCREDwEFCwgKAQOUg4AAjYSAAJ4FA28rAgMLqwIEqAMgpWD6vYADAA9mb2xkZXIv
dGVzdC50eHQKAwJTOjGVPEXWAcm1JwE2dTMzP1cDTeATg5DxsmFgFwuFmdFyudEFubAoUTTrQrjT
CSkcvfqB+KclonGGGGz5e/lHkh8SUSUiV4/fcfm7nPZPnPalr73JOCR44JCKOsfMDjDgnv6J5bPH
w6YPwk+xTNx7u89yMi25/I/8g5cghJm8Z7P33SGbGb4YDz7Mb9ujXV8Scq+RscGXoQ3fRF9qYwkO
FXKtOg89SVldDjeMtrChP8OtVOCEhpN4xcH1MaRgXnnRxtktogIDymrIpZQhAXwOicFjgPFSgqPh
afwtbaVRL3lCitfJ7sv7tSj603q6jYTGanIQB8PrOG6ucWL2aFuYUuO/qKaxQA2R069ZjiQGszj2
pcNhwnLU3bXSlV/M219FS5ypv7Uu1jBllHvtNf5GvToAFyc/PCACAwsABQAQAAAAAIAAAAZmb2xk
ZXIKAwJTu0kMO0XWAV9PV1AOAwbmAADmAACAAAACUU8hvVHINACAAzCeBQNvKwIDC6sCBKgDIKVg
+r2AAwAPZm9sZGVyL3Rlc3QudHh0CgMCUzoxlTxF1gED2TYXKAAlJRcnPzwgAgMLAAUAEAAAAACA
AAAGZm9sZGVyCgMCU7tJDDtF1gGNUjRNEgMHA+YEAOYEAIAAAAJSUgIHAXtSQn0tnEBQpqU3gGYC
AABQAAAAAQEAAAAAAAAAABYCAAAVAgAAAAAAABYCAAAAAAAAZgIAAAAAAAABAAEAAAAXvtwNW00Z
MwYADAYZvvy0UmFyIRoHAQCFRCREDwEFCwgKAQOUg4AAjYSAAJ4FA28rAgMLqwIEqAMgpWD6vYAD
AA9mb2xkZXIvdGVzdC50eHQKAwJTOjGVPEXWAcm1JwE2dTMzP1cDTeATg5DxsmFgFwuFmdFyudEF
ubAoUTTrQrjTCSkcvfqB+KclonGGGGz5e/lHkh8SUSUiV4/fcfm7nPZPnPalr73JOCR44JCKOsfM
DjDgnv6J5bPHw6YPwk+xTNx7u89yMi25/I/8g5cghJm8Z7P33SGbGb4YDz7Mb9ujXV8Scq+RscGX
oQ3fRF9qYwkOFXKtOg89SVldDjeMtrChP8OtVOCEhpN4xcH1MaRgXnnRxtktogIDymrIpZQhAXwO
icFjgPFSgqPhafwtbaVRL3lCitfJ7sv7tSj603q6jYTGanIQB8PrOG6ucWL2aFuYUuO/qKaxQA2R
069ZjiQGszj2pcNhwnLU3bXSlV/M219FS5ypv7Uu1jBllHvtNf5GvToAFyc/PCACAwsABQAQAAAA
AIAAAAZmb2xkZXIKAwJTu0kMO0XWAV9PV1AOAwbmAADmAACAAAACUU8hvVHINACAAzCeBQNvKwID
C6sCBKgDIKVg+r2AAwAPZm9sZGVyL3Rlc3QudHh0CgMCUzoxlTxF1gED2TYXKAAlJRcnPzwgAgML
AAUAEAAAAACAAAAGZm9sZGVyCgMCU7tJDDtF1gGNHXdWUQMFBAA=
[\code]

[ghisler(Author)]

I have tried to reproduce this error, but failed. Here is the command line sent by TC:
d:\utils\Winrar\winRar.exe e -c- "e:\test\external un-RAR.rar" C:\Temp\_tc @C:\temp\CMD8654.tmp
with CMD8654.tmp containing:
folder\test.txt

The parameter 'e' instructs winrar to unpack files without path. Maybe you have an option in winrar.ini to override this?

[gdpr deleted 6]

It also depends on what operation you are actually triggering.

If you are showing the file in the lister (F3), then TC unpacks the file without the path.

However, if you are going to open the file in the editor (F4) or let it open with whatever other application associated with the respective extension of the file (ENTER key), TC unpacks the file _with_ the path. Which makes sense, as TC needs to keep track of the complete relative file path in some way to be able to correctly pack/update it back into the archive in case the editor/external app has changed the file. This is the behavior regardless of whether you are using the built-in or an external unrar.

[byblo]

I forgot if the bug was also happening after pressing F3 or only F4. I retried but could not reproduce it with F3.

But indeed pressing F4 will extract without the subfolders the file to edit to the TC's temporary folder, while giving to the external editor the full path.

For example : Pressing F4 will extract the file to -->
r:\Temp\_tc\test.txt

then TC will start external editor and will give the path to edit-->
r:\Temp\_tc\folder\test.txt

[gdpr deleted 6]

I cannot confirm the observations you described in your last post.

If i take your folder.rar archive from your opening post and hit F4 on test.txt inside the archive, TC unpacks the file with its relative path from the archive, i.e.:

Code: Select all

%TEMP%\_tc\folder\text.txt

I suspect one of two things with regard to your observation:

One, the test.txt you are seeing there in your _tc temp folder is a leftover from previous experiments, perhaps. To make sure (if you have not done so already), delete the whole _tc folder, try the F4 test again and then check the content of the _tc temp folder.

Two, the external unrar tool you are using, or the commandline for the external unrar tool you told TC to use (which we don't know anything about) is (mis)configured or limited in a way that it always ignores the relative path from the archive while unpacking (regardless of whether TC employs additional commandline arguments enabling or disabling unpacking with relative paths), which could lead to the effect you observed.

[byblo]

Nevermind it seems my winrar ini file is messed for some reason. I tried with fresh winrar config and it is working correctly again.

Will try to find out what is wrong with winrar settings. It seems some settings has priority over the sent commandline...

This said, impossible to extract a subfolder without winrar complaining about the missing path, but seems another problem.

[Hacker]

[mod="Hacker"]Moved to the English forum.[/mod]