It would seem from the comment file here: http://nufans.net/grub4dos/tinybit
that the existing grub4dos updates are development versions.
If tinybit is involved then I guess we have a mainstream development and not a fork - tinybit created grub4dos originally before bean got involved when Ubuntu wubi was being developed.
Thanks for the links and your input to the Puppy community. I will now be following both with interest.
Please reply if you test it on 32 bit vista/7 or 9x, or if it doesn't work.
Fixes:
- windows vista/7 64 bit support
- added pfix=fsck to default boot option
- added "do not load save file" option in GRUB4DOS menu
- organized code
- you can now unzip this to anywhere (It must be a windows drive, so you can't use /root/, unless you mount it in wine)
- customized installer
!insertmacro MUI_LANGUAGE "English" ; first language is the default language
!insertmacro MUI_LANGUAGE "SimpChinese"
LangString License_Subtitle ${LANG_ENGLISH} "Please review the license terms before proceeding"
LangString License_Subtitle ${LANG_SIMPCHINESE} "在安装
G'day,
I have a new Samsung laptop running 64-bit Windows 7 to which I have successfully added Wary-500 using the Windows 1.1 installer. Very impressive package and presentation.
Having read an earlier post to this thread saying I could add a second Puppy, I prepared a Puppy-4.3.1.exe and installed that. I did nothing to the existing Wary install.
The new menu for the Puppies was fine with new lines added, and displayed when booting, but the booting of the second Puppy (4.3.1) failed with the "pup-431.sfs not found" message. I tried running 4.3.1 with and without loading a save file options.
The puppy431 directory is in C:\ and has the files I expected to see in it, including the "not-found" pup-431.sfs.
The first installed Puppy (Wary-500) still boots up and runs perfectly.
title Puppy 431 - Do not load save file
find --set-root --ignore-floppies /Puppy431/initrd.gz
kernel /Puppy431/vmlinuz psubdir="Puppy431" pfix=ram
initrd /Puppy431/initrd.gz
boot
The directory Puppy431 in C: contains:
initrd.gz
pup-431.sfs
readme.txt
uninst.exe
vmlinuz
zp430305.sfs
The second sfs file shows that the installer has added the extra .sfs file successfully, as part of the creation of the Puppy 431 .exe.
I did first try a manual adding of another Pup (4.3.0) by copying the three files into a new directory on C:\ and manually editing the original menu.lst file. The manual entry showed up on the boot options menu list but when I selected this and hit <Enter>, I got the "pup-430.sfs not found" message.
I then deleted my manual additions to the menu list and the manual directory on C:\. So I then used the Installer 1.1 to prepare the second Puppy .exe (this time Puppy 4.3.1) as I had assumed I had made a mistake in the manual entry when I tried to add the extra Pup to Windows 7.
I think GRUB is case sensitive. You called the folder "Puppy431", but in your first post you called it "puppy431". Fix that if menu.lst and try it again.