Pale Moon 'portable' browsers - 32- & 64-bit

[keniv]

If DpupStretch is up to date could I simply install the .deb?

[amethyst]

The .deb installation should work. I've downloaded the tarballs for Firefox and Palemoon directly from their homepage a while ago and made sfs files. I don't install stuff. DpupStretch runs all the new browsers OOTB as far as I know.

[keniv]

Thanks for that. I noticed that Mike posted a link to the.deb about the third post in the thread. Might try with pfix=ram just in case.

Regards,

Ken.

[mikewalsh]

@keniv :-

Ken, you should find this one works:-

https://drive.google.com/file/d/1HnnwHm ... sp=sharing

This is the first attempt I made at 28.17.0, and I was in DPup 'Stretch' at the time. This one doesn't need all the glibc stuff; it's a straight-forward build, and should work OOTB.

Let us know what happens, please..!

Mike.

[keniv]

@mikewalsh
Hi Mike,
Thanks for the link to the Dpup Stretch version of palemoon 28.17.0 portable. I've downloaded and installed it and am posting from it now. As you suggested I move the profile folder out of the legacy version and system linked it back. I couldn't think of a reason why I couldn't use the same profile for the Dpup Stretch version so I system linked it back to this version after renaming the original profile folder to profileorig in case anything went wrong. However, both versions are working using the same profile and unless there's a good reason not to do this I'll leave it as is but will remove the folder I renamed to profileorig. It strikes me that the above might not be very clear so I hope it's OK.

Regards,

Ken.

[mikewalsh]

@keniv :-

Nah, I know just where you're coming from. I share profiles between multiple browsers myself.

For instance:-

• 32- and 64-bit versions of the same release of FF-esr share a profile

• Ditto for different arches of the same release of FF-Quantum

• Ditto for different arches of the same release of Iron

• Ditto for different arches of the same release of Vivaldi

• Ditto for different arches of the same release of Pale Moon

.....etc, etc. I think you get the picture, yes?

For the Chromium 'clones', everything in the profiles is 'shared' with the exception of the WideVine stuff; it's the only item that is architecture-specific.

Anyway, glad to hear it's working for you. Enjoy.

Mike.

[keniv]

@mikewalsh
Hi Mike I'm sorry to say I have another problem. I decided to make a .desktop entry and make 28.17.0 the default browser. This worked well with Racy but not with DpupStretch. In Racy I called the menu entry file palemoonport.desktop. I did it by manually editing the existing palemoon.desktop file. Here it is.

Code: Select all

[Desktop Entry]
Encoding=UTF-8
Name=Palemoonport
Icon=/usr/share/icons/mozicon128.png
Comment=Palemoon web browser
Exec=/mnt/home/PaleMoon32+_glibc219-portable_legacy/LAUNCH
Terminal=false
Type=Application
Categories=X-Internet
GenericName=Palemoon web browser

I used the default application chooser to make 28.17.0 the default browser. Here it is.

Code: Select all

#!/bin/sh
exec /mnt/home/PaleMoon32+_glibc219-portable_legacy/LAUNCH "$@"

Both of the above work.
Please note that the paths to LAUNCH in both of these files start with /mnt/home/.
This is not the case with DpupStretch. Here is the the palemoonport.desktop file I made for DpupStretch.

Code: Select all

[Desktop Entry]
Encoding=UTF-8
Name=Palemoon Portable
Comment=Browse the Internet
Exec=/initrd/mnt/dev_save/PaleMoon-portable/LAUNCH
Icon=/usr/share/icons/mozicon128.png
Terminal=false
StartupNotify=false
NoDisplay=false
Type=Application
Categories=X-Internet-browser;
GenericName=Palemoon Portable
MimeType=

.
This works but I don't understand the path shown above. Basically I have a hdd split into two partitions. sda1 is formatted ntfs and sda2 as ext4. All my puppy's are manual frugal installs on sda1. Both Racy and DpupStretch are 32bit and on this partition and both have save files. I have save folders for a couple of modern 64bit puppy's and 64bit BusterDog on sda2. When I click on sda1 in Racy it sees it as /mnt/home/. When I click on sda1 with DpupStretch it sees the same partition as /initrd/mnt/dev_save/. Using this path in the .desktop file works in DpupStretch as a menu entry for 28.17.0 but does not work in the case of making it the default browser. With palemoon 28.16.0 as the default browser the code is

Code: Select all

#!/bin/sh
exec palemoon "$@"

With 28.17.0 the code I've tried is

Code: Select all

#!/bin/sh
exec /initrd/mnt/dev_save/PaleMoon-portable/LAUNCH "$@"

