Discussion, talk and tips
https://forum.puppylinux.com/
Hi,
I am using fossapup on a penrive.While I try to save the session before the shut down it hangs during the shut down time giving a #in the black screen.What to do now?
when you see the "#" on the black screen can you type at that prompt?
What happens if you type "reboot" and press enter at that "#"?
No I can't write at that time.
There is no blinking cursor
Only a hash
How long did you wait during the time the machine seemed stalled? It sounds like a write permissions or a usb drive problem. How is the pen drive formatted?
While I try to save the session before the shut down
Are you clicking on the desktop save icon to do the save or just doing a normal shutdown, having the save updated, as part of the shutdown?
Doing normal shutdown having the save updated.
The problem has started after I have started to save the session.
It is FAT2
FAT2 is not a format.
Is it fat32 format?
Have you made a initial save and booted using it?
This is the save you are trying to update on shutdown and get this hung condition?
If yes.
Was there anything you did or software you added, just before this problem started?
A little guessing by me.
Fat32 format has a max file size limit of 4GB.
The save file you originally made was what size?
It may be too small for what you are trying to put in it.
May need to make it bigger.
But the max size it can be is 4GB, if on a fat32 formatted partition.
As a follow-up to bigpup's thought that you're problem may be that you have reached or exceeded Fat32's 4 Gb limitation, you may want to consider the techniques discussed here, viewtopic.php?p=2235#p2235 even if you are not concerned with security. As its 2nd Paragraph notes, one of the roots of that post was shinobar's thread “Keep your savefile slim and healthy”. That is particularly important when you are booting from drive/partition having Fat32's size restriction.
The problem started after I have made made a initial save .As it was a bit experimental, I did what was recommended by the os.The file size was taken ~500 mb(recommended by the os).I didn't changed anything except for the time and keyboards layout and I didn't installed any app(because there is a problem with WiFi adapter where puppy os can't detect the adapter ).
So the save file must be small.
mikeslr wrote: ↑Thu Apr 22, 2021 9:14 pmAs a follow-up to bigpup's thought that you're problem may be that you have reached or exceeded Fat32's 4 Gb limitation, you may want to consider the techniques discussed here, viewtopic.php?p=2235#p2235 even if you are not concerned with security. As its 2nd Paragraph notes, one of the roots of that post was shinobar's thread “Keep your savefile slim and healthy”. That is particularly important when you are booting from drive/partition having Fat32's size restriction.
I think the total memory usage has
not exceeded 1 GB(Including the puppy os)
Just to be sure you are not confusing RAM usage with SaveFile usage, place your mouse-cursor on top of the icon on your Taskbar representing your SaveFile. When you do a tool tip will be displayed showing the SaveFile's current size and the amount of available space in it. RAM is RAM. A SaveFile is a dedicated and size-limited portion of your Storage Medium.
Pets (and IIRC other applications) are compressed in their repositories and transmitted as compressed files. They expand when you install them. Depending on the application and the compression ratio used, they will occupy between 2 and 3 times the amount of space in a SaveFile. The contents of SaveFiles are NOT compressed.
The less available space in a SaveFile, the longer it will take to write anything to it. I've had problems trying to install even a small (couple of mbs) application when the available space in a SaveFile got close to only 100 Mbs. Obviously, you can't Save an application when to do so requires more space in a SaveFile than is available.
Just checked the total USB memory usage .
Its just 1.3gb used
500MB is too small a save file.
Other programs use up space in the save.
Especially browsers and there saved stuff.
Boot and try to make the save file bigger.
In the menu is program resize personal storage.
Run this program.
Make the save 2 or 3 GB in size
The program actually works to change size on reboot.
If this will not work (may not with a broken save file).
I would delete the old save.
Boot not using the save and shutdown making a new save file of 2 or 3 GB size.
The boot menu may have option to boot not using the save.
This entry:
fossapup64 9.5 - RAM only