Peazip Rar
Jesper Sahu
Unfortunately, /usr/lib/peazip/peazip was an executable. Double-clicking on it ran PeaZip. The search for an accompanying folder yielded only one possibility: a folder named res next to that peazip executable. In res, the only folder was bin; and in bin, the folders appeared to provide information for the executable on various compression algorithms (e.g., 7z, brotli, zstd).
For a moment, it appeared that GNOME had switched over to a Firefox type of update numbering, where the winner was the one who got to 1,000 first. Wikipedia seemed to say that, in 2021, the GNOME people cheated a bit in this: they leaped directly from GNOME 3 to GNOME 40, presumably because that was 2x 21. I could only surmise that, for PeaZip and me, the GNOME 3 instructions were more likely to work on my GNOME 42 system than were the GNOME 2 instructions.
I am having trouble getting the Peazip contextual menu to show up in DO. It works fine in explorer, but when I right click on an archive, or any other file in DO, the Peazip menu isn't there. This is the first app I have had this problem with.....every other app I have tried that has a contextual menu has worked fine. So,I would appreciate any help on getting it to show up in DO.
Nope it doesn't show with shift-click. It's really weird, cause every other app I have installed show correctly. I tried fiddling in the file preference in DO, but don't know much about that are so I didn't really test anything very useful.
I suppose it's possible Opus might not support this new method of Windows context menu handling (which - really, is just a more cumbersome version of how Opus allows context menu modification - but I guess it's mainly intended for app developers). GPsoft will have to weigh in on that...
It could just as easily be something that's supposed to work "already" but for some reason is "not" working in just this particular case - but I don't have a guess what would be causing it (other than what Leo asked about) seeing as how it's unlikely to be any of the "recent" issues having to do with 32bit/64bit conflicts and such... even if you're running a 64bit OS.
At any rate - the upshot is that PeaZip just adds very simple "command line" calls into the registry to it's executable in order to do any of the things that it does with Context Menu actions (f.ex. "C:\Program Files\PeaZip\PEAZIP.EXE" "-add2multizip" "%1") as opposed to using a shell extension context menu handler dll. So, it'd be pretty easy to "recreate" them as Opus specific context menu entries as well - until GPsoft can comment. Shout if you're interested and need help.
Kudo's to Microsoft by the way - for finally implementing what seems to be a very "easy" way of modifying the context menu structure. Unfortunately, by remaining "backward" compatible for the sake of supporting older apps - this just means we've got yet ANOTHER place to look when things aren't working exactly as expected.
Make sure Preferences / Miscellaneous / Windows Integration / Hide Windows items on file context menus (shift overrides) is turned off (or try holding down shift when you right-click, as per earlier in the thread).
In the image I have posted below, my peazip appears in this subfolder and it looks like yours, with the "add to archive," but it does not do anything when clicked. you can also see explorers context menu on the right
with the commands that should be shown.
As you can see in the definition in the image below its setup in "All Folders" the thing is foobar does not show in the submenu and I have no idea
how peazip got in there either as i have just installed peazip yesterday for the first time.
I checked the other file types and no other types have entries, well except "All Files" which has one action in it.
I tried deleting the peazip entry and running the peazip integration setup again but it reappears in that submenu.
That said, I just installed Peazip 5.20 as well. Context Menu worked fine like with Leo. I then moved that weird Peazip entry that also got created on my system under a new 'Folder Options' sub-menu myself - and it immediately stopped working. I can't fix it by moving the item back (in fact, it disappeared after I added it under the sub-menu // wasn't there when I went back to re-edit the menu.
Note: by re-running PeaZip install, and selecting to reset the configuration... I got the PeaZip context menu definition back at the top level of the menu. However... it also doesn't seem to work. Selecting the one 'Add to Archive' menu item doesn't appear to do anything. But it's also not clear to me if PeaZip is sending an archive to some pre-configured destination folder. The Settings interface isn't very clear in this regard...
[quote="steje"]2. While you do indeed see a Peazip menu in your menu popup screenshot under your Folder Options sub-menu - I don't see why you even see that much... you've got it in your context menu definitions, so I don't understand why it would even show you anything at all there in the actual menu popup.
That said, I just installed Peazip 5.20 as well. Context Menu worked fine like with Leo. I then moved that weird Peazip entry that also got created on my system under a new 'Folder Options' sub-menu myself - and it immediately stopped working. I can't fix it by moving the item back (in fact, it disappeared after I added it under the sub-menu // wasn't there when I went back to re-edit the menu.[/quote]
Well as I have already said I did not add it the peazip entry and, as you say, it show "not defined" but it definitely runs When I click it, peazip shows in taskman but with no command line arguments!
As an update:
I was checking through other File type definitions and noticed that "File Types" -> "System file types" contains;
"udefrag.W7menu" aka, ultradefrag,
and is showing its command line as "". this app does shows in windows explorer - as shown in images above.
Someone said that the win7 context menu system was a bit more intuitive, I would disagree. It is so much more convoluted time consuming and there are fewer apps willing to tackle the easy management of the context menus.
Ark compressor also crashes when trying to compress this file, and so is fileroller. This is why I guess the problem lies in 7z, but I don't actually know for sure, because if I use peazip and try to compress the file to a single volume *.zip, it will also crash. But on the other hand I think zip compression is also done by 7z.
This was guessable also the problem why ark and fileroller crashed before, since I kept the peazip error window open and it won't release its temp file in /tmp till its closed and the whole system reacted strangely in this time.
c80f0f1006