(old)Puppy Linux Discussion Forum

Posted: **Sat 01 Jan 2011, 04:37**

lee321987 wrote:In top post you say, "Install on any Puppy-4.x/5.x running with RAM only mode". Does that mean that if I don't "copy to ram" at boot-up that I can't use this?

You can install the pupsaveconfig on your current Puppy.
RAM only mode is needed for precise test.

Posted: **Tue 04 Jan 2011, 23:29**

I tested pupsaveconfig in wary-500j02.iso
and it worked well . I tried no encryption and light encrytion and 'Legacy'.
They all worked as expected.

There was one odd bug. I filled in the details in the opening screen
then clicked button. I then chose American English.
The screen went entirely black. I clicked on it. and it came back
with the trial keyboard.

That's odd . I've never had pupsaveconfig do that before.
It wasn't an accident since it has happened about 5 times now.

______________________________________________

I spotted a couple of errors with the wording in this version.

For instance,

You copy a file to a hard drive.
You put a file on a hard drive.
The preposition is important.
Here's some screenshots with red ink corrections

http://www.datafilehost.com/download-54ba3caf.html

________________________________________________

Posted: **Wed 05 Jan 2011, 00:19**

don570 wrote:There was one odd bug. I filled in the details in the opening screen
then clicked button. I then chose American English.
The screen went entirely black. I clicked on it. and it came back
with the trial keyboard.

It is not the issue of the pupsaveconfig but of the firstrun(Country Settings).
When you change the timezone, the screen once goes black and comes back after a while. I don't know why but It may occur with Puppy-4.x and Wary.
EDIT: not right. It can be Wary only. The Puplite, based on Puppy-4.2, doesn't occur. Fluppy-010 also doesn't...

I may need to put some notice in the firstrun...

Thanks the correction, don.

Posted: **Wed 05 Jan 2011, 00:40**

Yes. I made a mistake. I should have called the app 'FIrstRun'
when I got the strange blackscreen.

_________________________________________________

Posted: **Wed 05 Jan 2011, 03:33**

shinobar wrote:
don570 wrote:There was one odd bug. I filled in the details in the opening screen
then clicked button. I then chose American English.
The screen went entirely black. I clicked on it. and it came back
with the trial keyboard.
It is not the issue of the pupsaveconfig but of the firstrun(Country Settings).
When you change the timezone, the screen once goes black and comes back after a while. I don't know why but It may occur with Puppy-4.x and Wary.
EDIT: not right. It can be Wary only. The Puplite, based on Puppy-4.2, doesn't occur. Fluppy-010 also doesn't...
I may need to put some notice in the firstrun...

Thanks the correction, don.

Running xrandr causes this behavior. Mostly with Xorg 7.3. Newer versions of xorg don't have this problem as bad.

Posted: **Wed 05 Jan 2011, 03:41**

I have a slight problem on my machine with two monitors. Firstrun crashes before it gets to the part where it disables itself. Causing it to run at every boot.

Code: Select all

+ for W in '$(echo "$XRESOELINES"| grep "^ $NEWDIM")'
+ '[' 1680x1050 = '' ']'
++ echo 1680x1050
++ cut -d. -f1
+ N=1680x1050
./firstrun: line 578: 1680x1050: value too great for base (error token is "1680x1050")
./firstrun: line 579: 16965 Terminated              gtkdialog3 -p DIALOG -c >/dev/null

Edit: oops I just noticed this is the wrong thread for this. Sorry.

Posted: **Thu 06 Jan 2011, 23:28**

Dutch translation for PupSaveConfig

Posted: **Sun 16 Jan 2011, 15:15**

MultisessionFlash

I'd like to have an option to have file changes stored on the hard disk, not in RAM.
And then, upon shutdown (and using the SAVE button),
save the changes to USB flash memory in a manner similar to multi-session DVD.
Furthermore, a utility to combine all the session saves into a single file,
and to recover file changes in the event of a system crash.

If a swap file or partition is used then storing file changes on hard disk is virtual.
But if system crashes it would be nice to have file changes on hard disk for recovery.

I run LUPU511 from USB flash memory stick with lupusave on the stick.
I turned off the periodic save; save on shutdown is good enough.
I have a swap file on the hard disk.

Posted: **Fri 21 Jan 2011, 13:30**

Update pupsaveconfig-1.9.8.pet (21 Jan 2011).

ext3 as the default, notebook
messages correction thanks to don570,
precaution: remove pupsave.conf at shutdown(rc.shutdown)
fix again avoid invalid shutdown when no save to flash(rc.shutdown)
includes NLS, German(L18L), Japanese(shinobar), Dutch(Bert) and Russian(rodin.s).