I've also tried

Code: Select all

#!/bin/sh
exec /initrd/mnt/dev_save/PaleMoon-portable/LAUNCH

and

Code: Select all

#!/bin/sh
exec palemoonport "$@"

None of the above worked with 28.17.0 so I'm now stuck. I'd welcome some help with this .

Regards,

Ken.

Edit: Now have default browser working (ie 28.17.0 is default browser) in DpupStretch but still don't understand the /mnt/home/ versus /initrd/mnt/dev_save/.

[mikewalsh]

Hallo, Ken.

Mm. You know, you're not the only one to notice this. From what I can make out, this seems to be 'standard behaviour' in all recent, Woof-CE-built Puppies; instead of seeing the 'base' layer as /mnt/home, they all now see it as simply a layer of the union aufs file system. Like you, I, too, first noticed this with Stretch.

The advice I'll give you is this; despite being seen by the system as /initrd/mnt/dev_save, it's still /mnt/home! Both $PATHs point to the exact same location.....and /mnt/home still exists. It's still there.

Did you actually try it with /mnt/home before using the /initrd/mnt/dev_save $PATH? I'm betting if you modify it back to /mnt/home, it'll work just fine..... Despite them using this different 'label' nowadays, I still use the 'old' way of doing things, and to date, it's given me no issues whatsoever.

Give it a try. Let us know what happens, please.

Mike.

[amethyst]

/initrd/mnt/dev_save is only /mnt/home if you have a savefile/folder.

[mikewalsh]

/initrd/mnt/dev_save is only /mnt/home if you have a savefile/folder.

.....which most folks DO have (though not all). But, yes; I take your point.

However; why is it that this location on older Puppies always showed the actual $PATH (e.g., a flash drive, one partition, formatted Ext2/3/4; say, /mnt/sdb1?), whereas modern Puppies always, without fail, seem to show it as a location in the union aufs system?

This, to me, shows that some of the code at Woof-CE has been re-written slightly....apparently, giving Puppy's aufs system priority in the 'naming' scheme.

Mike.

[amethyst]

Savefile/folder in use > /mnt/home is a link to /initrd/mnt/dev_save (new Puppys seem to use only /initrd/mnt/dev_save)
No savefile/folder, pfix=copy/ram > puppy partition indicated as a drive like /mnt/sda3, no /mnt/home
No savefile/folder, pfix=nocopy > puppy partition is /initrd/mnt/dev_save, no /mnt/home (I've seen an exception with Tahr where it's /initrd/mnt/dev_ro2 in this scenario if I remember correctly!!!)

[keniv]

Did you actually try it with /mnt/home before using the /initrd/mnt/dev_save $PATH? I'm betting if you modify it back to /mnt/home, it'll work just fine..... Despite them using this different 'label' nowadays, I still use the 'old' way of doing things, and to date, it's given me no issues whatsoever.

Give it a try. Let us know what happens, please.

No I didn't try /mnt/home before using the /initrd/mnt/dev_save with DpupStretch but I've just tried replacing /initrd/mnt/dev_save with /mnt/home in the defaultbrowser script and it does work.

Regards,

Ken.

[keniv]

Savefile/folder in use > /mnt/home is a link to /initrd/mnt/dev_save (new Puppys seem to use only /initrd/mnt/dev_save)
No savefile/folder, pfix=copy/ram > puppy partition indicated as a drive like /mnt/sda3, no /mnt/home
No savefile/folder, pfix=nocopy > puppy partition is /initrd/mnt/dev_save, no /mnt/home (I've seen an exception with Tahr where it's /initrd/pup_ro2 in this scenario if I remember correctly!!!)

Just booted DpupStretch will pfix=ram so no savefile/folder. On clicking on sda1 get /mnt/sda1 and not /mnt/home as you say above (please see image). Quite confusing for someone like myself who is no expert and only knows enough to use puppy and sometime not even that, however, I have learned something today.

Regards,

Ken.

[mikewalsh]

Did you actually try it with /mnt/home before using the /initrd/mnt/dev_save $PATH? I'm betting if you modify it back to /mnt/home, it'll work just fine..... Despite them using this different 'label' nowadays, I still use the 'old' way of doing things, and to date, it's given me no issues whatsoever.

Give it a try. Let us know what happens, please.

No I didn't try /mnt/home before using the /initrd/mnt/dev_save with DpupStretch but I've just tried replacing /initrd/mnt/dev_save with /mnt/home in the defaultbrowser script and it does work.

Regards,

Ken.

Hah! Thought so....

Nice one. Well done!

Mike.

