Page 17 of 20
Re: alphaOS support
Posted: Mon 04 Nov 2013, 04:17
by gcmartin
shinobar wrote:simargl5 wrote: ... This is list of files in frugal installation- top directory of sda6 partition
Code: Select all
alphaos
alphaos/alpha_12.sb
alphaos/changes.fs4
alphaos/extra_12.sb
alphaos/boot
alphaos/boot/vmlinuz
alphaos/boot/initrfs.img
alphaos/modules
....
1. Current grub4dosconfig does not find 'initrfs.img'.
2. Current grub4dosconfig does not search deeper 'boot' directory.
If you want to hack, find the code for Wubi and slitaz in the script. They can be a help.
BTW, most recent alphaOS_12.1-20121019.iso has these files:
Code: Select all
alpha_12.sfs
boot.cat
extra_12.sfs
initrd.gz
isolinux.bin
syslinux.cfg
vmlinuz
These can be found by the current grub4dosconfig when they are frugal installed in a sub-directory. The grub4dosconfig doesn't know what is the alphaOS, and takes 'Extra-12' for the title.
Shinobar, are you sharing that grub4dos will NOT search 3 levels deep for the kernel-init needs or are you sharing that all things need be in a single directory?
Trying to understand which.
Thanks in advance.
Posted: Mon 04 Nov 2013, 08:58
by simargl5
Edit: Ignore this post
I've fixed (partially) grub4dosconfig to recognize alphaos frugal installation (based on linux live)
file:
http://alphaos.tuxfamily.org/forum/down ... .php?id=44
diffs:
Code: Select all
@@ -252,6 +252,7 @@
io.sys) DISTRO_NAME="Windows 9x/Me";;
plpbt.bin) DISTRO_NAME="PLOP_boot_manager";;
rootfs*.gz) DISTRO_NAME="Slitaz Linux";;
+ initrfs.img) DISTRO_NAME="alphaOS";;
initrd) DISTRO_NAME="Fatdog64";;
puppy.sfs) # frugal installed Puppy with simple file name
DISTRO_IDSTRING=$(tail -c 16 $TOPDIR$KEYFILE)
@@ -290,7 +291,7 @@
[ -f $TOPDIR/etc/DISTRO_SPECS ] && source $TOPDIR/etc/DISTRO_SPECS
[ "$DISTRO_VERSION" != "" ] && DISTRO_NAME="$DISTRO_NAME $DISTRO_VERSION"
[ "$DISTRO_NAME" ] && echo "$DISTRO_NAME" && return
-
+
# other linux
if [ "$DISTRO_NAME" = "" ]; then
if [ -f $TOPDIR/etc/vine-release ] ; then
@@ -972,6 +973,18 @@
fi
break
done
+
+ # alphaos
+ for D in alphaos alphaOS Alphaos AlphaOS alphaos.usb alphaos-usb; do
+ if [ -f $TOPDIR/$D/boot/vmlinuz -a -f $TOPDIR/$D/alpha*sb ];then
+ LINUXOPTIONS="$LINUXOPTIONS from=/$D"
+ KEYFILE="/$D/boot/initrfs.img,/$D/boot/vmlinuz"
+ ITEM="$PART$KEYFILE|$(read_distro_specs $TOPDIR)"
+ FULLINSTS="$FULLINSTS
+ $ITEM"
+ fi
+ done
+
# Wubi
if [ -f $TOPDIR/ubuntu/disks/boot/grub/menu.lst ];then # ununtu on Windows
KEYFILE=/ubuntu/disks/boot/grub/menu.lst
problem: in case two frugal installation are on the same disk, in will add from=/dir1 from=/dir2 for both entries...
Posted: Mon 04 Nov 2013, 16:43
by simargl5
shinobar, do you consider this as a bug - fact that Grub4DosConfig is not being able to find alphaos frugal installation, and not just alphaos, it also can't boot Slax, one of distributions with highest reputation and long tradition. If yes what's status of that bug: need more info, wontfix, pending...
Posted: Wed 06 Nov 2013, 22:00
by simargl5
I mark this bug as SOLVED
... not upstream, but doesn't matter - will use my patch.
enhancment request
Posted: Fri 08 Nov 2013, 10:36
by gyro
Many current puppies , (at least the ones I have installed) support frugal installs down 2 directories, as per the following menu.lst entry:
Code: Select all
title squeeze 5.X.3.4.12
uuid 160b47eb-a8de-4fa1-ac7e-8f795e7bbe8d
kernel /puppy/squeeze/vmlinuz psubdir=puppy/squeeze pmedia=atahd pfix=fsck
initrd /puppy/squeeze/initrd.gz
Will Grub4DosConfig's search facility ever be changed so that it will find these?
gyro
Posted: Mon 06 Jan 2014, 19:57
by EdD
nooby wrote:Oops sorry. maybe the name is EasyBCD and NeoGrub is the name of a program within the EBCD program.
nooby, thanks for the link. just found this old thread in my quest to learn about grub and the page you linked has a good tutorial on syntax, which is what was suggested to me earlier by mikeb.
Regards,
Ed
Posted: Tue 11 Feb 2014, 00:00
by 01micko
Hello shinobar,
If you are interested, woof-CE has deprecated the 'mini-icons' in favour of svg icons. This breaks the images in the grub4dos-config gui. We have also deprecated the 24 icons in the icon-themes. I have made a patch which should be backward compatible against v1.9.1
Code: Select all
diff -ru a/usr/sbin/grub4dosconfig b/usr/sbin/grub4dosconfig
--- a/usr/sbin/grub4dosconfig 2014-01-08 00:29:03.000000000 +1000
+++ b/usr/sbin/grub4dosconfig 2014-02-11 09:58:27.713443548 +1000
@@ -192,6 +192,9 @@
which $PROG >/dev/null && HELPVIEWER=$PROG && break
done
ICONS="/usr/local/lib/X11/mini-icons"
+icon=mini-clock.xpm
+width=
+[ -d /usr/share/pixmaps/puppy ] && ICONS="/usr/share/pixmaps/puppy" icon=clock.svg width="<width>16</width>"
splash() {
ACTION="$1"
@@ -199,7 +202,7 @@
if [ "$ACTION" = "start" ]
then
DIALOG="<window title=\"$_Title\"><hbox>
- <pixmap><input file>$ICONS/mini-clock.xpm</input></pixmap>
+ <pixmap><input file>$ICONS/$icon</input>$width</pixmap>
<text><input>echo -en \"$MSG\"</input></text>
</hbox></window>"
$GTKDIALOG -p DIALOG -c &>/dev/null &
@@ -2042,7 +2045,7 @@
<text><label>$_Unmount</label></text>"
fi
[ "$FLOPPY" != "" ] && mount /dev/fd0 /mnt/fd0
- EDITADVANCED="<button><input file>/usr/local/lib/X11/pixmaps/edit24.png</input>
+ EDITADVANCED="<button><input file stock=\"gtk-edit\"></input>
<label>\"$_Edit_Advanced\"</label><action>defaulttexteditor $TOPDIR$ADVANCEDMENU &</action></button>"
[ "$ONEPAGE_MENU" = 'true' ] && EDITADVANCED=""
DIALOG="<window title=\"$_Title - Success\"><vbox>
@@ -2050,10 +2053,10 @@
<text use-markup=\"true\"><label>\"$_Success $_Fairwell1 $FILES $_Fairwell2 <b>$TOPDIR</b>. $_Fairwell3\"</label></text>
$MORE
<hbox>
- <button><input file>/usr/local/lib/X11/pixmaps/edit24.png</input>
+ <button><input file stock=\"gtk-edit\"></input>
<label>\"$_Edit\"</label><action>defaulttexteditor $TOPDIR/menu.lst &</action></button>
$EDITADVANCED
- <button><input file>/usr/local/lib/X11/pixmaps/file24.png</input><label>$(gettext 'See log')</label>
+ <button><input file stock=\"gtk-file\"></input><label>$(gettext 'See log')</label>
<action>defaulttextviewer $MYLOG &</action></button>
</hbox>
<hbox>
Posted: Tue 11 Feb 2014, 08:24
by gcmartin
Hi @Shinobar
This was posted about GRUB4DOS.
Has there been any changes in BIOS support?
Posted: Tue 11 Feb 2014, 21:48
by bigpup
version 1.9.1 'unknown' entries
Posted: Thu 08 May 2014, 12:29
by step
I installed and ran version 1.9.1 on Quirky Tahr 6.0.5. It found the exact NUMBER of frugal installs on my hhd but all menu.lst entries where labelled 'unknown' and resolved to /vmlinuz initrd=/initrd.gz.
I then uninstalled version 1.9.1 and installed version 1.8.0. It found the exact number of installs and built a complete, correct menu.lst file.
So there seems to be a problem in the way 1.9.1 builds menu.lst.
menu.lst the good one
(
the bad one looks the same but all entries are:
title unknown (sdb1)
kernel /vmlinuz
initrd /initrd.gz
)
Code: Select all
# menu.lst produced by grub4dosconfig-v1.8.0
color blue/cyan yellow/blue white/black cyan/black
#splashimage=/splash.xpm
timeout 10
default 0
# Frugal installed Puppy
title Flp 013 (sdb1/fluppy)
uuid 9f5d11ff-714b-48b1-860c-84924f0e9ece
kernel /fluppy/vmlinuz psubdir=fluppy pmedia=atahd pfix=fsck
initrd /fluppy/initrd.gz
title Puppy carolite 1.2 (sdb1/puppy-carolite)
uuid 9f5d11ff-714b-48b1-860c-84924f0e9ece
kernel /puppy-carolite/vmlinuz psubdir=puppy-carolite pmedia=atahd pfix=fsck
initrd /puppy-carolite/initrd.gz
title Saluki printer scanner 001 (sdb1/puppy)
uuid 9f5d11ff-714b-48b1-860c-84924f0e9ece
kernel /puppy/vmlinuz psubdir=puppy pmedia=atahd pfix=fsck
initrd /puppy/initrd.gz
title Puppy lina 1.1 (sdb1/puppy-lina)
uuid 9f5d11ff-714b-48b1-860c-84924f0e9ece
kernel /puppy-lina/vmlinuz psubdir=puppy-lina pmedia=atahd pfix=fsck
initrd /puppy-lina/initrd.gz
title Puppy lxpup 13.10 (sdb1/puppy-lxpup1310)
uuid 9f5d11ff-714b-48b1-860c-84924f0e9ece
kernel /puppy-lxpup1310/vmlinuz psubdir=puppy-lxpup1310 pmedia=atahd pfix=fsck
initrd /puppy-lxpup1310/initrd.gz
title Puppy lxpup 13.04 (sdb1/puppy-lxpup13)
uuid 9f5d11ff-714b-48b1-860c-84924f0e9ece
kernel /puppy-lxpup13/vmlinuz psubdir=puppy-lxpup13 pmedia=atahd pfix=fsck
initrd /puppy-lxpup13/initrd.gz
title Puppy lxpup 12.12 (sdb1/puppy-lxpup)
uuid 9f5d11ff-714b-48b1-860c-84924f0e9ece
kernel /puppy-lxpup/vmlinuz psubdir=puppy-lxpup pmedia=atahd pfix=fsck
initrd /puppy-lxpup/initrd.gz
title Xfce 4.10 (sdb1/puppy-precise)
uuid 9f5d11ff-714b-48b1-860c-84924f0e9ece
kernel /puppy-precise/vmlinuz psubdir=puppy-precise pmedia=atahd pfix=fsck
initrd /puppy-precise/initrd.gz
title Saluki printer scanner 001 (sdb1/puppy-saluki)
uuid 9f5d11ff-714b-48b1-860c-84924f0e9ece
kernel /puppy-saluki/vmlinuz psubdir=puppy-saluki pmedia=atahd pfix=fsck
initrd /puppy-saluki/initrd.gz
title Puppy xprecise 5.7.1 (sdb1/puppy-X-precise)
uuid 9f5d11ff-714b-48b1-860c-84924f0e9ece
kernel /puppy-X-precise/vmlinuz psubdir=puppy-X-precise pmedia=atahd pfix=fsck
initrd /puppy-X-precise/initrd.gz
# Full installed Linux
title Linux Mint 13 Maya (sdb1)
uuid 9f5d11ff-714b-48b1-860c-84924f0e9ece
kernel /vmlinuz root=/dev/sdb1 ro
initrd /initrd.img
title Linux (sdc1)
uuid A8EE-83EE
kernel /vmlinuz root=/dev/sdc1 ro
# Windows
title Windows
map (hd3) (hd0)
map (hd0) (hd3)
map --hook
uuid 9f5d11ff-714b-48b1-860c-84924f0e9ece
chainloader /bootmgr
# Advanced Menu
title Advanced menu
configfile /menu-advanced.lst
commandline
menu.lst and MBR saved to /dev/sdd1 USB key.
Code: Select all
# blkid
/dev/sdd1: LABEL="PUP" UUID="9024-4D2D" TYPE="vfat"
/dev/mmcblk0p1: LABEL="RDYBST " UUID="E806B96D0C36BE46" TYPE="ntfs"
/dev/sdc1: LABEL="ZIP16" UUID="A8EE-83EE" TYPE="vfat"
/dev/sdb5: UUID="81b9917a-974c-4c8e-8740-e91411253526" TYPE="swap"
/dev/sdb3: LABEL="DATA" UUID="08557d54-76ce-490c-9615-c47f2378b6c9" TYPE="ext3"
/dev/sdb2: LABEL="WIN" UUID="1CAA7CBBAA7C92CE" TYPE="ntfs"
/dev/sdb1: LABEL="LINUX" UUID="9f5d11ff-714b-48b1-860c-84924f0e9ece" TYPE="ext4"
/dev/sda8: LABEL="BOOT" UUID="1676-EF88" TYPE="vfat"
/dev/sda7: LABEL="SWAP" UUID="9cf61a01-225c-4313-8e3e-488ac04d0b16" TYPE="swap"
/dev/sda6: LABEL="WIN" UUID="25DAB16455F2E4C2" TYPE="ntfs"
/dev/sda5: LABEL="LINUX" UUID="4dc99106-5b4d-47d2-b04b-7031455e1cd8" TYPE="f2fs"
/dev/sda1: TYPE="vfat"
version 1.9.1 'unknown' entries
Posted: Thu 08 May 2014, 12:31
by step
(double post deleted)
Posted: Tue 01 Jul 2014, 19:28
by gcmartin
@Shinobar
As I know you offer Precise in 2 versions; one of which is Precise-571JP, I offer this idea for booting into the 2 languages you currently support.
Open the attached file in a text editor AS IS!
Hope this helps
grub4dos-0.4.4.v1.9.2
Posted: Sun 20 Jul 2014, 10:36
by shinobar
UPDATE:
grub4dos-0.4.4.v1.9.2.pet (2014-07-20)
http://shino.pos.to/linux/puppy/
#20Jul14 v1.9.2: grub2, titles, bootable mbr detection
Posted: Sat 16 Aug 2014, 19:14
by don570
I installed the newest version.
A full install of Quirky tahr by Barry Kauler . The result --->
I include the terminal output if you're interested.
It did work with
Tahrpup and Racy distros.
____________________________________________________
I have a suggestion:
I have a lot of frugal installations so the list of operating systems
available is very long and I can't see the OK button at the end of the list.
I have to use alt key. So I suggest putting the OK button at the top or side of window.
____________________________________________
Too many Frugals here too
Posted: Sun 17 Aug 2014, 00:22
by davids45
G'day shinobar,
I was about to go searching this thread but don570 has exactly my problem.
I was trying to rescue an old hard drive, which had more than 20 Frugal Puppies plus about ten Puppy Fulls. I was removing old Windows & Ubuntu partitions through which the hard drive had been booting.
I installed a new Pup to sda1 but when I tried to set up Grub4Dos, the Puppy list (box) went off the bottom of the screen and I could not 'Move' or 'Resize' the box to see the 'OK' button.
A scroll bar for the listing would be good so all the possible Puppies could be seen, but if that is too difficult or time-consuming, I too would appreciate the 'OK' button at the top of the dialog box.
Thanks & regards,
David S.
Computer won't boot Puppy Linux.
Posted: Thu 18 Sep 2014, 15:20
by sheldonisaac
Someone could use help with a computer that does not boot Puppy Linux.
Please see
http://murga-linux.com/puppy/viewtopic.php?t=95728
Thank you,
Sheldon
Posted: Tue 18 Nov 2014, 02:03
by bigpup
Running Tahrpup 6.0 CE
Puppy Universal Installer to do a frugal install on a hard drive.
When you get to the point of naming the install location.
It gives as an example "puppyfiles/pup6.0" for a name to use for location of the frugal install.
If you use that name.
Grub4dos config(v1.9.2) does not recognize that name as a Puppy install location.
No entry will be made in the menu.lst for that frugal install.
If you use the default location name "tahr6.0frugal".
Grub4dos config finds it and puts entry in menu.lst
One not working is two directories deep, if that has anything to do with it.
Posted: Wed 11 Feb 2015, 17:47
by bigpup
Tahrpup 6.0.2
Full install to hard drive
V1.9.2
Grub4dos Bootloader config is not able to make a tittle entry for Puppies as frugal installs.
From my latest menu.lst.
Code: Select all
# menu.lst produced by grub4dosconfig-v1.9.2
color white/blue black/cyan white/black cyan/black
#splashimage=/splash.xpm
timeout 10
default 0
# Frugal installed Puppy
title Unknown ()
uuid 60a52c2e-48d5-47a5-9f9d-8a312996d1f6
kernel /vmlinuz pmedia=atahd pfix=fsck
initrd /initrd.gz
title Unknown (sda5)
uuid 00aa0274-75d7-402d-ab7c-4e0f2d973e6a
kernel /vmlinuz pmedia=atahd pfix=fsck
initrd /initrd.gz
title Unknown (sda5)
uuid 00aa0274-75d7-402d-ab7c-4e0f2d973e6a
kernel /vmlinuz pmedia=atahd pfix=fsck
initrd /initrd.gz
title Unknown (sdb1)
find --set-root --ignore-floppies --ignore-cd /tahr64_6.0.2/
kernel /vmlinuz pmedia=usbflash pfix=fsck
initrd /initrd.gz
# Full installed Linux
title Linux (sda2)
uuid 60a52c2e-48d5-47a5-9f9d-8a312996d1f6
kernel /vmlinuz root=/dev/sda2 ro
initrd /initrd.gz
title Tahrpup 6.0.1 (sda3/boot)
uuid add3bbc4-3d00-442f-8792-b8b1e12ba6a2
kernel /boot/vmlinuz root=/dev/sda3 ro
title Slacko Puppy 5.7.0 (sda7/boot)
uuid 2a7dc791-ef27-4a70-ae9e-f59d14bdfa18
kernel /boot/vmlinuz root=/dev/sda7 ro
# Windows
# this entry searches Windows on the HDD and boot it up
title Windows\nBoot up Windows if installed
errorcheck off
find --set-root --ignore-floppies --ignore-cd /bootmgr
chainloader /bootmgr
find --set-root --ignore-floppies --ignore-cd /ntldr
chainloader /ntldr
find --set-root --ignore-floppies --ignore-cd /io.sys
chainloader /io.sys
errorcheck on
# Advanced Menu
title Advanced menu
configfile /menu-advanced.lst
commandline
Posted: Sun 08 Mar 2015, 14:27
by slavvo67
IF the MBR is already toast on a PC but I can still boot Puppy through CD, is there any downside in trying to install Grub4Dos on that computer?
Posted: Sun 08 Mar 2015, 15:44
by bigpup
It should work OK unless there is something physically wrong with the mbr section of the hard drive.
Grub4dos does give you options for locations to place it on the hard drive other than the mbr.
I usually always install it to the mbr with no problem.