if you have a frugal install, copy the missing seamonkey-bin file from /initrd/pup_ro2/usr/lib/mozilla/ to /usr/lib/mozilla/

if you have a full install, boot the Puppy cd maybe using the pfix=ram option, mount the partition, and copy the missing seamonkey-bin file from /usr/lib/mozilla/ to the mounted partition

there may be other missing files

Thanks, did the copy, will reboot.

Any idea why this would have happened?

You weren't kidding that there were other missing files!

I copied the entirety of /initrd/pup_ro2/usr/lib/mozilla/ TO /usr/lib/mozilla/
and Seamonkey seems to now be OK.

The HTML icon now returns the usual - open this under your browser
message, kind of a wasted icon.

gxine is still unresponsive.

How do I fix that, please?

And also, any idea what may have hiccupped to cause these significant
gaps in the upgrade process from 2.14 to 2.16?_________________Thanks! DavidHome page: http://nevils-station.comDon't googleSearch!http://duckduckgo.com
Puppy Carolina 1.3 & Lighthouse64-b602 & JL64-603

it depends what the problem with gxine is ... if it's missing or corrupted files, the files need to be replaced ... there may be missing or corrupted library files or configuration files

depending on the circumstances, an upgrade may not work properly

in your case, it sounds like you are having hardware problems, or maybe the cd did not burn properly, or maybe the iso file did not download properly

if the iso does not download properly, you would have a corrupted iso file, which would not be a Puppy iso at all ... it would be some sort of corrupted thing that might do anything to your system

i usually download isos with wget, which usually works well ... i always check the iso file's md5sum to be sure it is perfect ... i usually run Puppy as a frugal install, so i don't burn a cd, i just mount the iso file and copy the 4 files from it ... so to upgrade Puppy i might do something like this:

if you use a pup_save file (you seem to) you can look in /initrd/pup_rw ... corrupted and damaged and deleted files should be visible in there

