Xenialpup64 refuses to use save folder

[Lassar]

I was using a save folder just fine.

Tried to reboot and could not reboot, so I shut down the computer manually.

Xenialpup64 cashed.

So I used, one of my other puppies in multi-boot to get to the desktop and rename the
the save folder.

Now I could boot up xenialpup64, but it refuses to use a save folder.

When I check Puppy Event Manager the pupmode is always 5.

What can I do to fix this?

[musher0]

I was using a save folder just fine.

Tried to reboot and could not reboot, so I shut down the computer manually.

Xenialpup64 cashed.

So I used, one of my other puppies in multi-boot to get to the desktop and rename the
the save folder.

Now I could boot up xenialpup64, but it refuses to use a save folder.

When I check Puppy Event Manager the pupmode is always 5.

What can I do to fix this?

HI Lassar.

There are a number of unanswered questions in your post,

-- "you tried to reboot but could not." Hmm... A little bit of details would help here,
please? It just was taking too long a time, or one program was stuck, or you forgot that
you were downloading something, or what?

-- how did you manually shut down? You pulled the electricity cable? Or you pushed the
reset button? In a forced scenario like this, the Pup may not have closed everything
(apps, partitions) properly.

But I think the main thing is: "you renamed the save folder." (Why? But maybe it does
not matter.)

In any case, try creating a "dummy" pupsave for your XenialPup64 in addition to what
you have. You can create it with this command:

Code: Select all

echo . > xenialsave-dummy.2fs

Or whatever name the xenialPup64 uses for its pupsaves.

Reboot. During boot Puppy should stop and ask you which pupsave / pupfolder to use.
Of course you type the number of the good pup folder, not the number of the dummy.

What happens? Any luck?

If no luck, it could be that the Pup is expecting the old pupfolder name because you
forced the shutdown. It looks at the old place and the folder is not there. The Pup does
not know where to look for its save folder. Maybe you have to create a new pup folder
as if it was the first time.

Just a thought.

IHTH. BFN.

[bigpup]

Now I could boot up xenialpup64, but it refuses to use a save folder.

I am going to assume you are using xenialpup64 7.5

Xenialpup64 7.5 is only going to see a save folder if the name is:

xenialpup64save

It can have more added to the name by using a dash (-) at the end and adding whatever you want.

Example:
xenialpup64save-something

So, if you changed the name, that is the problem about not finding the save.

[Lassar]

I decided as much trouble, that I had using save folders, think I will make a custom iso where palemoon folder is symlink to a folder on a ext4 partition.

Also think I will do the same with the download folder.

[amigodetux]

I have a similar problem, in other post I wrote:

"Now I am trying to create another USB in EXT4 for my use, I used for this, the Puppy Universal Installer, as in previous versions, but when finally boot the USB here go again, stop the process after load vmlinuz and initrd.gz,"

For me, Xenialpup worked well in a FAT32 but when I want to install in a Ext4 formated USB with the goal of use a save folder instead a save file, It does not work, at least for now.

[Lassar]

I tried to get rid of anything that might remotely confuse puppy linux.

I rename some folders that had xenial in the foldername.

Rename anything that had the word save in the folder.

Deleted so iso's and sha256 because has the name xenial in them.

Finally got the save function working again.