Different behaviour when unpack to write-protected folder

[MVV]

When I try to unpack the whole archive or some files into write-protected folder, TC behaviour depends on target folder existence:

When I try to unpack to existing folder (I type new target path or choose unpack to dir with archive name), TC says folder is write-protected and asks to unpack as admin.

But when I want to unpack to a new folder, TC just does labour of Sisyphus - it shows the progress window, it shows how files being unpacked, BUT no 'unpack as admin' dialog shows and no files are placed into target dir because it doesn't exist.

Expected behaviour: when user tries to unpack to a non-existing folder and TC can't create it because of write-protection, TC should ask user to perform an operation as admin (to create target folder and to place unpacked files into it).

The one idea of this topic - to ask user for folder creation as admin before unpacking because the rest of the unpack process TC does well.

[ghisler(Author)]

Sorry, I don't understand your report. Here is what I tried:
1. Place cursor on zip file
2. Press Alt+F9
3. Change target dir from c:\somedir to c:\somedir\new

-> TC creates subdir "new" and unpacks files to it.

What are you doing differently?

[StatusQuo]

Confirmed in TC 7.5 pb5.

2ghisler(Author)
Create a new directory c:\test\readonly,
then change your own access there to read only (and Admin's to full access; removing all other access rights):

Code: Select all

cacls c:\test\readonly /g your_username:R Administrator:F

Now use F9 to unpack from zip:

Access denied!
[OK] [As Administrator]

Error writing (path\filename)!
[OK] [Cancel]

[ghisler(Author)]

I see - indeed this isn't currently supported, sorry. Maybe in a later version.