I thought that the savefile could sort of fix itself? I'm told that one can mount an unbootable ("corrupt") savefile while running from RAM, copy over everything that needs saving, and then unmount/overwrite the old (broken) savefile with a new one that works, without losing a thing.

...or am I mistaken?

All depends on what the problem is.
If you crash it the way goingnuts did, you're lucky if anything's left.

- goingnuts:I am tinkering with the xorg pet on different machines and tried manually grafting it into the filesystem (no real success yet) and have a couple of questions:
1) When I use the pupngo pet installer the xorg pet works properly, even though the X11 folder within the pet is labelled x11r7 (lower case). However, after the installer does it's work the files are in the X11R7 folder. How does this happen? I see no pinstall file to guide it?
2) After the installer has run, the libs from the pet are in their expected places, but there are also symlinks ponting to the new libs. How did those symlinks get there? How does "it" know how to name those symlinks correctly? Again I see no pinstall file to guide things. I do see a petspecs file but it does not give me any clues.
??

I'm not sure what I am doing wrong. In order to extract the pet files I am changing the suffix to tar.gz and clicking on it, and I can see all of the symlinks listed there in the archiver, but when I extract the files none of the symlinks get extracted. I notice a | in front of the permissions list for each of the symlinks, but all the other files just have a -
Seems as if i am needing to change my system permissions somehow in order to be permitted to extract those symlinks?? or maybe use a cli command and some special arg to extract all??

EDIT: google tells me the first letter | is actually an "ell" and means the file type is "link", so not significant in terms of my problem I guess.

EDIT again: Turns out I needed to do the extraction within the /root folder. Not on another partition. Not sure why. All good now.

I am still uncertain if the "pink"-screen on some reported hardware is due to pupngo Xvesa or Xvesa in general. I have cut out a Xvesa from micropuppy which could be an option to test. Also included the programs xcompmgr and transset witch works with the micromuppy Xvesa and gives window-shadows, fade-in/out and transparent windows - view attached image. Its quite cool actually - wonder which Xvesa version is used and how it was configured...Download Xvesa_micromuppy.

I am still uncertain if the "pink"-screen on some reported hardware is due to pupngo Xvesa or Xvesa in general. I have cut out a Xvesa from micropuppy which could be an option to test. Also included the programs xcompmgr and transset witch works with the micromuppy Xvesa and gives window-shadows, fade-in/out and transparent windows - view attached image. Its quite cool actually - wonder which Xvesa version is used and how it was configured...Download Xvesa_micromuppy.

It is an error in Xvesa and I did stumble on a patch for it once but I was on my droid and haven't come across it again, but I bet it is in dix (btw dix stands for display/driver independent X and ddx is display/driver dependent X) ... IIRC it was something in RBG instead of RGB or something like that for some of the lower res display modes_________________Web Programming - Pet Packaging 100 & 101

EDITI have now added a version of pupngo2012 with xorg and Freeoffice installed. Out of the pupngo spirit really because its pretty big, but hey, it lets me do all my typing/pdf creation on a pupngo install and runs like lightning so why not?

New build uploaded with fix for severe bug found by Jan99: Cryptosave was not working as I have used losetup from util-linux-2.11z which does not support -f switch. Unfortunately this is placed in initrd so only fix has been to ship a new iso.

This works in pupngo for a heavy encrypted savefile.
Please note that in pupngo losetup is same as losetup-FULL - in other Puppy versions losetup is a symlink to busybox and losetup-FULL is ...the full losetup. The busybox version is present but you need to call it by "busybox losetup"...

live-cd running now, tried playing an mp3 song :
minimp3 /mnt/data/Small-mem-card/Music/Can I go now.mp3
Error: cannot open `/mnt/data/Small-mem-card/Music/Can'!
file name with spaces gives an error (truncated), there was a small puppy tool for this situation ' -_' (space,hyphen,underline)
minimp3 /mnt/data/Small-mem-card/Music/'Can I go now.mp3' #file name quoted
song played
xhippo can handle file names with spaces.

beaver doesn't like ctrl+c/ctrl+v method, ctrl+v closes previous opened window
.. could this be a jwm shortcut problem ?
high-lighting and mouse middle click paste method works between rxvt/beaver/beaver/rxvt
not between beaver/dillo save file then open in dillo. a bit complicated

@ starhawk my acer 508t also has a magicGraph128XD 2MB card (aka neomagic)
googled it : very poor results with Xvesa (nil), slightly better with Xfbdev, better with fb and best with Xorg
needs some $magic to get it working under Xvesa with linux, tried but never completly implemented.
searched the forum with keyword Xfbdev : 29 results, interesting reading (blacklisted with Xvesa /funny colors)

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