there may be hidden .wh. whiteout files in pup_rw that are causing some files in pup_ro2 to be invisible and therefore "deleted" ... if there are .whw. files that should not be there, they could be deleted and the files in pup_ro2 (the pup_216.sfs file0 should be available again ... i have a script that deletes all .wh. whiteout files

I downloaded 2.16 today to try it out and didn't make it very far. It made it through the first few steps in the boot process on the CD and then it crashes telling me it can't find my CD or something to that effect. I don't remember the exact error but that's basically what it said. CD is good and checksum worked out fine. So for right now, I am halting on 2.16 and just gonna stick with 2.15.

And my 2 cents...
While I absolutely enjoy Puppy Linux, I just have not been impressed with the last 2 versions. While I can get 2.15 to work, it was not without a little bit of headache to make it work. I think the most trouble-free versions I have experienced so far is Puppy 2.13 and 2.14._________________The Official Myspace Puppy Linux Group

I downloaded 2.16 today to try it out and didn't make it very far. It made it through the first few steps in the boot process on the CD and then it crashes telling me it can't find my CD or something to that effect. I don't remember the exact error but that's basically what it said. CD is good and checksum worked out fine. So for right now, I am halting on 2.16 and just gonna stick with 2.15.

And my 2 cents...
While I absolutely enjoy Puppy Linux, I just have not been impressed with the last 2 versions. While I can get 2.15 to work, it was not without a little bit of headache to make it work. I think the most trouble-free versions I have experienced so far is Puppy 2.13 and 2.14.

I am guessing that the differences are partially hardware-specific because the
newer versions are accessing new hardware and are running more sophisticated
apps.

I have used most of the MS-like Linux distros with all of their code-bloat and
saw the same sort of occasional upgrade anomalies. The good thing about
Puppy is that the code is efficient and easier for the team to troubleshoot._________________Thanks! DavidHome page: http://nevils-station.comDon't googleSearch!http://duckduckgo.com
Puppy Carolina 1.3 & Lighthouse64-b602 & JL64-603

I am guessing that the differences are partially hardware-specific because the
newer versions are accessing new hardware and are running more sophisticated
apps.

I have used most of the MS-like Linux distros with all of their code-bloat and
saw the same sort of occasional upgrade anomalies. The good thing about
Puppy is that the code is efficient and easier for the team to troubleshoot.

I figure that newer hardware support might've been part of the reason, although I hope this doesn't mean that the quality of the support on old hardware is deteriorating. It almost seems it with the last 2 versions for me....of course maybe it's me, but then again, if I put a slightly newer version of Puppy on a machine that was already running Puppy, I expect to not really have any troubles. Now if I switched hardware around that'd be different. That is actually one of the main reasons I went with Puppy was b/c I had some old machines that I wanted to sort of revive with a nice lightweight Linux distro. I never was all that crazy for DSL, then when I found Puppy I was just amazed at how well it performed.

Manually entering a soundcard config isn't that big of a deal, but telling me it can't find my CD drive when it was reading from it 30 seconds earlier kinda is in my book. Never was able to get the system fully booted. Of course I never did try it in my old desktop, so not too sure if I will get the same result. The CD error was with my laptop. I dunno....I love Puppy Linux and it is one of the main distros I recommend to people looking for something lightweight...but these past 2 versions of the distro just have not liked me for some reason._________________The Official Myspace Puppy Linux Group

Well I managed to get it going on my laptop....sorry for the previous response, my patience was a little thin that day. I ended up using the ide=nodma option at boot time before I was able to get anywhere with the installation. I have never had to do that before in previous versions of puppy.

The only thing I have noticed now which this is a minor issue, is that my touchpad on my laptop partially works...I can move the mouse pointer around but when I touch it to highlight something nothing happens. I have to use the buttons to highlight or select anything._________________The Official Myspace Puppy Linux Group

Well I managed to get it going on my laptop....sorry for the previous response, my patience was a little thin that day. I ended up using the ide=nodma option at boot time before I was able to get anywhere with the installation. I have never had to do that before in previous versions of puppy.

The only thing I have noticed now which this is a minor issue, is that my touchpad on my laptop partially works...I can move the mouse pointer around but when I touch it to highlight something nothing happens. I have to use the buttons to highlight or select anything.

My 2.16 on my laptop was handling my USB mouse fine until I forgot it at home and had to use the pad.

Came home and powered up and now it refuses to recognize the USB mouse.

Very odd ... but then my 2.16 install hiccupped so I really need to do a reinstall from a clean CD._________________Thanks! DavidHome page: http://nevils-station.comDon't googleSearch!http://duckduckgo.com
Puppy Carolina 1.3 & Lighthouse64-b602 & JL64-603

i usually download isos with wget, which usually works well ... i always check the iso file's md5sum to be sure it is perfect ... i usually run Puppy as a frugal install, so i don't burn a cd, i just mount the iso file and copy the 4 files from it ... so to upgrade Puppy i might do something like this:

i usually download isos with wget, which usually works well ... i always check the iso file's md5sum to be sure it is perfect ... i usually run Puppy as a frugal install, so i don't burn a cd, i just mount the iso file and copy the 4 files from it ... so to upgrade Puppy i might do something like this:

Edoc, make sure that the file your trying to mount on the loopback device is not in Puppy's normal file system (/root or anywhere in your pup_save file). If it is copy it to a harddrive partition (/mnt/home) and try it there.

The only thing I have noticed now which this is a minor issue, is that my touchpad on my laptop partially works...I can move the mouse pointer around but when I touch it to highlight something nothing happens. I have to use the buttons to highlight or select anything.

That's a design "feature." Seems as though some folks don't have the patience to teach themselves to keep their cotton-picking thumbs off the touchpad when they're typing. So Barry disabled "tap." Sad, eh?

-aj_________________hangout: ##b0rked on irc.freenode.net
diversion:http://alienjeff.net - visit The Fringe
quote: "The foundation of authority is based upon the consent of the people." - Thomas Hooker

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