(old)Puppy Linux Discussion Forum

new linux foxit pdf reader 2.4.4

https://www.foxitsoftware.com/pdf-reader/

zagreb999 wrote:new linux foxit pdf reader 2.4.4

https://www.foxitsoftware.com/pdf-reader/

I installed this FoxitReader 2.4.4
The install does not create a menu entry,

Attached is a PET file to create a menu entry in the Document menu after installing FoxitReader downloaded from the foxitsoftware site.

perdido wrote:after installing FoxitReader downloaded from the foxitsoftware site.

Which one?
I downloaded FoxitReader.enu.setup.2.4.4.0910.x86.run.tar.gz , which eventually created a monster: 254MB for the installation directory, The FoxitReader executable alone amounts to 87MB (and doesn't even start in Slacko 5.6). Is there a slimmer version?

My current FoxitReader 1.1.0 takes merely 4MB. Only annoyance: Would always open with Navigation Panel visible, no way to keep it off by default

Works for me in XenialPup (32), although I had to rename the setup file because the name kept triggering a syntax error when run. MochiMoppel - have you tried running FoxitReader from a terminal to see what error messages pop up?

Yeah, it's a bit... big. If I run FoxitReader's binary through UPX, though, it goes from around 87MB to 27MB, and still runs. Haven't tried compressing any of the other files in the directory.

Makoto wrote:MochiMoppel - have you tried running FoxitReader from a terminal to see what error messages pop up

This one: I can read the manual. From what I can see there are no new features that would make an update worthwhile.

MochiMoppel wrote:Which one?
I downloaded FoxitReader.enu.setup.2.4.4.0910.x86.run.tar.gz

Same version FoxitReader I used. I ran it inPrecise-Light-5.7.1

I did some testing, the Foxit will not start in the original Precise 5.7.1 due to an older GLIBC, it needs at least GLIBC_2.17 I checked out Slacko 5.6 PAE and it has an older GLIBC and refused to run.

There is a workaround to this if you want to upgrade GLIBC
If you do this pay attention to the install order, the gcc-4.9.2.pet needs to be installed last or system could hang/crash.

After updating GLIBC in Slacko 5.6 PAE and installing and loading FoxitReader2.4.4 the program started right up.
I did not even have to save to the save file, just loading the PET files was enough.
I downloaded the files from Battleshooter's post that has a GLIBC 2.20 upgrade, had to get the files from archive.org (thanks Ally!) because no longer available at links.

Here are some working links for the files

Downloads
glibc-2.20.pet 27.7 MB - https://archive.org/download/Russoodles ... c-2.20.pet
gcc-4.9.2.pet 35.8 MB - https://archive.org/download/Russoodles ... -4.9.2.pet
binutils-2.24.pet 11.5 MB - https://archive.org/download/Russoodles ... s-2.24.pet

GCC dependencies:
gmp-6.0.0.pet 636 KB - https://archive.org/download/Russoodles ... -6.0.0.pet
mpc-1.0.2.pet 110 KB - https://archive.org/download/Russoodles ... -1.0.2.pet
mpfr-3.1.2.pet 469 KB - https://archive.org/download/Russoodles ... -3.1.2.pet

If you want to look at whats there in that archive here is the link
https://archive.org/download/Russoodles ... tleshooter

.

Makoto wrote: Yeah, it's a bit... big. If I run FoxitReader's binary through UPX, though, it goes from around 87MB to 27MB, and still runs. Haven't tried compressing any of the other files in the directory.

Code: Select all

upx -9 FoxitReader
                       Ultimate Packer for eXecutables
                          Copyright (C) 1996 - 2018
UPX 3.95        Markus Oberhumer, Laszlo Molnar & John Reiser   Aug 26th 2018

        File size         Ratio      Format      Name
   --------------------   ------   -----------   -----------
  91164098 ->  27642400   30.32%   linux/i386    FoxitReader                   

Packed 1 file.

Wow, thats a great utility. Thanks for showing that trick

.

You can use upx -9 *.* to let it automatically try compressing everything in a directory (and skipping whatever can't or shouldn't be compressed).

I think I got Foxit's directory down to about 130MB after running through all the subdirectories... but then it wouldn't run, so I'm guessing it doesn't like one or more of the libraries being compressed.