Puppy Linux Windows Installer - LICK v1.3.3 released
I've attached 1.1 beta. Please test.
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
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
And I would like to Recommend the gfxmenu mesaage to you.
To edit it , you can see here:
http://diddy.boot-land.net/grub4dos/files/gfxmenu.htm
To edit it , you can see here:
http://diddy.boot-land.net/grub4dos/files/gfxmenu.htm
- Attachments
-
- back.jpg
- (9.31 KiB) Downloaded 3565 times
yes. i am going to translate it.
Code: Select all
!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} "在安装
Second Puppy - can't find the pup sfs
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.
Anything I need to do or change?
David S.
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.
Anything I need to do or change?
David S.
I just uploaded a pre-compiled Puppy Linux 520: http://db.tt/FJcXCZF
G'day noryb009,
My new Samsung laptop's Windows 7 C:\ menu.lst:
timeout=5
default=0
gfxmenu=/Grub_GUI.gz
title Wary Puppy 500
find --set-root --ignore-floppies /Wary-Puppy-500/initrd.gz
kernel /Wary-Puppy-500/vmlinuz psubdir="Wary-Puppy-500" pfix=fsck
initrd /Wary-Puppy-500/initrd.gz
boot
title Wary Puppy 500 - Do not load save file
find --set-root --ignore-floppies /Wary-Puppy-500/initrd.gz
kernel /Wary-Puppy-500/vmlinuz psubdir="Wary-Puppy-500" pfix=ram
initrd /Wary-Puppy-500/initrd.gz
boot
title Puppy 431
find --set-root --ignore-floppies /Puppy431/initrd.gz
kernel /Puppy431/vmlinuz psubdir="Puppy431" pfix=fsck
initrd /Puppy431/initrd.gz
boot
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.
Thank you for your assistance,
David S.
My new Samsung laptop's Windows 7 C:\ menu.lst:
timeout=5
default=0
gfxmenu=/Grub_GUI.gz
title Wary Puppy 500
find --set-root --ignore-floppies /Wary-Puppy-500/initrd.gz
kernel /Wary-Puppy-500/vmlinuz psubdir="Wary-Puppy-500" pfix=fsck
initrd /Wary-Puppy-500/initrd.gz
boot
title Wary Puppy 500 - Do not load save file
find --set-root --ignore-floppies /Wary-Puppy-500/initrd.gz
kernel /Wary-Puppy-500/vmlinuz psubdir="Wary-Puppy-500" pfix=ram
initrd /Wary-Puppy-500/initrd.gz
boot
title Puppy 431
find --set-root --ignore-floppies /Puppy431/initrd.gz
kernel /Puppy431/vmlinuz psubdir="Puppy431" pfix=fsck
initrd /Puppy431/initrd.gz
boot
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.
Thank you for your assistance,
David S.
Nice work! I had done this a while back with 4.3.1, but I am very pleased to see it here! Nice work on 520 and for making it easier for those Windows users...noryb009 wrote:I just uploaded a pre-compiled Puppy Linux 520: http://db.tt/FJcXCZF
hi, noryb009,
I fixed the code sucess use iso file don't need add in the soft.
I hope you can see this as soon as possible.
And at .oninit
I fixed the code sucess use iso file don't need add in the soft.
I hope you can see this as soon as possible.
Code: Select all
Function UnzipPuppy
# SetOutPath "$INSTDIR"
# SetOverwrite ifnewer
# File "${PLICDIR}${PUPPY_SFS}"
# File "${PLICDIR}vmlinuz"
# File "${PLICDIR}initrd.gz"
InitPluginsDir
File /oname=$PLUGINSDIR\7zG.exe "7zG.exe"
File /oname=$PLUGINSDIR\7z.dll "7z.dll"
${If} ${FileExists} "$EXEDIR\puppy520.iso"
ExecWait '"$PLUGINSDIR\7zG.exe" x "$EXEDIR\puppy520.iso" -o"C:\${INSTALL_DIR}" -y -x![BOOT]*'
${EndIf}
SetOutPath "$INSTDIR"
SetOverwrite ifnewer
call in
FunctionEnd
And at .oninit
Code: Select all
IfFileExists "$EXEDIR\puppy_520.iso" found
MessageBox MB_YESNO "you must have a puppy520.iso file in the same directry, now i had check that you have not got it, continue?" IDYES NoCancelAbort
Abort
NoCancelAbort:
found:
Code: Select all
Function un.deleteFiles
# Delete "$INSTDIR\uninst.exe"
# Delete "$INSTDIR\${PUPPY_SFS}"
# Delete "$INSTDIR\readme.txt"
# Delete "$INSTDIR\initrd.gz"
# Delete "$INSTDIR\vmlinuz"
Delete "$INSTDIR\*.*"
RMDir "$INSTDIR"
Call un.uninstall
FunctionEnd