PupsaveConfig-2.2.5

[shinobar]

It seems heavy encryption does not work - I haven't tested light encryption yet.
It gives an error about an incorrect password when creating the save file. Both the GUI and Legacy scripts are broken.

Humm... I will test.
EDIT: confirmed(on fluppy-010). I will check it up.

Also it shouldn't let you create an encrypted save file with any filesystem execept ext2 - journaling apparently causes a problem with the encryption.

Don't worry. If the user select ext3/4 and encryption, forced ext2.

[shinobar]

Updated to pupsaveconfig-1.9.5. See the top post.

• Bugfix: was failed encrypted save file.
• Messages correction thanks to don.

@don
I keep 'no encryption', 'light encrypted' and 'heavy encrypted' because they are the same as the original dialog.

[jemimah]

Thanks!

[shinobar]

Updated pupsaveconfig-1.9.6.pet available at the top post.

• Fixed was getting improper shutdown message when you choose not to save session at shutdown for frugal install on flash. (Thanks to einar reporting the issue)
• Fixed was sfs file copied at the top directory.
• Pot file updated.

[einar]

Updated pupsaveconfig-1.9.6.pet available at the top post.

• Fixed was getting improper shutdown message when you choose not to save session at shutdown for frugal install on flash. (Thanks to einar reporting the issue)
• Fixed was sfs file copied at the top directory.
• Pot file updated.

thanks for helpin out / awesome app i will try this today / tomorrow

[tlchost]

Updated pupsaveconfig-1.9.6.pet available at the top post.

Downloaded 3 times....package manager in Quirky1.2 says it is installed....but not in menu. The .desktop file has no contents.

Thom

[shinobar]

Updated pupsaveconfig-1.9.6.pet available at the top post.

Downloaded 3 times....package manager in Quirky1.2 says it is installed....but not in menu. The .desktop file has no contents.

Something wrong in download.　Download and check the file size.
The menu should appear at Menu>System> PupsaveConfig.
I have checked on Quirky-1.2.

[tlchost]

Something wrong in download.　Download and check the file size.
The menu should appear at Menu>System> PupsaveConfig.
I have checked on Quirky-1.2.

Tried again...After I rebooted the system, it showed up...thanks.

Thom

Could you investigate being able to save to a different file name than the one that was loaded at the start?

Thom

[don570]

Note to Shinobar : a minus sign is put in front of a number i.e. -5
I think the word you should use is 'hyphen' which is a punctuation mark
to separate two words.

I've suggested some changes in red ink
http://www.datafilehost.com/download-57d7f570.html

________________________________________________

[shinobar]

Updated pupsaveconfig-1.9.7.pet available at the top post.

• Fix finding system files installed
• Fix was failed to eject CDs(rc.shutdown)
• Update messages thanks to don570, update help file, update .pot file

[tlchost]

Updated pupsaveconfig-1.9.7.pet available at the top post.

Check your upload...No pet file.

Thom

[shinobar]

Updated pupsaveconfig-1.9.7.pet available at the top post.

Check your upload...No pet file.

Thanks, Thom. Now have uploaded the pet.

[tlchost]

Thanks, Thom. Now have uploaded the pet.

Thanks....downloaded and installed.

I noticed something in Quirky1.2 It seems that I have to uninstall 196, reboot and then install 197. Not sure if that's normal, a Quirky12 quirk, or my USB bootable.

Regardless, it's a valuable addition and I have suggested that BigMike`` include it in the next version of ThinkLinux.

As an aside...I have read that one should not attempt to copy a save file in use to another one with a different file name. Is there a way to do that?

Thanks,
Thom

[jemimah]

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.

[lee321987]

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?

[shinobar]

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.

[don570]

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

________________________________________________

[shinobar]

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.

[don570]

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

_________________________________________________

[jemimah]

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.