Many files on the internet come in either .rar or .7z format. Puppy 2.17 (the last Puppy I stuck with for any period of time) had unrar by default, but Dingo does not. Nor do we have 7zip support. Well, I had some free time and decided to compile and package them.

These have been compiled under Puppy 4.00 from the source on the T2 Project website. Since the 7z executable and the 7za executable handle multiple formats that Puppy already has programs for, I replaced them with symlinks to the 7zr executable which should only handle .7z files.

These are recognized by XAarchive, but you have to open XArchive and then open the files, I can't figure out how to make XArchive open them by default (it tries to add them to a new archive).

If these give you trouble, you can also look for PeaZip which will handle both formats.

There are wrapper scripts in /usr/local/lib/xarchive/wrappers that control these functions. I recently patched the tar wrapper to accept 'xz' and 'lzma' tarballs. I just used the gz and bz2 as a template. For 7z and rar the zip may be a better model. They are just bash scripts - so if you are decent at bash you may be better able to fix it.

I also compiled the latest 7za and 7zDec in the 4.4 CE phase 1 pet test thread (7zDec is the best bang for the buck at <20kb pet) The latest 7za supports more formats but is a bit larger, so I will probably go with 7zDec only in the release... better to just convert them to .tar.xz after extraction anyways.

Thanks, technosaurus. Unfortunately I think my knowledge in these areas is much lower than yours. I'm quite newbie with Puppy ...

(I continue with my previous message)

(Specially for beginners, but also for everybody else)

(Problem and questions at bottom: specially for experienced, but also for everybody else)

2. To extract from .rar files using the context menu (compatible with 1.):

+ If not done already, the first 6 stepts of 1 have to be done (from Download ... to Save ..., both included)
+ In ROX-Filer (file manager), while holding shift key right click on any file or folder - click on Customise - click on OK
+ In that path ( /root/.config/rox.sourceforge.net/OpenWith ) create a directory and name it .application_x-rar
+ Go into the new folder (before click on the eye to show it -it's hidden because it begins by the dot-)
+ Open ROX-Filer again (it will open in a new window)
+ Go to /root/my-applications/bin
+ While holding Ctrl and shift keys drag rar_xtrct to the other ROX-Filer window (the one in /root/.config/rox.sourceforge.net/OpenWith/.application_x-rar ). This way a symbolic link will be created

To open the .rar file with the context menu:

a) Fastest: while holding shift right click on the .rar file and click on rar_xtrct (top)

Problem: the same as in 1.: it always extracts to /root , independently of where the .rar file is located. I know why: xterm (in the code of rar_xtrct) opens the console, and this one (rxvt) opens by default in ~ ( /root in other words). I've had a look to http://linux.die.net/man/1/xterm to try to find how to open the console in the path you want; but I found nothing. ROX-Filer knows how to do that: right click-Window-Terminal Here. I hope somebody knows how to do it or can look into ROX code to find the "secret".

Thanks, amigo. I'm not sure if I understand well the stated by you. I think you are outlining how the solution could be found. Yes? Please, if you have found the solution, if you could say step-by-step (for newbies like me) how to execute it it would be appreciated. Thank you

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum