Grub4DosConfig

[shinobar]

UPDATE: grub4dos-0.4.4.v1.7.2.pet

v1.7.2: fix was mmc card(ex. mmcblk0p1) failed(thanks to jemimah), which vmlinuz and initrd should be taken(thanks to Karl)

[don570]

I used pemasu's exprimo which has the Enlightenment WM


It seems to have a bug when scripts don't finish nicely with 0

so when I close grub4dos I get this....


It's a common bug. It usually can be solved by putting a zero
after exit. So for example I did the following

line 623 of usr/sbin/grub4dosconfig
change

Code: Select all

[ "$EXIT" = "OK" ] || exit

to

Code: Select all

[ "$EXIT" = "OK" ] || exit 0

[shinobar]

Test release: grub4dos-0.4.4.v1.7.9.pet (2012-04-30)
http://shino.pos.to/linux/puppy/
# 28apr12 v1.7.9: improved detecting special puppies like LHP, advanced menu, old menus, legacy grub compatible menu, splash image, text domain, exit status (thanks to don)
Document
This release is not bugfix, but improved and has new features. Welcome your feedback.

Highlight of the new features:

1. Pupplet detection
   Detects LazY Puppy, LightHousePup, was not auto-detected.
2. Advanced menu
   Advanced menu is shown behind the top menu, at the second page.
3. Old menus
   The grub4dosconfig makes back up the existing old menus. You can go back with choosing the "Previous menu" in the 'Advanced menu'.
4. Splash image
   You can make background image behind the bootup menu. The image will need to be in the .xpm format and must be 640x480 pixels with a maximum of 14 colours. Place the image file with name 'splash.xpm' at the same place of the 'menu.lst' file. You can make your original splash image by using the mtpaint or the gimp. (Grub4dos Guide - Creating a Splash Image)
   EDIT: You need to comment out the 'color' line both from menu.lst and menu-advanced.lst if you use the splash image.

   # menu.lst produced by grub4dosconfig-v1.7.9
   #color white/blue black/cyan white/black cyan/black
   splashimage=/splash.xpm

5. Legacy grub compatible
   you can take the "Legacy compatible 'menu.lst'" option. Then the grub4dosconfig avoids grub4dos specific commands. Note that this option is only for ones who want and can manage it.

[Pete22]

It now will recognize lhp!!!! That really makes my day.

Trying it out I noticed a few possible bugs.

If I select the advanced menu, it highlights everything instead of one line.
If I go back to main menu, it will still have all the lines highlighted.


Is that how you meant for the new version to work?

I also noticed it did not see Legacy puppy.


Pete

[shinobar]

If I select the advanced menu, it highlights everything instead of one line.
If I go back to main menu, it will still have all the lines highlighted.

Yeh, i realized the problem with using splash image.
Comment out the 'color' line both from menu.lst and menu-advanced.lst if you use the splash image.

# menu.lst produced by grub4dosconfig-v1.7.9
#color white/blue black/cyan white/black cyan/black
splashimage=/splash.xpm

I also noticed it did not see Legacy puppy.

Which puppy do you mean?

[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

[shinobar]

# 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

The puppy that grub4dos does not find is Legacy os4.

Where is the pup_421.sfs?

[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.




__________________________________________

[shinobar]

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.

[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

[shinobar]

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?

[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 produced by grub4dosconfig-v1.7.9
#color white/blue black/cyan white/black cyan/black
splashimage=/splash.xpm

[Pete22]

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

Yes that fixes that problem.

Thanks for your persistence in helping me SEE it.


This is a great program.

Pete

[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]

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

[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.

______________________________________________

[shinobar]

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.

[shinobar]

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.

[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

______________________________________________

[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.