Grub4DosConfig

Miscellaneous tools
Message
Author
User avatar
Pete22
Posts: 264
Joined: Fri 08 May 2009, 22:59
Location: Utah, USA

fixing the boot up menu

#286 Post by Pete22 »

# menu.lst produced by grub4dosconfig-v1.7.9
#color white/blue black/cyan white/black cyan/black
splashimage=/splash.xpm
I tried this fix in saluki and in lighthouse on 2 machines.
It does not solve the menu highlighting problem.

The puppy that grub4dos does not find is Legacy os4.

Hope that helps.

Pete

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Re: fixing the boot up menu

#287 Post by shinobar »

Pete22 wrote:
# menu.lst produced by grub4dosconfig-v1.7.9
#color white/blue black/cyan white/black cyan/black
splashimage=/splash.xpm
I tried this fix in saluki and in lighthouse on 2 machines.
It does not solve the menu highlighting problem.
Will you try to comment out the 'splashimage' line instead of the 'color' line if you are not using splash image. (Both menu.lst and menu-advanced.lst)
# menu.lst produced by grub4dosconfig-v1.7.9
color white/blue black/cyan white/black cyan/black
#splashimage=/splash.xpm
Pete22 wrote:The puppy that grub4dos does not find is Legacy os4.
Where is the pup_421.sfs?
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#288 Post by don570 »

Would you check out these two buttons in
Pemasu's Precise.

They caused the application to freeze when clicked.

I didn't have time to test properly

The app does work well otherwise.


Image

__________________________________________

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Some buttons freeze

#289 Post by shinobar »

don570 wrote:Would you check out these two buttons in
Pemasu's Precise.
They caused the application to freeze when clicked.
Thank you don for the report.
I am aware that the '<list>' box of the gtkdialog is buggy under some circumstance. It will be replaced with '<tree>' by coming release. Hopefully it will fix the problem.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
Pete22
Posts: 264
Joined: Fri 08 May 2009, 22:59
Location: Utah, USA

#290 Post by Pete22 »

I am using a splash screen with saluki 21.
But the fix did not fix it.

The Legacy 4.21 sfs is in the mnt/home/Legacy os4 folder.


hope that helps.

Pete

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

spaces in the directory name

#291 Post by shinobar »

Pete22 wrote:The Legacy 4.21 sfs is in the mnt/home/Legacy os4 folder.
means 'Legacy os4' with a space? Can you save your session there?
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Re: using splash

#292 Post by shinobar »

@Pete22
Ensure BOTH from the menu.lst and menu-advanced.lst commented out the 'color' line if you use the splash image.
menu*.lst wrote:# menu.lst produced by grub4dosconfig-v1.7.9
#color white/blue black/cyan white/black cyan/black
splashimage=/splash.xpm
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
Pete22
Posts: 264
Joined: Fri 08 May 2009, 22:59
Location: Utah, USA

#293 Post by Pete22 »

OH Ok I found what you were talking about for the Advanced Menu.lst. :oops:

Yes that fixes that problem.

Thanks for your persistence in helping me SEE it. :wink:


This is a great program.

Pete

User avatar
Pete22
Posts: 264
Joined: Fri 08 May 2009, 22:59
Location: Utah, USA

Legacy os and others that the grub4dos can't see.

#294 Post by Pete22 »

Yes, the space makes a difference.
In fact, I also had this problem with HanSamBen. There was a blank space
after the name that I did not know was there. When I deleted it, Grub4dos could see the installation.
When I tried to boot Hansamben, Grub4dos did it with no problem.
So I changed Legacy os4 to Legacyos4,and then Grub4dos could see the installation.

Now I have a new problem with Legacy. It says it can not find the main sfs file that is in the folder. So boot fails :?

With Lighthouse x64 5.14 Grub4dos finds the main sfs file but can not load it into ram. So boot fails. :?


Still I love this program.

Pete

vanchutr
Posts: 438
Joined: Sat 05 Aug 2006, 12:04

#295 Post by vanchutr »

To Pete22
This is my entry in menu.lst to boot lighthouse 64

Code: Select all

title lighthouse 64 MARINER
  find --set-root --ignore-floppies /lighthouse/initrd.xz
  kernel /lighthouse/vmlinuz pfix=vesa pmedia=atahd psubdir=lighthouse
  initrd /lighthouse/initrd.xz
This can help you? May be

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

bug in version 179

#296 Post by don570 »

Note to Shinobar about new version of Grub4dos 179 :

I made a mistake when criticising Pemasu's Precise

It was actually Lucid Puppy 528. I burnt an ISO and
I made a full install.

When I tested more recent Puppies they worked well.

Here's how to duplicate the bug just for the record.

1) I booted the LUPU 528 CD puppy pfix=ram

2) My browser wasn't set and I have no internet access.
I installed your pet package.

3)From the start menu I launched grub4dos, then I
selected a hard drive entry and clicked on either of the
two icons I showed in picture.

4) App would freeze.



I checked a full install of LUPU 528 and it did the same thing.

Note that version 1.7 doesn't have this problem.

______________________________________________

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Re: bug in version 179

#297 Post by shinobar »

don570 wrote:I made a mistake when criticising Pemasu's Precise

It was actually Lucid Puppy 528. I burnt an ISO and
I made a full install.

