I hope this is the correct place to post. I really like Puppy, but was having a big problem getting it to work on a specific laptop. I searched the Internet and did not find the work around. I did find many people with the same issue. Some experiments on the laptop found the solution. I hope this solution may help others.

Here is what I needed to do:
Run newer version of Puppy from LiveCD and save the SAVE SESSION file/folder on a small partition (separate from the OS partition) on the internal hard drive. This is a permanent arrangement. No need to go into the details why, it just is.

Specifics:
Puppy Linux, Tahrpup 6.0.2 CE, live cd disk
puppy partition: 5GB, formatted ext4
Laptop
brand: Dell
model: Latitude E6410/0667CC
ram: 4GB
CPU: intel i5 M560 @ 2.67GHz
SATA hard drive: 250GB, Windows 7 Professional installed
using Legacy boot in BIOS

Issue:
I could boot Puppy LiveCD the first time and create the SAVE SESSION file/folder. The second time I boot Puppy there is a kernel panic and a hard stop. Specific error text:
Loading the 'Puppy_tahr_6.0.sfs' main file ... coping to ram
Preforming a 'switch_root' to the layered filesystem...Kernel panic - not syncing: Attempting to kill init! Exit code-0x00000100
Then a core dump to the screen.
If Puppy booted with ‘PFIX=RAM PMEDIA=CD’ no issue. But it is slow that way and I could not load saved settings.

Solution:
I will avoid listing all the things I tried or how I discovered this solution. Let just get right to what worked. The first time you save the setting, Puppy walks you though a script to save settings. Tahrpup stores the saved settings in a folder - excellent idea. The script then offers to copy the file system (ei: puppy_tahr_6.0.sfs). But it goes to the root of the partition, not the folder. On next boot, you get the kernel panic and hard stop. Here is the fix. Boot Puppy with ‘PFIX=RAM PMEDIA=CD’ so the file is not in use. Move Puppy_tahr_6.0.sfs into the save setting folder. Restart. After two restarts the system is optimized and boots supper fast without any errors.

Not sure if this will fix the issue on other hardware. I hope this helps some others.

I found the solution. In my first experiments I used the SAVE FOLDER option and put it at the partition root of an EXT4 partition. The next boot caused the kernel panic. In later experiments, I made a folder in the EXT4 partition. Then used the SAVE FOLDER option and put it into the folder I created. This solved the issue. So it was user error not understanding a folder had to be created to use this option.

Moved: This thread is more suitable in <Puppy> and has been moved accordingly to help your thread/question get the exposure it deserves.

Thank you.