Extract to network share not possible?

[AVE160]

Some weird just occurred to me:
I have an archive (rar) and want to extract the files to another computer. Due to password problems I have setup TC to use Winrar for handling the rar archives. When I do a copy F5 to \\server\share the files are unpacked to the local directory, not the network share.

Is this intentional or is it a bug?

[ghisler(Author)]

Try using WinRAR.exe instead of Rar.exe. I have just tested with WinRAR.exe, and it works.

[AVE160]

I am using winrar version 3.51 and TC 7.0pb4

Now using my pc with XP and tried to unpack to a share on the same computer. The files end up in the same directory the archive located.

For the record: I am extracting to a UNC path, not a mapped drive.

[Flint]

Cannot reproduce. Tester on XP SP2 Pro, TC7rc3, WinRAR 3.62. Unpacking with Alt+F9 from the left panel (local drive) to the right one (UNC-path).

<ADDED>
Tested with copying from archive via F5 - results are the same.
All tests were performed with the local share \\<my-computer>\Incoming.

[StatusQuo]

When I do a copy F5 to \\server\share the files are unpacked to the local directory, not the network share.

Confirmed (TC7rc3, WinRar 3.62, W2k).
This seems to apply only to local shares (both via \\127.0.0.1\share and using the external IP of the local PC), this problem does not exist with remote shares on other PCs.
Also everything is going right when using Alt-F9 to extract the whole archive.

But (after opening the archive in TC) using F5 to copy single files or dirs fails, the extracted files/dirs are extracted to the local dir the archive is in.

To reproduce:
- make shure "Use internal un-RAR if possible" is NOT checked in Options / Config. / Packer
- open rar file on the left
- open a (local) share on the right panel (\\127.0.0.1\c)
- use F5 to copy a single file or dir to the share on the right panel
=> It will be extracted to the dir of the rar that is opened on the left side.

[Flint]

- make shure "Use internal un-RAR if possible" is NOT checked in Options / Config. / Packer

Ah, that's the point! Now I can confirm the problem. However, I can't tell whether it is a bug of TC or WinRAR...

[AVE160]

Neither do I.
I can try giving the commandline options to WinRAR directly, if I only knew what they were
Doing a manual unpack of a .rar file with winrar (manual=from the commandline) the files are extracted to the networkshare, but that was without much options and I do not know what options TC gives to the external unpacker.

[Flint]

and I do not know what options TC gives to the external unpacker.

You can check it with my simple test program from this post.

[ghisler(Author)]

Here is the command line passed to WinRAR:

c:\WinRAR\winrar.exe x -c- E:\test\test.rar \\server\share @c:\temp\CMD363.tmp

The file CMD363.tmp contains the file names of the files which need to be unpacked. You can write *.* instead of it to extract all files.

I can confirm that WinRAR tries to extract to the directory of the rar file when trying to unpack to the root of the share. This seems to be a bug in WinRAR. It seems to work when I specify \\server\share\ with a trailing backslash instead of just \\server\share ...

As a workaround, I will append a backslash for the RAR packer if the target is the root of a share.

[StatusQuo]

I can confirm that WinRAR tries to extract to the directory of the rar file when trying to unpack to the root of the share. This seems to be a bug in WinRAR. It seems to work when I specify \\server\share\ with a trailing backslash instead of just \\server\share ...

As a workaround, I will append a backslash for the RAR packer if the target is the root of a share.

Fully confirmed here, and a trailing backslash seems to help.

[ghisler(Author)]

Should be fixed now in RC4, please test!

[Flint]

Yes, confirm fixed.

[StatusQuo]

Confirm, fixed in RC4.

[ghisler(Author)]

Thanks for checking it!