[Clif McIrvin]

Just found this thread -- still trying to run Rerwin's sulu-002; but it seems that I'm going to have to give up because of all the websites that won't support old browsers.

Anyway -- today had downloaded tharpup 6.0.6 and your 28.17.0 portable loads and fires just fine!

I'm on a Dell P4 2G RAM

(Didn't solve my banking issue -- next step is get on the phone w/ my bank - we'll see where that goes.)

Also tried to run it from sulu-002 .... nope.

[mikewalsh]

@Clif McIrvin :-

Mm. Lupu, eh? I didn't think anyone was still running it anymore, because browsers ARE the big issue with it now. And to MY way of thinking, an OS that can't get on-line is a bit useless these days...

Have you tried the glibc-'tweaked' version of this? I was using an older glibc-tweaked release of Pale Moon, running under Lupu, 18-24 months back, but I wouldn't like to say that this newest version will still do so. You can only try it. I can no longer do so, because the UEFI firmware in this new Pavilion tower turns its nose up at anything pre-Tahrpup; I've lost access to many of my old favourite Puppies!

Download available from here (direct link):-

https://drive.google.com/file/d/1UZomNh ... sp=sharing

Let us know what happens, please.

Mike.

[Clif McIrvin]

@mikewalsh
I've been running palemoon-27.6.1-p4-glibc219tweak.pet - that's what broke on my banking site.
28.17.0 gives me the same error message I get with 27.6.1.
I'll download your newer version and see what happens:

Code: Select all

# ./LAUNCH
XPCOMGlueLoad error for file /initrd/mnt/dev_save/sulu+/PaleMoon32+_glibc219-portable_legacy/palemoon32/libxul.so:
libxcb-shm.so.0: cannot open shared object file: No such file or directory
Couldn't load XPCOM.

rox tells me libxul.so is present in the specified location - I kind of expected that from what I'd recently read in the forum.

However - I tried your Iron 32 bit portable on thar 6.0.6 and my bank likes it!
I used to run Iron on lupu; but switched to PM back when 18 quit working.

Looks like I may be moving to tharpup -- that seems to be a good fit for my hardware. (Posting this from tharpup)
Thanks! for your efforts helping to keep 32 bit browsers going!

[mikewalsh]

Yah; banks are slowly getting more & more fussy with browsers. They're also steadily requiring multiple forms of ID & logging-in, too....

You do realise that current Iron isn't really related to the one you used to use, yes? That was almost a life-time away.....and a totally different code-base, too.

Tahrpup's a decent Puppy. It was the first one I used full-time when it was released in November 2014; it's pretty stable, although getting a wee bit long in the tooth now. I'm presently posting from its successor, a recently-installed 32-bit 'frugal' of Xenialpup 7.5.....and even that's only got around 4 months life left in it. Tahrpup is nearly 2 years past EOL already, yet plenty of folks still like it (even me, though newer software is becoming a bit of a pain to get running these days.)

I mostly run 64-bit Pups now, though I like to keep a couple of 32-bitzers around; partly for nostalgia, partly because I still think they run that little bit faster than 64-bitzers.....and partly because it makes it easier to put together 32-bit packages on the odd occasions when I still do so.

If Iron-portable does what you want, that's great. I produce both 32- and 64-bit packages when I build them; I'm a long-term Chrome user - since day one in 2008 in fact - and with Google having dropped 32-bit Chrome on Linux around 4 years ago, Iron is the closest equivalent to it that is still produced for 32-bit Linux.

And i still like my 32-bit Puppies.....

Mike.

[keniv]

@mikewalsh and@Clif McIrvin
Guess who likes Lucid 5287 and still has a version running on an old p3 Toshiba laptop. I had a copy of the iso for the 2017 version of lupusuper4 that I downloaded from Mainline Puppy Linux Distros>Legacy on this forum. I made a manual frugal install then tried Mikes PaleMoon32+_glibc219-portable_legacy but got the same output from running in a terminal as Clif. I the tried watchdog's post on the old forum http://www.murga-linux.com/puppy/viewto ... 93#1035893 and downloaded and installed palemoon-28.9.0.2-glibc219tweak.pet: but this did not work either. I thought this odd as I'd this running until recently and in fact it had updated over time to 28.16.0. I found I also had installed Lupu-palemoon-28.8.0-deps.pet. I still had a copy of this and installed it. I now have palemoon 28.9.0 running in running in lucid 5287 and I'm currently posting from it,however, it won't update to 28.16.0. Pity Mikes PaleMoon32+_glibc219-portable_legacy doesn't work. I can't be the only person that still likes Lucid5287 (perhaps I am). I am, however, still very grateful it works in Racy.

