Cannot choose where to save the savefile

[mimine]

Hi,
I boot Fossapup64 from a USB drive.
My PC has a usb drive and a hard disk.
When exiting Fossapup64, it asks me to save the savefile, but only proposes the USB drive !
That's not good, I want to chose where to save my savefile...
Thanks

[williams2]

If you have a save file on the usb drive, you can copy the file to the hard drive.
Puppy should find it the next time you boot.

You should really copy the save file while Puppy is not using it,
from another OS, or booting pfix=ram,
though I have done similar copies many times with the save file in use, with no problems.

reboot, choose the save file on the hard drive, if it asks.
If it seems to work properly, you can delete or rename or move the save file on the usb drive.

I find that the pmedia= kernel boot option is the cause of the problem.
Changing it to

pmedia=hdata
or
pmedia=cd
or
pmedia=

or deleting the pmedia option completely, might work.

pmedia=cd is supposed to allow you to choose from all possible locations,
but sometimes, it may not work.

EDIT: The psave=sda4 kernel boot option might work. Change sda4 to the correct partition name, of course.
See https://forum.puppylinux.com/viewtopic.php?t=5818

[mimine]

@williams2
thanks for the complicated stuff that no "average user" would understand.

The interface should give us the choice about where to save the savefile.
I think in bionicpup it let us choose where to save the save file, if I remember correctly.
So it's a bug.

[bigpup]

It is not a bug, but the way the shutdown save process was designed to work, when Fossapup64 9.5 was developed.

The thinking was the install of Puppy Linux on a USB drive.
You would want the save to be stored on this USB drive, so if you used it to boot some other computer.
All the needed Puppy files would be on the drive.
The Puppy OS and the save for it.

You can try making some pemedia= changes, to the boot loader config file entry, that controls how it boots.

With the save on the USB, writes to the save are only when you click on the desktop save icon, at a set time to auto save (which can be turned off), and at shutdown (where you could be asked to save, not save, or auto save)

Save on any other drive, will just directly write to the save, as anything happens, that needs to write to the save.

So, are you OK with making this change to how writes to the save are done?

[mimine]

@bigpup
yes I understand.
But in my opinion it's a bug in the design, because bionicpup did let us choose where to save the savefile...

(Even if the savefile was on another hard disk, there could also be created a save button on the desktop too. So it's not related to the problem.)

[Clarity]

Hi @mimine

I ask you to do the following, then follow these instructions.

• Do:
  Deteremine which of the partitions on your system's HDD that you want to save your sessions. Some of us have partitions that have a lot of space on an NTFS/FAT32 partition, while others of us have created a Linux partition (ie EXT2/EXT3/EXT4) which we use to save Linux stuff.
  .

• After you choose the HDD partition: Follow:
  On the boot of ANY Linux PUP distro of your choice, at its Menu,

  1. edit one of the Menu line (usually many of us choose the top line) and add
     psave=sdaX:/Sessions/

     • where "X" is the partition number you chose from the above 'Do' step

     • and "Sessions" is the folder on the partition your session-saves will be kept...and found on reboot.

  2. Allow your PC to boot the menu line

  3. EXPECT, when you shutdown/reboot that your PUP will offer to save the session in a folder ("/Session" folder) on the partition you chose in the 'Do' step

This works for the WoofCE PUPs since 2019.

[mimine]

@Clarity
thank you very much.
But that's not my question.
My question is why isn't it by default in fossapup, like in bionicpup, to have the choice on where to save ?

[Clarity]

Sorry for misunderstanding. It is my experience, like yours, that EACH PUP is distinctly different from each other due to several factors... even those in the same family. Thus, you are witnessing how so.

I believe, the times when each were developed contributes largely to the question of "Why". Not speaking for @666philb the timing and use of WoofCE would/does impact distro outcomes as well.

Just some ideas/guesses