Hi,
I've tried saving puppy save files to a partition on my HDD which has worked in the past but no longer works properly.
Having deleted the previous save file and made a new lightly encrypted one it will fail to access the save file properly and as such this error manifests in that it does not load the background image or the icon images. There are also some problems with the interface of the device mounter software for example and I am unable to locate the hard-drive file from the root menu etc. What the hell is going on?
When restarting the x-server I get this message:
...f X failed to start, type "xorgwizard" to setup X"
Then it opens up SFS-Load on-the-fly, asking me if I want to load extra SFS files. I get the feeling this/these are something it should have loaded automatically and I don't know which files need to be loaded in this case.
Also: The error message associated with the background image reads:
"Couldn't recognise the image file format for /usr/share/backgrounds/defult.jpg, backdrop removed"
Any ideas?
I would really appreciate some help with this one, cheers
Failure to load encrypted Save file properly
What version of Puppy are you using and how are you using it? (Frugal install, booting from CD with Save file on hdd, etc.) How much RAM has the computer?
Were the previous Save files, the ones that worked, also encrypted?
What do you mean you are unable to locate the hard drive file from the root menu? What hard drive file, the encrypted Save file?
Were the previous Save files, the ones that worked, also encrypted?
What do you mean you are unable to locate the hard drive file from the root menu? What hard drive file, the encrypted Save file?
type
in the console to see what is mounted
A too small Pupsave-file choice at shutdown might have corrupted the filesystem inside the save file . Lately there had been fixes to shutdown to check if the savefile got mounted read-write and to offer only choices for save-files above the needed space .
Ext2 fs can corrupt much easier then ext3 or 4 .
There had been a time where much was going on about such, but that is long time ago :
How to mount encrypted pup? (SOLVED)
Code: Select all
mount
A too small Pupsave-file choice at shutdown might have corrupted the filesystem inside the save file . Lately there had been fixes to shutdown to check if the savefile got mounted read-write and to offer only choices for save-files above the needed space .
Ext2 fs can corrupt much easier then ext3 or 4 .
There had been a time where much was going on about such, but that is long time ago :
How to mount encrypted pup? (SOLVED)
Thanks,
Just going to add:
* It has worked with a non encrypted save that's 1.25GB - 2GB
* I always save as ext3, the same as the partition.
* The partition its saved to is within an extended partition.
* Normally, I can access the partition file system via the file browser (allowing me to see the save file).
* The computer has 2GB Ram
Just going to add:
* It has worked with a non encrypted save that's 1.25GB - 2GB
* I always save as ext3, the same as the partition.
* The partition its saved to is within an extended partition.
* Normally, I can access the partition file system via the file browser (allowing me to see the save file).
* The computer has 2GB Ram
What version of Puppy?
Frugal install to hard drive or run from live Puppy CD/DVD?
Frugal install to hard drive or run from live Puppy CD/DVD?
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)