Regards,

Ken.

[Clif McIrvin]

I think I had some vague notion that the world was moving on and leaving me behind, yes.

Until I give up on this box and get a 64 bit machine I'll keep depending on guys like you that keep this old stuff alive.

Many moons ago I downloaded xenial 7.5 at Rerwin's suggestion, iirc. At the time it wouldn't even run ... many months later I stumbled onto the realization that the problem was my 512 MB RAM and not even a swap file. Creating a swap file resolved a lot of the PaleMoon crashes I was experiencing. Eventually I purchased some memory and beefed my box up to it's 2 GB max. When I tried xenial again I gave up because at the time I was unsuccessful at finding browsers that my bank liked. I suppose I must have done a better job of searching for solutions this time.

I'm trying tahrpup because of what I read at http://wikka.puppylinux.com/WhatPuppyLinuxIsBestForYou. So far, so good.

@keniv Hmm. I may try that deps pet and see what happens.

[mikewalsh]

I think I had some vague notion that the world was moving on and leaving me behind, yes.

Until I give up on this box and get a 64 bit machine I'll keep depending on guys like you that keep this old stuff alive.

Many moons ago I downloaded xenial 7.5 at Rerwin's suggestion, iirc. At the time it wouldn't even run ... many months later I stumbled onto the realization that the problem was my 512 MB RAM and not even a swap file. Creating a swap file resolved a lot of the PaleMoon crashes I was experiencing. Eventually I purchased some memory and beefed my box up to it's 2 GB max. When I tried xenial again I gave up because at the time I was unsuccessful at finding browsers that my bank liked. I suppose I must have done a better job of searching for solutions this time.

I'm trying tahrpup because of what I read at http://wikka.puppylinux.com/WhatPuppyLinuxIsBestForYou. So far, so good.

@keniv Hmm. I may try that deps pet and see what happens.

Ha. I guess I'm not really a typical Puppy user these days. I, too, have recently 'maxed-out' my own RAM - a little bit of 'future-proofing' - except in my case, you can add another 30GB on top of your own..... This HP Pavilion tower came with 4 GB, which immediately became 8GB. Increased that to 16GB in the summer, then upgraded all the way to 32GB shortly before Xmas.

I had to replace my old Compaq tower (which expired almost a year ago). Took it outside for its annual spring-clean, only it refused to ever start again after that. So I decided it was high time to invest in some new tech; up until then, I'd always used old clunkers.....though running Puppy, even old clunkers run pretty well.

You run Puppies on a brand-new machine, though, and you discover a totally NEW level of the "Whooah!!" factor. "Fast" takes on a completely different meaning, all of a sudden! And all that RAM, along with a 9th-Gen 'Coffee Lake' Pentium 'Gold' quad-core running at nearly 4 GHz, means I no longer need to worry about multi-tasking, and can do whatever I want, whenever I want....for as long as I want.

In complete contrast, I still have a 2002 Dell laptop, running a Pentium 4 with 1½ GB of DDR1. Runs Slacko 560 & radky's DPup 'Stretch', with which it copes admirably.....

Whatever we run, it's all about having a machine that allows you to do what YOU want with it. And Puppy lets you do that. I may well run brand-new hardware these days, but I'm still happy to help others keep their old 'clunkers' going.....

Mike.

[Clif McIrvin]

I now have palemoon 28.9.0 running in running in lucid 5287 and I'm currently posting from it

Ken - same here - I'm posting from 28.9.0 in sulu-002 (I've forgotten - but that must be lucid 5287).
This did resolve a functionality loss on dropbox.com; but my bank still doesn't like this.

So -- still poking about looking for what will work.

Thanks!

[keniv]

Your welcome Clif. 28.16.0 was the last 32bit official version of palemoon. I believe before 28.17.0 appeared 28.9.0 would have updated to 28.16.0 but palemoon seems to have removed the 32bit updates. It's a pity your bank doesn't play with 28.9.0. I thought there was a chance it would work with palemoon 28xxx rather than the 27xxx you were using.

Regards,

Ken.

[amethyst]

Your welcome Clif. 28.16.0 was the last 32bit official version of palemoon. I believe before 28.17.0 appeared 28.9.0 would have updated to 28.16.0 but palemoon seems to have removed the 32bit updates. It's a pity your bank doesn't play with 28.9.0. I thought there was a chance it would work with palemoon 28xxx rather than the 27xxx you were using.

Regards,

Ken.

Well, Palemoon is not publishing already compiled 32-bit versions anymore nor will you be able to receive updates from the official site but third parties do still compile the latest from source. So the latest Palemoon 32-bit version is still available. See the third post of this thread.