Posted: **Sat 05 Feb 2011, 19:34**

I checked pupsaveconfig in Wary 06 Multilingual.
The German version had a couple of spelling errors.

As well , the word 'Minus' is used instead of 'hyphen'
which is properly translated 'der Bindestrich'

________________________________________

Posted: **Sun 06 Feb 2011, 07:52**

don570 wrote:I checked pupsaveconfig in Wary 06 Multilingual.
The German version had a couple of spelling errors.

Thanks, don.

Updated: PupsaveConfig-1.9.9
# v1.9.9d 6feb11: rfkill, performance.sh, remove /mnt/*mnt/+..(rc.shutdown), message on progressbar, sort the probepart
/etc/rc.d/rc.shutdown at line 70-

Code: Select all

# 5feb11: some stuff for fluppy
which rfkill &>/dev/null && rfkill unblock all
[ -x  /etc/acpi/performance.sh ] && /etc/acpi/performance.sh

Posted: **Sat 12 Feb 2011, 04:57**

The first time I run it, it doesn't probe all the devices. The only saving option is the boot media. It will probe the devices if I click the back button though.

Is this a bug or a feature? It seems confusing.

Posted: **Sat 12 Feb 2011, 05:31**

jemimah wrote:The first time I run it, it doesn't probe all the devices. The only saving option is the boot media. It will probe the devices if I click the back button though.

Is this a bug or a feature? It seems confusing.

It is intended. The pupsave at the same place of the boot medium is recommended i think.
For whom want to save on another media, I left the message on the back button.
If you boot from CD, all the devices are scanned from the first time.

This feature was old standard of Puppy. But it is recently modified. Wary-500 lists up all the devices.
It maybe convenient for someone, but can be confusing for the beginners, i suppose.

One example: I make frugal install on sda2, the Windows 7 system partition.
The Wary-500 lists up all the partition and the sda1 as the default, but the sda1 is a small 100MB partition for the boot stuff of Windows 7.

Posted: **Mon 14 Feb 2011, 16:46**

pupsaveconfig-1.9.9 (on p412, PULP 3 puplet - bootdisc+savefile on usb stick)

Firstly a few details/opinions
1) on the drives-selection page, dividers or separators might be helpful - the paired lines need to be obviously paired

2) on the folder/file-name page - folder-name should work on any pup that can 'look' beyond the base dir, possibly leave it blank but a pre-done 'hint' is ok too

3) a tabbed interface might be overlooked, but it does get away from the sequential tyranny. A choice of the smallest 32 mb would help if things are tight on a usb stick (or for testing). Not sure, but I think with a usb save the main sfs from the CD was automatically copied on 1st run.

4) At the actual save/reboot/poweroff, perhaps the wording on the "save" button could be changed to 'hold' or 'redo', I can see someone going "Sure, save my session" and getting confused with another config run.

..and next-to-finally it does not seem to have solved my particular issue (this topic) in regard to making it to a successful 2nd boot with a bootdisc/savefile on usb combo (but I finally remembered the "puppy ..." startcode

).

5) the 60 second timer seems a good idea (progress bar a nice touch) on the save/nosave dialogue and a default nosave even better for when things might go fairly wrong, but it still needs set to zero in that eventmanager tab if one prefers no periodic saves (easy enough to remember to do manually and that could be considered a user preference, learning experience or further development)

Good utility, shinobar and thanks - I may need to add your optical drive tweak to pulp as well (ack, tray opens/closes too quickly sometimes in certain situations - not good to force-hold the mechanism open

).

small detail

pupsaveconfig-1.9.9.pet didn't update the /usr/share/doc/index.html in the 'available in menu' and 'packages contained in' fieldboxes, indeed the remnant in / was a rather generic-named "pet.specs" file

, dunno if it makes any difference after it's in, but I renamed it to full name anyway (the .packages and rootmenu items are fine)
---addenda to the last-mentioned immediately ^ above---
It does update the relevant pages after a reboot and clears the remnant in / like a well-trained pet should

Posted: **Fri 06 May 2011, 10:23**

1. This was the method I was using previously.
Notice that I edited the ISO file used to burn the CD, such that it treats a lupusave on an internal HDD as though it is a lupusave on a Flash Drive.

2. I decided to begin anew to make a lupusave [for Lupu-525] on a partition on an internal HDD.
This gave the opportunity to use Pupsaveconfig-1.9.9 to make the new lupusave.

