Moderator: Forum moderators
Hi, I have an install that used to be on a flash drive. so i used pupmode 13. Now i moved it to a hard drive and i want changes to go directly onto my pupsave folder instead of being in ram until i shutdown or sync files. Can I change to a different pupmode to do that?
cheers
Direct writes to a media does pupmode 12.
To be honest, I very appreciate pupmode 13 (save changes only on demand). If something goes wrong, I can simply escape by rebooting without saving. I boot from hard drive and use pupmode 13 on it without a problem. With pupmode 13 you also can set a save interval to a shorter time in puppy event manager if you want.
Anyway if you really require direct writes you need to edit the boot parameter "pmedia" on the kernel line in bootloader´s config file (menu.lst or grub.cfg or syslinux.conf):
on usb flash drive with pupmode 13 there was probably: pmedia=usbflash
and now for direct writes to a hard drive you need to change it to: pmedia=atahd
Ditto what Feek wrote, especially about NOT changing from pupmode 13. You'll regret that you traded a couple seconds shut-down delay the first time you have to spend hours unscrambling a problem that was automatically written to your SaveFile or SaveFolder; Or having surfed the Web you are now automatically Saving malware you didn't know you had picked up.
As Feek wrote, you can shorten the time before the shut-down process begins. Menu>System>Puppy Event Manager, click the Save Sessions Tab, edit the Save Sessions Interval. But you really don't have to do anything.
During shut-down a GUI appears with two buttons. The one named Save is highlighted so that you can quickly press the Enter/Return Key to generate a Save. You may have assumed that you have to change focus to the 'NO SAVE' button and click it to shut-down without Saving. But the default routine is 'no save'. You can just walk away and after the time interval set in Save Sessions your computer will shutdown or reboot without executing a Save.
i save ALL of my forum PUP-DOG sessions in a folder on the PC's system drive. For performance and integrity reasons, NEVER on a USB stick.
I have an ext4 partition that has folder on it "Sessions" where all persistence from each and every PUP/DOG is kept. This makes for easy understanding and for good housekeeping.
For example on one of my PC, a pristine boot of any new PUP is ALWAYS started on the 'linux' line adding PUPPY's PSAVE parameter: It looks like this:
linux /vmlinuz ... psave=sda4:/Sessions/
This parm does 2 important functions if you are using any modern WoofCE based PUP; namely
directs the pristine WHERE to save the persistence.
allow @gyrog's WoofCE INIT modules to create a 'persistence' identifier file such that the need to specify psave is not needed upon reboots. It creates the SAVESPEC file.
The SAVESPEC for the above PC looks like this:
Code: Select all
SS_ID='Linux'
SS_DIR='/Sessions'
SS_MEDIA='atahd'So if I want to find what was done in any particular PUP/DOG, I look in the "Sessions" folder for the PUP's persistence.
Hope this is helpful understanding
Thanks everyone for the advice! I definitely do appreciate pupmode 13, have been using it happily for over a year now. but my laptop is a little weird sometimes, and i have had it hard-crash sometimes when i accidentally overdraw too much power on the USB ports. Usually when I'm trying out little hardware experiments with arduinos with too many things plugged into them 
. If it's that easy to change modes though I might just set it to 12 whenever I think I might start crashing my computer so I don't lose my progress. Or i could remember better to save it outside the pupsave I guess
oh ALSO about the save interval. I used to use that, but I kept getting logged out of some websites when I did. I guess browsers do not like it when you remount their storage while they are running, because discord and a bunch of other things that used localStorage (or maybe the database feature idk which) would lose all their state any time a pupsave happened while they were running. So I have to close down any browsers and electron apps before pupsaving to avoid it
I don't know why but I don't get a button to choose whether to save when I shut down. It just always saves without asking. Maybe I changed something and forgot
I don't get a button to choose whether to save when I shut down. It just always saves without asking.
If you are running in pupmode 13.
Puppy Event Manager -> Save Session
There is a selection to check if you want to be asked to save at shutdown.
If not checked it will auto save.
Note:
Selection may not take affect until you reboot.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected 
Now i moved it to a hard drive and i want changes to go directly onto my pupsave folder instead of being in ram until i shutdown or sync files. Can I change to a different pupmode to do that?
As far as I can tell, you are now running with the pmedia=atahd option, as Feek advised.
Which causes Puppy to write directly to your save folder.
Which is exactly what you asked for.
In this mode, there are no icons to save the changes in ram to the save folder.
Because in this mode (run mode 12) any changes to the file system (configurations, installing a package, etc)
are written immediately to the hard drive.
Which is what you asked for.
williams2 wrote: Fri May 13, 2022 6:14 pmNow i moved it to a hard drive and i want changes to go directly onto my pupsave folder instead of being in ram until i shutdown or sync files. Can I change to a different pupmode to do that?
As far as I can tell, you are now running with the
pmedia=atahdoption, as Feek advised.
Which causes Puppy to write directly to your save folder.
Which is exactly what you asked for.In this mode, there are no icons to save the changes in ram to the save folder.
Because in this mode (run mode 12) any changes to the file system (configurations, installing a package, etc)
are written immediately to the hard drive.
Which is what you asked for.
Yes. Pupmode 13 is automatically run from a USB-Key. The default when you locate Puppy on a hard-drive is Pupmode 12. You want to be using Pupmode13, especially during experiments as you don't want to accidentally make mistakes permanent by Saving them. And most importantly, if you have a system crash while a Save is taking place your SaveFile/Folder may be corrupted.
To switch to Pupmode 13 when booting from a hard-drive is a 3-step process.
(1) First you have to 'fool' Puppy into thinking its being booted from a USB-Key. To do that edit the boot menu/grub.cfg file. Look for the pmedia= argument. If it does NOT read pmedia=ataflash change it to that. If there is no pmedia= argument, insert one into the line beginning with either linux or kernel. [grub starts the line with linux; grub4dos with kernel].
(2) After making that change, reboot. Then open Menu>System>Puppy Event Manager, click the Save Sessions Tab, and change the interval to '0'=zero.
(3) Put a check-mark in the "Ask at Shutdown" button. Unless you do that the system doesn't Ask; it saves automatically. 
Remember, computers are idiots operating at the speed of light. It doesn't understand that '0' means 'never'
If you've done it right, on your next reboot a Save icon will appear on your desktop. FYI, you can also manually Save at any time by opening a terminal and typing, without the quotes 'save2flash'.
I realize this is an old thread, but I'd also like to run fossapup64 from my HD in PUPMODE=13. NOT PUPMODE=12 so I can choose whether or not to save the session. I tried to fool the system, as instructed by mikeslr, but i'm unclear where to add pmedia=atahd as my grub.cfg (displayed below) says pmedia=cd several times. I've tried changing all to atahd but it did seem to change a thing.
Thanks!
Code: Select all
insmod part_acorn
insmod part_amiga
insmod part_apple
insmod part_bsd
insmod part_dfly
insmod part_dvh
insmod part_gpt
insmod part_msdos
insmod part_plan
insmod part_sun
insmod part_sunpc
loadfont /boot/grub/font.pf2
set gfxmode=800x600
set gfxpayload=keep
insmod efi_gop
insmod efi_uga
insmod all_video
insmod video_bochs
insmod video_cirrus
insmod gfxterm
insmod png
insmod jpeg
terminal_output gfxterm
insmod ext2
insmod f2fs
insmod ntfs
insmod exfat
insmod loopback
insmod iso9660
insmod udf
background_image /boot/splash.png
set timeout=10
# https://help.ubuntu.com/community/Grub2/Displays
color_normal=cyan/black
#menu_color_highlight=black/light-gray
menu_color_highlight=yellow/red
menu_color_normal=light-gray/black
menuentry "fossapup64 9.5" {
linux /vmlinuz pfix=fsck pmedia=cd
initrd /initrd.gz
}
menuentry "fossapup64 9.5 - Copy SFS files to RAM" {
linux /vmlinuz pfix=copy,fsck pmedia=cd
initrd /initrd.gz
}
menuentry "fossapup64 9.5 - Don't copy SFS files to RAM" {
linux /vmlinuz pfix=nocopy,fsck pmedia=cd
initrd /initrd.gz
}
menuentry "fossapup64 9.5 - RAM only" {
linux /vmlinuz pfix=ram,fsck pmedia=cd
initrd /initrd.gz
}
menuentry "fossapup64 9.5 - No X" {
linux /vmlinuz pfix=nox,fsck pmedia=cd
initrd /initrd.gz
}
menuentry "fossapup64 9.5 - No KMS (Kernel modesetting)" {
linux /vmlinuz nomodeset pfix=fsck pmedia=cd
initrd /initrd.gz
}
menuentry "fossapup64 9.5 - Ram Disk SHell" {
linux /vmlinuz pfix=rdsh pmedia=cd
initrd /initrd.gz
}
menuentry "Shutdown" {
halt
}
menuentry "Reboot" {
reboot
}
Bill_Gates wrote: Wed Jan 24, 2024 4:05 pmI realize this is an old thread, but I'd also like to run fossapup64 from my HD in PUPMODE=13. NOT PUPMODE=12 so I can choose whether or not to save the session. I tried to fool the system, as instructed by mikeslr, but i'm unclear where to add pmedia=atahd as my grub.cfg (displayed below) says pmedia=cd several times. I've tried changing all to atahd but it did seem to change a thing.
Thanks!
Code: Select all
insmod part_acorn insmod part_amiga insmod part_apple insmod part_bsd insmod part_dfly insmod part_dvh insmod part_gpt insmod part_msdos insmod part_plan insmod part_sun insmod part_sunpc loadfont /boot/grub/font.pf2 set gfxmode=800x600 set gfxpayload=keep insmod efi_gop insmod efi_uga insmod all_video insmod video_bochs insmod video_cirrus insmod gfxterm insmod png insmod jpeg terminal_output gfxterm insmod ext2 insmod f2fs insmod ntfs insmod exfat insmod loopback insmod iso9660 insmod udf background_image /boot/splash.png set timeout=10 # https://help.ubuntu.com/community/Grub2/Displays color_normal=cyan/black #menu_color_highlight=black/light-gray menu_color_highlight=yellow/red menu_color_normal=light-gray/black menuentry "fossapup64 9.5" { linux /vmlinuz pfix=fsck pmedia=cd initrd /initrd.gz } menuentry "fossapup64 9.5 - Copy SFS files to RAM" { linux /vmlinuz pfix=copy,fsck pmedia=cd initrd /initrd.gz } menuentry "fossapup64 9.5 - Don't copy SFS files to RAM" { linux /vmlinuz pfix=nocopy,fsck pmedia=cd initrd /initrd.gz } menuentry "fossapup64 9.5 - RAM only" { linux /vmlinuz pfix=ram,fsck pmedia=cd initrd /initrd.gz } menuentry "fossapup64 9.5 - No X" { linux /vmlinuz pfix=nox,fsck pmedia=cd initrd /initrd.gz } menuentry "fossapup64 9.5 - No KMS (Kernel modesetting)" { linux /vmlinuz nomodeset pfix=fsck pmedia=cd initrd /initrd.gz } menuentry "fossapup64 9.5 - Ram Disk SHell" { linux /vmlinuz pfix=rdsh pmedia=cd initrd /initrd.gz } menuentry "Shutdown" { halt } menuentry "Reboot" { reboot }
Change pmedia=cd to pmedia=ataflash but you must have or create a save file/folder first and your boot files must be installed on the HD. Don't know why you have pmedia=cd in the first place (probably created automatically when you booted with a CD first time). Are you booting (is your bootloader installed on a CD) from a CD?
Thank you @amethyst for your quick reply.
Everything is on the HD. It is a clean install using LICK boot manager and fossapup64-9.iso. I do have a savefile. I have 3 different distros on the HD and they are all PUPMODE=12 
I tried changing ALL the instances of pmedia=cd to pmedia=atahd ing grub.cfg, (see below) and still no luck.
LICK boot manager created called lickmenu.lst does something need to be changer there too? (also see below)
Thanks
grub.cfg,
Code: Select all
insmod part_acorn
insmod part_amiga
insmod part_apple
insmod part_bsd
insmod part_dfly
insmod part_dvh
insmod part_gpt
insmod part_msdos
insmod part_plan
insmod part_sun
insmod part_sunpc
loadfont /boot/grub/font.pf2
set gfxmode=800x600
set gfxpayload=keep
insmod efi_gop
insmod efi_uga
insmod all_video
insmod video_bochs
insmod video_cirrus
insmod gfxterm
insmod png
insmod jpeg
terminal_output gfxterm
insmod ext2
insmod f2fs
insmod ntfs
insmod exfat
insmod loopback
insmod iso9660
insmod udf
background_image /boot/splash.png
set timeout=10
# https://help.ubuntu.com/community/Grub2/Displays
color_normal=cyan/black
#menu_color_highlight=black/light-gray
menu_color_highlight=yellow/red
menu_color_normal=light-gray/black
pmedia=ataflash
menuentry "fossapup64 9.5" {
linux /vmlinuz pfix=fsck pmedia=ataflash
initrd /initrd.gz
}
menuentry "fossapup64 9.5 - Copy SFS files to RAM" {
linux /vmlinuz pfix=copy,fsck pmedia=ataflash
initrd /initrd.gz
}
menuentry "fossapup64 9.5 - Don't copy SFS files to RAM" {
linux /vmlinuz pfix=nocopy,fsck pmedia=ataflash
initrd /initrd.gz
}
menuentry "fossapup64 9.5 - RAM only" {
linux /vmlinuz pfix=ram,fsck pmedia=ataflash
initrd /initrd.gz
}
menuentry "fossapup64 9.5 - No X" {
linux /vmlinuz pfix=nox,fsck pmedia=ataflash
initrd /initrd.gz
}
menuentry "fossapup64 9.5 - No KMS (Kernel modesetting)" {
linux /vmlinuz nomodeset pfix=fsck pmedia=ataflash
initrd /initrd.gz
}
menuentry "fossapup64 9.5 - Ram Disk SHell" {
linux /vmlinuz pfix=rdsh pmedia=ataflash
initrd /initrd.gz
}
menuentry "Shutdown" {
halt
}
menuentry "Reboot" {
reboot
}
lickmenu.lst
Code: Select all
## start header
timeout=10
default=0
## end header
## start section xenialpup64
title xenialpup64
find --set-root --ignore-floppies /xenialpup64/vmlinuz
kernel /xenialpup64/vmlinuz pfix=fsck dofsck psubdir=xenialpup64
initrd /xenialpup64/initrd.gz
boot
title xenialpup64 (no save file)
find --set-root --ignore-floppies /xenialpup64/vmlinuz
kernel /xenialpup64/vmlinuz pfix=ram savefile=none psubdir=xenialpup64
initrd /xenialpup64/initrd.gz
boot
## end section xenialpup64
## start section F96-CE_4-2
title F96 CE 4
find --set-root --ignore-floppies /F96-CE_4-2/vmlinuz
kernel /F96-CE_4-2/vmlinuz pfix=fsck dofsck psubdir=F96-CE_4-2
initrd /F96-CE_4-2/initrd.gz
boot
title F96 CE 4 (no save file)
find --set-root --ignore-floppies /F96-CE_4-2/vmlinuz
kernel /F96-CE_4-2/vmlinuz pfix=ram savefile=none psubdir=F96-CE_4-2
initrd /F96-CE_4-2/initrd.gz
boot
## end section F96-CE_4-2
## start section fossapup64-9.5-2
title fossapup64 9.5
find --set-root --ignore-floppies /fossapup64-9.5-2/vmlinuz
kernel /fossapup64-9.5-2/vmlinuz pfix=fsck dofsck psubdir=fossapup64-9.5-2
initrd /fossapup64-9.5-2/initrd.gz
boot
title fossapup64 9.5 (no save file)
find --set-root --ignore-floppies /fossapup64-9.5-2/vmlinuz
kernel /fossapup64-9.5-2/vmlinuz pfix=ram savefile=none psubdir=fossapup64-9.5-2
initrd /fossapup64-9.5-2/initrd.gz
boot
## end section fossapup64-9.5-2Bill_Gates wrote: Wed Jan 24, 2024 5:33 pmThank you @amethyst for your quick reply.
Everything is on the HD. It is a clean install using LICK boot manager and fossapup64-9.iso. I do have a savefile. I have 3 different distros on the HD and they are all PUPMODE=12 :(
I tried changing ALL the instances of pmedia=cd to pmedia=atahd ing grub.cfg, (see below) and still no luck.
LICK boot manager created called lickmenu.lst does something need to be changer there too? (also see below)Thanks
grub.cfg,
Code: Select all
insmod part_acorn insmod part_amiga insmod part_apple insmod part_bsd insmod part_dfly insmod part_dvh insmod part_gpt insmod part_msdos insmod part_plan insmod part_sun insmod part_sunpc loadfont /boot/grub/font.pf2 set gfxmode=800x600 set gfxpayload=keep insmod efi_gop insmod efi_uga insmod all_video insmod video_bochs insmod video_cirrus insmod gfxterm insmod png insmod jpeg terminal_output gfxterm insmod ext2 insmod f2fs insmod ntfs insmod exfat insmod loopback insmod iso9660 insmod udf background_image /boot/splash.png set timeout=10 # https://help.ubuntu.com/community/Grub2/Displays color_normal=cyan/black #menu_color_highlight=black/light-gray menu_color_highlight=yellow/red menu_color_normal=light-gray/black pmedia=ataflash menuentry "fossapup64 9.5" { linux /vmlinuz pfix=fsck pmedia=ataflash initrd /initrd.gz } menuentry "fossapup64 9.5 - Copy SFS files to RAM" { linux /vmlinuz pfix=copy,fsck pmedia=ataflash initrd /initrd.gz } menuentry "fossapup64 9.5 - Don't copy SFS files to RAM" { linux /vmlinuz pfix=nocopy,fsck pmedia=ataflash initrd /initrd.gz } menuentry "fossapup64 9.5 - RAM only" { linux /vmlinuz pfix=ram,fsck pmedia=ataflash initrd /initrd.gz } menuentry "fossapup64 9.5 - No X" { linux /vmlinuz pfix=nox,fsck pmedia=ataflash initrd /initrd.gz } menuentry "fossapup64 9.5 - No KMS (Kernel modesetting)" { linux /vmlinuz nomodeset pfix=fsck pmedia=ataflash initrd /initrd.gz } menuentry "fossapup64 9.5 - Ram Disk SHell" { linux /vmlinuz pfix=rdsh pmedia=ataflash initrd /initrd.gz } menuentry "Shutdown" { halt } menuentry "Reboot" { reboot }lickmenu.lst
Code: Select all
## start header timeout=10 default=0 ## end header ## start section xenialpup64 title xenialpup64 find --set-root --ignore-floppies /xenialpup64/vmlinuz kernel /xenialpup64/vmlinuz pfix=fsck dofsck psubdir=xenialpup64 initrd /xenialpup64/initrd.gz boot title xenialpup64 (no save file) find --set-root --ignore-floppies /xenialpup64/vmlinuz kernel /xenialpup64/vmlinuz pfix=ram savefile=none psubdir=xenialpup64 initrd /xenialpup64/initrd.gz boot ## end section xenialpup64 ## start section F96-CE_4-2 title F96 CE 4 find --set-root --ignore-floppies /F96-CE_4-2/vmlinuz kernel /F96-CE_4-2/vmlinuz pfix=fsck dofsck psubdir=F96-CE_4-2 initrd /F96-CE_4-2/initrd.gz boot title F96 CE 4 (no save file) find --set-root --ignore-floppies /F96-CE_4-2/vmlinuz kernel /F96-CE_4-2/vmlinuz pfix=ram savefile=none psubdir=F96-CE_4-2 initrd /F96-CE_4-2/initrd.gz boot ## end section F96-CE_4-2 ## start section fossapup64-9.5-2 title fossapup64 9.5 find --set-root --ignore-floppies /fossapup64-9.5-2/vmlinuz kernel /fossapup64-9.5-2/vmlinuz pfix=fsck dofsck psubdir=fossapup64-9.5-2 initrd /fossapup64-9.5-2/initrd.gz boot title fossapup64 9.5 (no save file) find --set-root --ignore-floppies /fossapup64-9.5-2/vmlinuz kernel /fossapup64-9.5-2/vmlinuz pfix=ram savefile=none psubdir=fossapup64-9.5-2 initrd /fossapup64-9.5-2/initrd.gz boot ## end section fossapup64-9.5-2
Why two bootloader configs?
lickmenu.lst does not have any pmedia= parameters, so if the lick bootloader has the ability to temporility alter a parameter at boot time without actually editing the file, what happens when you add pmedia=ataflash?
do you see a lick bootloader at boot? a grub menu? one after the other?
If the last 5 characters are "flash" the top layer in the stack remains the tmpfs in memory, otherwise any found save layer becomes the top layer in the stack.
@amethyst I was looking at the wrong file. I added pmedia=ataflash to lickmenu.lst and puppy no longer saves the savefile unless I tell it to.
Thanks for your help!