Apparent glitch with some encryption via shell
I say “apparent,” 'cause perhaps I missed something. But I tried it three times . . . and had the same problem every time.
I have created a Profile called “ZIPX + PAE” – all with optimal settings. (I have a similar one for 7ZIP + PAE). The problem happens when I am tying to create a new PAE file using the former profile – in one cases.
Here’s what I found – all within the shell (highlight the files, then select PA and Compress To).
- the 7 zip/pae profile worked just fine – even if I renamed the file.
- the zipx worked fine if I did not rename the file.
- But if I tried to rename the file, it would not create the archive to be encrypted – it went straight to the encryption window . . . without having first created the archive.
I may just be missing something. But, as I said, I tried it thrice with the same result.
I did go back and recheck the definition of the profile. Everything looks to be in order.
hmmm, lets give it a check
Thanks. I am really not 100% sure. I may be overlooking something obvious. But it kept happening when it wasn’t happening with the parallel 7Z profile.
I appreciate it.
It happened ONLY when I renamed the file. I thought it might be a problem with the name (had a dash). But the 7Z profile worked.
Could you email me the .reg settings please?
Also, you’re changing the name in the full path field in the compress options menu or?
Also#2, is a PAE file created at the end or there’s no PAE file at all?
I tried it again. Every worked fine with the 7zip + PAE profile. But this time, I couldn’t even get the encryption window to open with the ZIPX +PAE profile. But these were different files, including different files types. That may have made a difference.
I attached a pic of the zipx profile in case I am missing something simple.
I am changing the name in the add window, which standardly opens first, and then - after the archive is created - the encryption windows (normally) opens. But not now with ZIPX +.
No PAE2 is created.
great, we’ll replicate and post the results. thanks!
I deleted the profile. Create a new one – exactly like the old.
It worked just fine.
So somehow that profile must have been corrupted, although the settings looked fine.
But maybe if you peek, you can figure out what.
Or prudence may demand ignoring it.
Attached is a comparison of the two:
The “new one” has “Use current folder as temp” (which is what I usually have set).
Could this have made the difference?
hmmm, i’ve tried using both ways and both work fine for me. But when I use your .reg settings, I get the issue you referred to.
I’ll be logging it in and do some further investigating to see what the culprit might be.
thanks very much for the details!
So a culprit lurking in the reg settings. The mystery deepens.
I went fishing in my config settings.
I discovered the cause of my problem reported a month ago (that you could not duplicate). Perhaps it is source of this problem as well.
Burning support was set to “autodetect.”
I changed it to SPTD, and the .iso window open exactly as it was supposed to – no 38 sec delay!
Maybe it is also causing this problem?
I have no idea how the setting got switched . . . it has always been SPTD. Maybe it was with one of the updates?
Actually, glad to know that I was not nuts claiming there was a 38 second delay in having the iso windows open!