(old)Puppy Linux Discussion Forum

just the option Ram in menu.lst would be fine. Because adding pfix=ram in script or creating a second pupsave will not be guessed by a newbie. Generally they don't register in our forum. Not sure they read it.
The problem exists only when pupsave is alone, accessd to Ram comes backs as soon as a second pupsave is created (option 0, pupsave 1, pupsave 2, 3.4...)

People without windows can erase windows chapters : Yes or no ?
"At least one item of Windows menu are displayed here no matter they are installed or not. Erase the items if you do not need boot up Windows. But the last (was 'top' before v1. entry is recommended to leave. Especially in case you install Grub4Dos on removable devices because they might be useful with other PC's.
Duplicated folder names""

Yes and no.

If Windows is on the computer and you are using Grub4dos as the primary (only) boot loader.
Windows entries need to stay.

If Windows is not on computer or you have a way of selecting a different boot loader, other than Grub4dos, to boot Windows.
Do not need Windows menu entries in Grub4dos.

bigpup wrote:As a user of Puppy for a long time and someone that tries to help new Puppy users.

I disagree.

The menu-advanced.lst was added to Grub4dos to provide
Advanced boot options.
New users of Puppy do not need to see or use these options, until they get some understanding of how Puppy works.
For them, it will just cause problems they do not understand.

The menu.lst is the normal boot entries.
Those are all you usually need to use.

A lot of work was done to Grub4dos boot loader to improve how it works in detecting what is on the computer and making a correct menu entry.
If you are not using the latest version you should.
grub4dos-0.4.4.v1.9.2
http://www.murga-linux.com/puppy/viewtopic.php?t=51697

I am sure you understand the edit menu feature at the end of running Grub4dos Config.
That is for people that understand the menu and how it is used. People that like to do things the way they want them.
I always edit out the Windows stuff.

But as I understand it the new grub4dos does not list the RAM mode option in the "regular" menu.lst but in the advanced menu. If that is so, I have to disagree with you. Booting in RAM mode with puppy is one of puppys best and well-known features. Why should this be in the advanced menu?

Simple reason.

New users of Puppy do not need to see or use these options, until they get some understanding of how Puppy works.
For them, it will just cause problems they do not understand.

I have answered, I do not know how many times, why the save is not being used. Turns out they are using a boot loader that has pfix=ram on the menu entry.

Also, this one from a new Puppy user.
I thought pfix=ram would make Puppy run in ram only.
No, a frugally installed Puppy still normally runs in ram.
pfix=ram keeps Puppy from using the Puppysave.
Option has nothing to do with making Puppy run in ram.

You may understand all of these options.
A new Puppy user does not.

Edit the menu to make it the way you want it.
This is Linux,
You have options.
However, you need to understand the option before you use it.

Having two menu.lst files is more confusing to a new user me thinks.

This is confusing!

I want to underline that Puppy Linux installed by Grub4dos will load automatically pupsave only when pupsave is alone.
when two pupsaves, option Ram is given again to the user, without having to add pfix-RAM in script.
Newbies soon use pupsaves, because it's really boring to set again and again Fr, Parisfr keyboard, install a browser (french bad idea not to include one).
Furthermore Puppy will ask at shutdown if he wants to create pupsave..
What is not an evidence is that newbie should create two pupsaves to get 0 (zero) boot in ram appearing as a choice when booting.
About the philosophy, devs now consider their puppies will be used by people as experts as them, that is the big error that will soon reduce Puppy Linux to a training OS for bachelors , even for Linux high school students, so around one hundred guys (addicted)
Don't be confused, Grub4Dos is the easiest way to install Puppies; IMO; but some improvement would make it perfect.

Develop for experts is easy, develop for everybody is a lot more complicated. You must imagine all wrong ways your program could be used. And without feed-back, complication becomes Huge.
Now devs ask users .. to compile

Grub4dos will load automatically pupsave only when pupsave is alone.
when two pupsaves, option Ram is given again to the user, without having to add pfix-RAM in script.

That is not Grub4dos boot loader doing this.

That is the Puppy boot process program(s) in control.
Grub4dos is already finished and no longer in control of what is happening.

When Puppy boot process detects more than one save for the Puppy version. It stops and asks, what save do you want to use or what do you want to do?

see page one, add ram option in menu.list.
I don't want to modify Grub4dos, i give users how to add option RAM at boot;
Screenshot here below is not an option, but something keeps your Puppy always booting in Ram , Option has to be offered in menu.lst.