First, thank you very much for the advice.
[quote="gcmartin"]
this was created as a multi-session media when burning the ISO.
[/quote="gcmartin"]
The problem I see with multi-session rw disc is that anyone can write to it, or call a script at shutdown to "add something" to the disc or savefile. That's why my goal was to create an "uncorruptible" save which I could revert to the moment problems arise and start from scratch again. I don't want to marry the os, I just want to use it as a tool and then wipe it off and put it away. My initial thinking was to simply boot that savefile one time, then back it up to other media (cdr), as the successful bootup would be proof of (at least) initial usability. But since it would not load that save, I am stuck with a hesitant "redo".
[quote="gcmartin"]
Tailored couple of apps for the owner[/quote="gcmartin"]
One thing I did not mention before was that the goal is to implement some newish Linux version with compatibility with my HW to create a highly mobile and "foolproof" usb or mini cd based desktop environment that will load a specific set of progs/data and have the ability to save on the fly. I am still very much in study mode, but that is the end goal.
Said another way, I simply want to get ONE stable linux os setup and working the way I want it to then KEEP it that way to MAXIMIZE productivity and stop chasing my tail. Caveat, I tend to enjoy tail/goose chasing from time to time. The other goal is to learn to dev, so that I can create/tinker with some apps I think will be very useful in my line of work.
[quote="gcmartin"]
[*]Created a 4GB SWAP (to match RAM size) partition [/quote="gcmartin"]
So the swap should match the available ram? OK,
when I get back on that project I will check it out. I do have a dedicated linux swap on the HD but am not sure of the size at
the moment.
[quote="gcmartin"]
[*]And showed them how to save the work (session) back to the LIve media by answering correctly ("Save to CD") at shutdown/reboot.[/quote="gcmartin"]
Don't you just love it when a plan comes together?
But my save was on a USB. I followed the advice to heavily encrypt in the pupsave dialog box, but something went awry somewhere... Looking at the TRACE data, I suspect something to do with this version and ACPI not seeing bit to bit, but that is just a guess. I tried earlier Wary versions with and without ACPI and always had problems no matter what. Now that I think of it, this sounds like a classic faulty ram scenario, hmmm. I will be taking it to be serviced soon as the W7 (forgive my weakness o Lord) that came on the pc has been corrupted beyond recognition. And, as I question its "genuine-osity", I do hope to resolve the problems with puppy sufficiently so as to be able to bid a final and total farewell salute to all MS bloatware.
[quote="gcmartin"]
* I would strongly encourage you to delete the "Save session" you have, currently, on your hard drive. (Puppies are very particular about what they find on your HDDs/USBs at boot time.)[/quote="gcmartin"]
Are they? I've had and still have several differing versions of puppy savefiles all in the same partition and have been booting from cd with nary a savefile related issue before. Also, all of those saves are over the suggested size limit (1.8/2gb???).
Your reasoning? If it saved the save file ok, then during the load/init it obviously bypassed that point ok, why should the savefile be corrupt? I still think it is something else HW, FS, or procedural related. Keep in mind it is an el cheapo laptop with delusions of grandeur (imo). On an aside, the bios was also recently "corrupted" by the simple fact that I had both a system pwd and a user pwd set up at the same time (I was tired). Presto chango and one reboot later, every usable option in the bios was grayed out. I searched literally for two weeks for any clues as to why, with no success and heaps of outdated info none of which shed any light on a possible solution. When I say grayed out I mean it, the F9, Load optimized defaults was also incapacitated. As I could not reset defaults and could not flash the bios (due to it having the latest one already and the flash util would not allow a retrograde) I was temporarily stymied. Finally, I put the brakes on my racing brain, took a deep breath, let it out, and voila, there was the answer in the winflash app error msg (hint: dates can be changed with a simple hex edit). One quick edit and voila, new, usable bios (there's a peculiar fact about that event which may be interesting to some, but as this "saga-like" post has probably already stepped on a few toes, I'll digress.
[quote="gcmartin"]
This
may work flawlessly for you as well. [/quote="gcmartin"]
I can dream can't I? Thanks so much for the tips. I'll give it a shot this weekend when time should be my own again. One final thought-how's the hybrid graphics working on that system there? Any tips on step-by-step setup so I can disable the Intel onboard that you could PM to me? Pretty please!