Porteus

With time, it seldoms happen that your save change folder will not become corrupted. For those familiar with that problem and who have been ingenuous to develop solutions, your tricks would be quite appreciated in this thread.

Do you have some basic save change folder with some standard or basic setup for your porteus os and your basic packages? Do you make copies of them so to have them handy as some kind of spare tire? Or do you go simply for some kind of cleanup in the save change folder? What folders within the save change folder will you delete to do such a cleanup?

Yeah..another chance to advertise my "never have Problems again solution"

When everything is installed/configured and working flawlessly I make an Image
of the partition or the whole usb-flash-drive.After doing so, i can install/deinstall
or experiment with the OS till everything is corrupt or broken.And If so,
just restore the Image and everything will be OK again.As a positive side-effect
you can do/learn more/faster about your OS/programs without the fear to damage
the OS and have to Install all the stuff again.
I'm doing so the last 15 years and I really don't know what could be easier or better 8)

Porteus has the possibility for a similar solution. I always create modules of my changes and leave them in the modules folder. When I am happy that things are stable I merge all the changes modules into a single module. Then I mostly use fresh mode and load the changes module. If I want to save some changes I just save the session as a module and continue in this way. I have NEVER experienced a problem of corruption that couldn't be fixed in seconds using this method.

At first glance, brokenman solution seems to be more handy and fast, and probably tailored specifically for the porteus os.

Thanks both of you for providing these solutions.

The last time I used the changes folder was in Slax-Remix!

I locate my changes in /mnt/live/memry/changes and move them to rootcopy first. After testing that everything is ok, I make a module MyXXsettings.xzm and put it together with the main module in a folder.

This never fails 8) ...and when an update of the Os comes, I move my setting unchanged (mostly!)

When porteus boots on my hdd installation, there is a lot of error messages before I get into the X environment. This is not the case in always fresh. As the messages follows one another, it is impossible for me to read them. Is there a way to dump them into a file for some eyeball analysis? Are these due to the fact that from one bootup to another I provide porteus with a different setting in terms of modules?

please boot to text mode with 'debug' cheatcode enabled and use shift+PgUp/PgDown to scroll the screen.
a photo of the errors would be welcome.

I know that I should have come back on this issue with you fanthom. And I will.

Meanwhile, I thought that the new cheatcode introduced with porteus 3.0, deserves some mention here:
http://forum.porteus.org/viewtopic.php?f=35&t=2953
http://forum.porteus.org/viewtopic.php? ... &start=105

Added 'changes-ro' cheatcode which keeps saved changes in a frozen state. This is handy if you have set your system 'how you like' and do not want to make other modifications to it.

Glad to have this one at hand. I finally always get corrupted my save changes folder.

I had it several times that my save.dat is corrupted.. so I could only use fresh mode.. normal did not boot anymore.

usually it gets corrupted when my system crashes. I have one Laptop that sometimes freezes when I plug in the power-cord for charging.. this oftenly wrecked my savefile.

I usually do a backup-copy once I set everything up and prefer to save downloads and documents outside the save.dat file system.

yet to test it in-depth in 3.0 and will check out your links above, cause this is probably what I need.

I use Porteus when I switch machines frequently (not happening too oftenly lately) and as portable system for emergencies (not too many of those lately) - the new 3.0 release didn't had much test-drive here till now, sorry.

Corruption is an issue, but it does not deters me to appreciate porteus os. changes-ro cheatcodes and the different tricks proposed by our smart guys in the above post, should help you be in less pain.

In addition, I imagine that you always have a copy of your sensitive data and general data out of your save.dat file. Do you? Most of my data is out of the computer on a usb key, or for bigger files on an external hdd (they are so cheap now). 8)

Save.dat files are tied to some limitation of the windows filesystem. Did you think about moving to linux filesystem?

fanthom wrote:please boot to text mode with 'debug' cheatcode enabled and use shift+PgUp/PgDown to scroll the screen.
a photo of the errors would be welcome.

It took some time but here it is:
http://www.mediafire.com/view/c92xck5xk ... _debut.jpg#

francois wrote:This post is still useful for me.

It's 18 months old!! You do know it doesn't cost any more to start a new thread.

Personally I backup my save changes from time to time thus if something happens to the live one I can restore it.

Good luck with your move.

Did you look at the output, that I left for fanthom? This is why I have tagged this post.

Contrarily to what you often write, I like old posts, especially when they still convey pertinent data. I really see no need to post anew. This way we build knowledge on which to reflect.

francois wrote:I left for fanthom? This is why I have tagged this post.

Actually I think you forgot. I see no FAA in the title.