Page 3 of 30
Posted: Thu 20 Jan 2011, 20:38
by teasiu
noryb009 wrote:Hi teasiu!
Because gfxmenu is only at the top, you only need it once (Therefore, you don't need any extra code in the uninstall menu).
Hi Noryb,
I am learnning the NSI script these days, and may a nice look in the installer welcomepage.
Code: Select all
!define MUI_ICON "C:\Puppy Linux Installer Creator\Puppy Linux Install.ico"
!define MUI_UNICON "C:\Puppy Linux Installer Creator\Puppy Linux Uninstall.ico"
#!define MUI_ICON "${NSISDIR}\Contrib\Graphics\Icons\modern-install.ico"
#!define MUI_UNICON "${NSISDIR}\Contrib\Graphics\Icons\modern-uninstall.ico"
!define MUI_WELCOMEFINISHPAGE_BITMAP "C:\Puppy Linux Installer Creator\ppp.bmp"
!define MUI_WELCOMEPAGE_TITLE "\r\n XXXXXXXXXXXXXX"
!define MUI_WELCOMEPAGE_TEXT "\r\n 1
Posted: Fri 21 Jan 2011, 12:59
by ICPUG
teasiu,
Thanks for the additional info.
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.
Posted: Sun 23 Jan 2011, 13:04
by noryb009
teasiu: Thank you so much! You've given me ideas, and helped me get back into this project!
Anyways, I'll be uploading 1.1 later today. It will fix windows vista/7 64-bit, and have better organized code.
Posted: Sun 23 Jan 2011, 15:00
by teasiu
noryb009 wrote:teasiu: Thank you so much! You've given me ideas, and helped me get back into this project!
Anyways, I'll be uploading 1.1 later today. It will fix windows vista/7 64-bit, and have better organized code.
wait for your good CODE.
By the way , I will translate your codes in SimpChinese and push it online.
Posted: Sun 23 Jan 2011, 18:47
by amigo
My understanding is that chenall is the current maintainer. bean is busy working on wee -and even more 'burg'
Posted: Mon 24 Jan 2011, 03:34
by noryb009
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
Posted: Mon 24 Jan 2011, 10:06
by teasiu
Hi, noryb009
I build it on Nullsoft install system v2.45 on win7-32,
building is ok , but the Installer doesn't work,
It stop on halfway.
Posted: Mon 24 Jan 2011, 11:28
by teasiu
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
Posted: Mon 24 Jan 2011, 21:49
by noryb009
teasiu: Thanks for testing, it seems my 64 bit fix broke the 32 bit. I've fixed it in 1.1 beta 2 (attached)
I'll look into gfxmenu for 1.2 (maybe 1.1)
Posted: Mon 24 Jan 2011, 22:25
by noryb009
Wow - the gfxmenu is awesome! Thank you so much! I'll add it to 1.1.
Posted: Tue 25 Jan 2011, 08:36
by teasiu
Good!
It works!
on win7 32bit.
Posted: Wed 26 Jan 2011, 03:23
by noryb009
Puppy Linux Windows Installer V1.1 is attached to the first post.
Posted: Wed 26 Jan 2011, 09:34
by teasiu
noryb009,
other idea:
1
Posted: Wed 26 Jan 2011, 12:10
by noryb009
teasiu: That's one of the things I'm going to add.
Are you still able to translate it to chinese?
Posted: Wed 26 Jan 2011, 13:54
by teasiu
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
Posted: Sun 06 Feb 2011, 11:14
by davids45
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.
Posted: Sun 06 Feb 2011, 12:22
by noryb009
1) Could you post your menu.lst? Just the 431 part, please.
2) What are all the files in C:\puppy431 ?
Posted: Sun 06 Feb 2011, 14:25
by noryb009
I just uploaded a pre-compiled Puppy Linux 520:
http://db.tt/FJcXCZF
Posted: Mon 07 Feb 2011, 06:19
by davids45
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.
Posted: Tue 08 Feb 2011, 01:40
by noryb009
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.