HELP! Shell integration completely broken.
-
also, please make sure that you have enabled Shell extensions in Configuration > Shell extensions.
-
BTW: to extract multiple archives you can use the Multi Extract tool in PowerArchiver…
-
@NTFS:
also, please make sure that you have enabled Shell extensions in Configuration > Shell extensions.
Just to re-enforce this suggestion - if you choose the “Add as Submenu” option, then this should be available even when Zip files are NOT associated with PowerArchiver.
-
@NTFS:
Welcome to PowerArchiver forum, Sigh!
first, PowerArchiver does not use Windows’ Zip Folders. PA creates it’s own association. you can repair it in Configuration > File Formats > Associate now.
Also you don’t need to reinstall windows to fix zip folders association. just right click any file > Send to >Compresses zipped folder… Then windows will ask you if you want to associate files. click Yes.
1st, yes powerarcher uses the zipfldr REGISTRY ALIAISING LINK, not the zipfldr.dll.
2, I’m really fcuking pissed that you dumbed down my real problem with some simpleminded filetype association newbee moron idiocy.
The REGISTRY for the entire shell extension integration is FCUKED! I’m NOT asking you for help on that. It’s beyond you, waaaaaaaaaay beyond you.
What I want is the command line arguments for powerarc.exe …what are the command line switches? That’s all I want to know. NOTHING ELSE!!!
-
This post is deleted! -
@NTFS:
also, please make sure that you have enabled Shell extensions in Configuration > Shell extensions.
Yeah, IT’S FCUKING BROKEN IN THE FCUKING REGISTRY. Maybe you could suggest some magic “registry heal thyself” button.
I’ve run “regsvr32 zipfldr.dll” also run direct .reg scripts to restore all zipfldr functionality to its original condition, but to no avail, there is no shell integration on zipfldrs. When I install powerarchiver, it does all the right things, all the registry settings seem to be 100% correct, but guess what, STILL NO FCUKING SHELL INTEGRATION MENU. If it doesn’t work with zipfldr, just how the fcuk do you think it will work with powerachiver, which uses the same registry attachment technique as zipfldr.
If powerarchiver used actual command line arguments, then I could restore shell integration, but becuase powerarchiver attaches thru a registry key, {d03d3e68-0c44-3d45-b15f-bcfd8a8b4c7e} to be specific, shell itegration will not work.
So what are the command line args to powerarc.exe?
That’s all I want to know, nothing more, nothing less.
-
Just to re-enforce this suggestion - if you choose the “Add as Submenu” option, then this should be available even when Zip files are NOT associated with PowerArchiver.
Duuuuhhhh, NO FCUKING censoredcensoredcensoredcensored. But it does NOT.
That whole registry mechanism is totally fcuked. It’s beyond hope, totally not even a consideration at this point. I don’t want help with it, I don’t even want to mention it again.
All I want to know is the powerarc.exe command line switches. If I had those the rest would be a frickin cakewalk.
-
For command line use please try PowerArchiver Command Line:
http://www.powerarchiver.com/pacl/
It is free to registered PowerArchiver users.It contains all the documentation you need.
-
but here is what you want:
ShellExt Command line args for powerarc.exe:
Extract to…: -et
Extract here: -e
Add to archive…: -aZIP
Add to FileName.zip: -aZ -
Duuuuhhhh, NO FCUKING censoredcensoredcensoredcensored. But it does NOT.
That whole registry mechanism is totally fcuked. It’s beyond hope, totally not even a consideration at this point. I don’t want help with it, I don’t even want to mention it again.
All I want to know is the powerarc.exe command line switches. If I had those the rest would be a frickin cakewalk.
you should be a lot nicer to people trying to help you deal with your issue. NTFS has correctly answered to your issue (-e).
