robert_m wrote:Let's all hope that this can get resolved!
I downloaded XenialPup64, tried it on two systems, I like it!
When I closed it, I save to my USB Flash.
I then moved the flash to the 2nd system, and it booted to the "This is the First Time you are Running..." screen. Did I save the .sfs to the hard drive by accident? No, I have 3 files on the sdc2 partition - see attached "empty3fs.png"
I see that I actually have two earlier sessions I saved, only the first .2fs has any content.
Is this a result of the problem that is discussed in this thread, or something else.[/img]
Hello robert_m.
No, your problem is not related to the subject of this thread, since you
were able to create three pupsaves.
I would however delete the empty pupsaves or move them to a sub-sub-
directory (where Puppy can't recognize / reach them). Yes, you have
read correctly, that's "sub-sub-directory", i.e. second or even third
"basement" under your /mnt/sdc2. Move the extra pupsaves to
something like /mnt/sdc2/extra/psaves/.
BTW, the "*.sfs" file ending is reserved for use for and by the Puppy
system itself. Pupsaves typically have a "*.2fs", "*.3fs" or "*.4fs" file
ending, depending on whether you chose the ext2, ext3 or ext4 file-
system structure for your pupsave when you created it.
Finally a word of caution on the ready-made pupsaves provided in this
thread: I have created them on a 32-bit system. They are totally
untested on a 64-bit.
I'd be happy to learn that they work on a 64-bit Puppy, the file structure
being the same; but at this point I can provide no guarantees. Thanks
for your understanding.
IHTH.
~~~~~~~~~~~~
Edit, 5 minutes later.
I do not have a 64-bit XenialPup on this computer, so I'm groping a bit
in the dark. That said...
Looking at you list of files in your screen cap, I think I can explain why
your Pup is saying "This is the first time..."
The two empty files are automatically dismissed at boot-up because they
are empty. Try to load them manually, and you will get an error message.
The valid one, content-wise, that has +/- 450 Kb, seems to bear only the
default pupsave name, not a personalized one.
A pupsave file name should have 3 parts, like so: xenialsave-arf.2fs.
A default "xenialsave" name, provided by the Puppy (in this case, my
32-bit Puppy), a dash and a second part provided by us, the users, and
thirdly the file ending.
The middle, personalized, part seems to be missing on your pupsave. So
your Puppy thinks that file is also invalid, and concludes: "This user has
not created a pupsave yet". So, of course, it asks you to create a new
one.
Try renaming it from another Pup? Or even from the pristine
xenialPup-64, it should be ok, but you will have to reboot in this case.
I mean adding a middle part to the file name? Maybe something like:
xenialpup64save-me.2fs. I indicate "-me", but it can be "-schmurf" or
anything you like. (A combination of letters and numbers only, however;
no punctuation or fancy characters.)
Although at 450 Kb, you likely have only your time zone and language
localization saved in it, yes? So maybe just respond to the prompt and
create a new pupsave?
But don't forget to provide a personalization part when asked. It is
important to type in one, since a PuppyLinux system can have several
pupsaves for various uses or functions.
IHTH. Keep us posted as to how it went?