[keniv]

So the latest Palemoon 32-bit version is still available. See the third post of this thread.

I've had another look at Mike's post.

this is Steve Pusser's build of the current Pale Moon 28.17.0 release

Correct me if I'm wrong but is this not part of what Mike used to make the PaleMoon32+_glibc219-portable_legacy which works on some series 5 puppy's but not Lucid 5287. Do you mean that the updates for 28.9.0 ( the most up to date version we can get working in Lucid) that would take it to 28.16.0 are available as source code. Even if this was the case I don't have the skills to compile it for Lucid. I also doubt if 28.16.0 would work with Clif's bank if 28.9.0 doesn't but you never know.

Regards,

Ken.

[amethyst]

So the latest Palemoon 32-bit version is still available. See the third post of this thread.

I've had another look at Mike's post.

this is Steve Pusser's build of the current Pale Moon 28.17.0 release

Correct me if I'm wrong but is this not part of what Mike used to make the PaleMoon32+_glibc219-portable_legacy which works on some series 5 puppy's but not Lucid 5287. Do you mean that the updates for 28.9.0 ( the most up to date version we can get working in Lucid) that would take it to 28.16.0 are available as source code. Even if this was the case I don't have the skills to compile it for Lucid. I also doubt if 28.16.0 would work with Clif's bank if 28.9.0 doesn't but you never know.

Regards,

Ken.

I don't know what Mike did, you should ask him. All that I know is that the latest Palemoon should work for Precise 571 as is without any glibc upgrade. I'm using Palemoon 28.14.2 with Precise which I downloaded not too long ago.

[keniv]

@amethyst
Ah, your using Precise 571. I'm assuming from the number it's also a 5 series puppy. I have tried Precise in the past. I think it was a lite version but I no longer have it. However, I'm aware that we might have strayed off of the topic of Mikes thread "Pale Moon 'portables' - current release 28.17.0" so I think I'll leave it there.

Regards,

Ken.

[mikewalsh]

@keniv :-

I wouldn't worry too much about it. Thank you for thinking of it, but if you remember from the old Forum, thread 'evolution' often took subjects in strange & wonderful directions..!!

It's true, though, that when subjects get mixed in with each other, it does make them hard to follow, and for the multitude of would-be 'advisors' to make any real kind of sense of them. There was quite a heated discussion about this very point, in the early days after folks began to migrate over here from Murga-Linux.....

Mike.

[amethyst]

@amethyst
Ah, your using Precise 571. I'm assuming from the number it's also a 5 series puppy. I have tried Precise in the past. I think it was a lite version but I no longer have it. However, I'm aware that we might have strayed off of the topic of Mikes thread "Pale Moon 'portables' - current release 28.17.0" so I think I'll leave it there.

Regards,

Ken.

Yes, it's a series 5 Puppy. I must add that Palemoon seems to be the only new browser which works OOTB in the officially released Precise. To get other newest browsers working needs some upgrades to the operating system.

[MochiMoppel]

@mikewalsh and@Clif McIrvin
Guess who likes Lucid 5287 and still has a version running on an old p3 Toshiba laptop. I had a copy of the iso for the 2017 version of lupusuper4 that I downloaded from Mainline Puppy Linux Distros>Legacy on this forum. I made a manual frugal install then tried Mikes PaleMoon32+_glibc219-portable_legacy but got the same output from running in a terminal as Clif. I the tried watchdog's post on the old forum http://www.murga-linux.com/puppy/viewto ... 93#1035893 and downloaded and installed palemoon-28.9.0.2-glibc219tweak.pet: but this did not work either. I thought this odd as I'd this running until recently and in fact it had updated over time to 28.16.0. I found I also had installed Lupu-palemoon-28.8.0-deps.pet. I still had a copy of this and installed it. I now have palemoon 28.9.0 running in running in lucid 5287 and I'm currently posting from it,however, it won't update to 28.16.0. Pity Mikes PaleMoon32+_glibc219-portable_legacy doesn't work. I can't be the only person that still likes Lucid5287 (perhaps I am).

Thank you. I have an old Fujitsu laptop and like all Fujitsus it has some peculiar tastes. Works best with Lucid 5.2.8. I tried your recipe: palemoon-28.9.0.2-glibc219tweak.pet with Lupu-palemoon-28.8.0-deps.pet. Bingo! The tweak pet contains libxcb-shm.so.0 which Mike's portable complains about as missing, so I don't know if it would be worthwhile for Mike to update the portable. In any case it solved my problems.