How to get Slacko's boot menu when booting into RAM?
How to get Slacko's boot menu when booting into RAM?
booting into RAM? Now it sends me to the save right away, don't get the boot menu ...
Re: how can I get to Slacko's boot menu, with the option of
One way is trick it into thinking that you have 2 save files (or folders). Assuming your save file or folder is called puppysave.2fs. Make a text file called puppysave-dummy.2fs and save it in the same directory as the original save file. Now when boot it will ask you if you want to use puppysave.2fs, puppysave-dummy.2fs, or no save file at all. At that point, you can boot with no save file and create another real one if you want and delete puppysave-dummy.kuman11 wrote:booting into RAM? Now it sends me to the save right away, don't get the boot menu ...
What specific version of Slacko?
Slacko is installed on what?
The install was done how?
What did the boot menu normally give you for boot options?
If we know exactly what boot loader menu you have, could give better answer as to how to select options.
Most boot menus are setup to boot the normal boot option after a few seconds of no activity.
Some are very short time, 5 seconds or less.
This is the time you have to select other options.
After you make a save it is normal to boot using it.
Slacko is installed on what?
The install was done how?
What did the boot menu normally give you for boot options?
If we know exactly what boot loader menu you have, could give better answer as to how to select options.
Most boot menus are setup to boot the normal boot option after a few seconds of no activity.
Some are very short time, 5 seconds or less.
This is the time you have to select other options.
After you make a save it is normal to boot using it.
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)
Hi kuman11,
If you're using Grub4dos as bootloader, the last part of the menu.lst it wrote is a listing for "Advanced Menu". Select that. The second listing on the GUI which then appears will be "title Slacko XXX ... RAM mode\nBoot up Puppy without pupsave". Select that and Slacko will boot without using the SaveFile/Folder.
If you're using Grub4dos as bootloader, the last part of the menu.lst it wrote is a listing for "Advanced Menu". Select that. The second listing on the GUI which then appears will be "title Slacko XXX ... RAM mode\nBoot up Puppy without pupsave". Select that and Slacko will boot without using the SaveFile/Folder.
At the top of menu.lst is a block of instructions something like this:
# menu.lst produced by grub4dosconfig-v1.9.2
#color blue/cyan yellow/blue white/black cyan/black
splashimage=/splash.xpm
timeout 10
default 0
See if the timeout argument somehow got set to 0 (zero). With no 'timeout' you would have no opportunity to choose anything other than the default (0=first) menu.listing, thus unable to select Advance Menu.
# menu.lst produced by grub4dosconfig-v1.9.2
#color blue/cyan yellow/blue white/black cyan/black
splashimage=/splash.xpm
timeout 10
default 0
See if the timeout argument somehow got set to 0 (zero). With no 'timeout' you would have no opportunity to choose anything other than the default (0=first) menu.listing, thus unable to select Advance Menu.
mike, I have grub.cfg with similar values, seems timeout is set at 10
don't see menu.lst
insmod png
background_image /xslacko.png
set timeout=10
menuentry "Start X-Slacko Slim" {
linux /vmlinuz
initrd /initrd.xz
}
menuentry "Start X-Slacko Slim - RAM only" {
linux /vmlinuz pfix=ram
initrd /initrd.xz
}
menuentry "Start X-Slacko Slim - No X" {
linux /vmlinuz pfix=nox
initrd /initrd.xz
don't see menu.lst
insmod png
background_image /xslacko.png
set timeout=10
menuentry "Start X-Slacko Slim" {
linux /vmlinuz
initrd /initrd.xz
}
menuentry "Start X-Slacko Slim - RAM only" {
linux /vmlinuz pfix=ram
initrd /initrd.xz
}
menuentry "Start X-Slacko Slim - No X" {
linux /vmlinuz pfix=nox
initrd /initrd.xz
I would not delete any of them. They are in the save for a reason.
If you are using a save file.
Resize it to make it bigger, so it has some free space in it.
If using a save folder.
It is limited by how much free space is on the partition the save folder is on.
Check for stuff on the partition not needed.
If you have the browser you use setup to save everything it does. That can eat up space in the save.
Check the preferences in the browser.
Cache settings, history settings, etc........
If you are using a save file.
Resize it to make it bigger, so it has some free space in it.
If using a save folder.
It is limited by how much free space is on the partition the save folder is on.
Check for stuff on the partition not needed.
If you have the browser you use setup to save everything it does. That can eat up space in the save.
Check the preferences in the browser.
Cache settings, history settings, etc........
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)
-
a_salty_dogg
- Posts: 180
- Joined: Sun 15 Dec 2013, 19:08
@kuman11
You can massively reduce the size of your save files by:
1. Loading .sfs files instead of installing.pets, whenever you have the option.
2. Symlink large files/folders, typically browsers and their config files etc., to "home" directory. (Feel free to ask if you need guidance how to do this.)
Also has the advantage of letting you share up-to-date browser personal settings between Puppies, if applicable.
You can find which files and folders are the greediest for space by running and navigating around the "gdmap" utility.
You can massively reduce the size of your save files by:
1. Loading .sfs files instead of installing.pets, whenever you have the option.
2. Symlink large files/folders, typically browsers and their config files etc., to "home" directory. (Feel free to ask if you need guidance how to do this.)
Also has the advantage of letting you share up-to-date browser personal settings between Puppies, if applicable.
You can find which files and folders are the greediest for space by running and navigating around the "gdmap" utility.
-
a_salty_dogg
- Posts: 180
- Joined: Sun 15 Dec 2013, 19:08
Oh, I'd thought all Puppies had gdmap built in, but it seems X-Slacko Slim doesn't for some reason (maybe excluded in attempt to keep it light?).
The 5.7 Slackos have version 0.8.0, so I'd suggest trying that one first, unless someone with more experience of working with XSlacko Slim comes along and can advise better? (Never use it myself, found it too finicky)
After installation the menu entry should appear under "Filesystem > Gdmap graphical disk usage", or start it in terminal as "gdmap".
The 5.7 Slackos have version 0.8.0, so I'd suggest trying that one first, unless someone with more experience of working with XSlacko Slim comes along and can advise better? (Never use it myself, found it too finicky)
After installation the menu entry should appear under "Filesystem > Gdmap graphical disk usage", or start it in terminal as "gdmap".