When I tested more recent Puppies they worked well.
I couldn't reproduce with lupu-528.005 furugal install, pfix=ram. Depends on the hardware?
But i have encountered similar problem with other program using <list> in the gtkdialog3 on lupu-528JP(developing). Anyway, I will switch to <tree> instead of <list> in the next release. The <tree> is used in the Puppy Package Manager, so it must be stable on many Puppies.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Re: Legacy os and others that the grub4dos can't see.

#298 Post by shinobar »

Pete22 wrote:Now I have a new problem with Legacy. It says it can not find the main sfs file that is in the folder. So boot fails :?

With Lighthouse x64 5.14 Grub4dos finds the main sfs file but can not load it into ram. So boot fails. :?
Have you ever run the Legacy and/or Lighthouse x6 on your PC?
The kernel the Puppies use and your hardware may cause a problem.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#299 Post by don570 »

I couldn't reproduce with lupu-528.005
Two possible reasons

1) I used the basic ISO which has gtkdialog 0.7.21
not .8 (I believe)

2) I tested on a full install and booting from a CD

______________________________________________

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

grub4dos-0.4.4.v1.8.0

#300 Post by shinobar »

EDIT: there was a fault:
#15jun12 v1.8.0: fix was no Safe mode nor RAM mode

Released grub4dos-0.4.4.v1.8.0.pet (2012-06-15)
http://shino.pos.to/linux/puppy/

15jun12 v1.8: fix was failed to install on floppy with recent kernels like Wary/Racy-5.3 and etc., fix menu header was problem with splash image, detectiong slitaz and fatdog
# 28apr12 v1.7.9: improved detecting special puppies like LHP, advanced menu, old menus, legacy grub compatible menu, splash image, text domain, exit status

Translations: Calling for translations. The .pot file at /usr/share/doc/nls/grub4doscinfig. The help file at /usr/share/doc/help/C/grub4dosconfig.html.
Last edited by shinobar on Fri 15 Jun 2012, 12:08, edited 2 times in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Grub4DosConfig 1.8.0

#301 Post by shinobar »

Sorry, there was a fault:
#15jun12 v1.8.0: fix was no Safe mode nor RAM mode
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

gcmartin

#302 Post by gcmartin »

Request for explanation/guidance
Edited: 2012-06-27 SOLVED! Remove the pmedia parm and system boots

Code: Select all

# menu.lst produced by grub4dosconfig-v1.7.2
color blue/cyan yellow/blue white/black cyan/black
timeout 10
default 0

# Frugal installed Puppy
title FAT Slacko 533
  root (hd0,0)
  kernel /PUP-boots/FATSlacko/vmlinuz pmedia=usbflash pfix=fsck
  initrd /PUP-boots/FATSlacko/initrd.gz psubdir=/PUP-boots/FATSlacko

# Skip save-session  Run from RAM
title FAT Slacko in RAM mode\nBoot up Puppy without pupsave
  root (hd0,0)
  kernel /PUP-boots/FATSlacko/vmlinuz pmedia=usbflash pfix=ram,fsck psubdir=/PUP-boots/FATSlacko
  initrd /PUP-boots/FATSlacko/initrd.gz

	o
	o
	o
	o
	o
	o
When this GRUB4DOS boot manager executes, it fails with "puppy_slacko_5.3.3x.sfs not found".
Yet, the sfs is in the proper folder on the HDD.

Should I move a copy of it to root ("/"), then, the system boots fine.

Questions if you know the answer to this phenomenon
  1. What is missed in the understanding of this?
  2. And what would you recommend to change in the menu.lst entry to instruct GRUB4DOS to find the sfs?
Thanks in advance
Last edited by gcmartin on Thu 28 Jun 2012, 00:34, edited 1 time in total.

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

#303 Post by shinobar »

gcmartin wrote:When this GRUB4DOS boot manager executes, it fails with "puppy_slacko_5.3.3x.sfs not found".
Yet, the sfs is in the proper folder on the HDD.
USB HDD, or Internal HDD?
'pmedia=usbflash' option may be wrong.
Most safe is to remove the pmedia option.
Or, try 'pmedia=atahd' or 'pmedia=ataflash'(for internal SSD).

I am not sure if the upper case for the directory name is a problem or not.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

gcmartin

#304 Post by gcmartin »

shinobar wrote:
gcmartin wrote:When this GRUB4DOS boot manager executes, it fails with "puppy_slacko_5.3.3x.sfs not found".
Yet, the sfs is in the proper folder on the HDD.
USB HDD, or Internal HDD?
'pmedia=usbflash' option may be wrong.
Most safe is to remove the pmedia option.
Or, try 'pmedia=atahd' or 'pmedia=ataflash'(for internal SSD).

I am not sure if the upper case for the directory name is a problem or not.
It a USB Flash that is partitioned with a SWAP partition as the 2nd 4GB partition on the 8GB stick.There is NO HDD on this PC, only the USB stick.

I will try your suggestion, tonight to see if that makes a difference. Also, if I remove the pmedia parm, should I expect a change in behavior. The 1st partition on the stick is formatted NTFS.

More information here that may help point to reasons of the error message.

Hope this helps

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

puppy_slacko_5.3.3x.sfs not found

#305 Post by shinobar »

gcmartin wrote:It a USB Flash that is partitioned with a SWAP partition as the 2nd 4GB partition on the 8GB stick.There is NO HDD on this PC, only the USB stick.
In that case, the menu.lst entry you showed seems quite right.
I suspect the slacko kernel cannot handle your usb.
For you information, the vminuz and the initrd.gz are load by the grub4dos via BIOS, but the main sfs is read by the kernel.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

Post Reply