3. It was proving difficult to use at 1st, but after a few attempts it "just worked".
Don't know what I was doing wrong.
Now working well as follows:
[With a lupusave on an internal HDD]
(a) Doesn't auto-save during the session, but I can choose to save manually at any handy point in time.
(b) Offers the opportunity "to save or not to save" at shut-down or reboot.

NEEDED
4.
(a) I'd like to be able to make "No save..." the default, with a configurable timeout period [5 seconds?]

(b) I'd like to be able to configure that the CD is not ejected at power-off.

5. Thank you SO MUCH for this program; I LOVE that Puppy has the ability to do this.

Posted: **Fri 06 May 2011, 12:21**

jemimah wrote:One thing I always add to the shutdown script is "rfkill unblock all". Most puppies have rfkill support disabled so it doesn't matter for them. But Fluppy and I think some of Iguleder's, and Pemasu's puplets have it enabled.

The problem is if you shutdown with RF blocked, it actually disables the NIC in the BIOS. If the next OS you boot isn't RF-switch aware, the networking hardware on some machines will not be properly detected during boot.

Shinobar, this post by Jemimah is most important to me. If you have applied it then apology my lack of attention to details but I fail to see any response to it and I use Pemasu's Snow puppy and that one uses RFKILL and so on. So this is a must have for us who do Snow puppy

Posted: **Sat 20 Aug 2011, 20:15**

Hi Shino,

As you were not much around anymore, because of the disaster ?, I did not post earlier.

It seems that when I tell 1.9.9d "not to save" it still saves.

E.g. in Lupu 5.2.8 SqueezeX3 ec., while it works properly in 540

http://smokey01.com/stu90/

Any idea how I could solve this ? something something /etc/rc.x /xxx ?

Posted: **Fri 09 Sep 2011, 14:51**

HI FOLKS !
Experienced the same problems like nancy reagen.
Tried a lot of advices with no real success.
This whole topic causes me a lot of headaches.
It realy drives me crazy.
Will i ever find a simple method of "shutdown (to USB) without save" ?

Cheers

Posted: **Fri 09 Sep 2011, 21:29**

backi wrote:HI FOLKS !
Experienced the same problems like nancy reagen.
Tried a lot of advices with no real success.
This whole topic causes me a lot of headaches.
It realy drives me crazy.
Will i ever find a simple method of "shutdown (to USB) without save" ?

Cheers

Though haven't tried yet but thought read today Exprimo cares for this (at your request ?)

Posted: **Sat 10 Sep 2011, 08:38**

Hi Folks !
Shut down with no saving.
Used this script in dpupexprimo and Three Headed Dog :

#!/bin/sh
# skips rc.shutdown and powers off computer without saving the session.
Xdialog --title "script $0" --yesno "\n\nAre you sure to power-off computer WITHOUT saving?\n\n" 0 0
[ $? -eq 0 ] && rm /initrd/pup_ro1/etc/.XLOADED && rm /etc/.XLOADED
exec /bin/busybox poweroff

In DpupExprimo you find it here:

" /root/my-applications/bin/nosaveshutdown script has been included since the Exprimo you first time posted about your need. It works as it works. "

Does work so far Shutdown without save, but not in every case.
Try to explain what i experienced.

For example: installed Iron-13 pet >shutdown with no save option (fast shutdown)
after restart- bootup this programm-browser still there (despite shutting down with no save)
For example installed an opera deb >shutdown with no save option (fast shutdown)
after restart- bootup this programm-browser still there (despite shutting down with no save)
(this programms don't appear as installed in PPM- if this may give some information)

Then did a test installing an hpprinter driver pet (indicated as installed in PPM) or made changes remove builtin packages then
>shutdown with no save option (fast shutdown)
after restart- bootup this installation-changes are not saved

Another example: making a text file saving it as dokument
>shutdown with no save option (fast shutdown)
after restart- bootup this saving is gone.

My thinking is i am running in ram and >shutdown with no save option (fast shutdown) will eliminate all changes during session.

Why these above mentioned pets and debs (there are others too) surpass
>shutdown with no save option (fast shutdown) ?
how do the manage to go to my USB despite>shutdown with no save option (fast shutdown) and other pets or debs don't ?

Quite curious.
Somehow these above mentioned pets and debs and others too ,manage to go to my USB stick despite >shutdown with no save option
Some others don't.

I'ḿ quite confused.

(old)Puppy Linux Discussion Forum

PupsaveConfig-2.2.5

Re: "running with RAM only mode"?

test in wary5 japanese version

Re: test in wary5 japanese version

mistake

Re: test in wary5 japanese version

pupsaveconfig-1.9.8

german version

PupsaveConfig-1.9.9

probing device

saves, while telling -not to

Exprimo ?