Puppy Linux Discussion Forum

[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

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

[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

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

[noryb009]

Wow - the gfxmenu is awesome! Thank you so much! I'll add it to 1.1.

[teasiu]

Good!

It works!

on win7 32bit.

[noryb009]

Puppy Linux Windows Installer V1.1 is attached to the first post.

[teasiu]

noryb009,

other idea:

1、if the MUI_FINISHPAGE_TEXT had told people reboot and where can uninstall, The "readme.txt" do not have to [Filewrite]. how about change to use [Filecopy]. Copy a new readme.txt to [INSTALL_DIR] what is the Puppyusage incloud inside.

2、This is the great installer release , so how about to make it "Universal-windows-Installer"? Because people is hard to download another 100M *.exe file. We can let the installer auto unzip by selectISOfile which had downloaded before.
example:

[noryb009]

teasiu: That's one of the things I'm going to add.

Are you still able to translate it to chinese?

[teasiu]

yes. i am going to translate it.

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

[noryb009]

1) Could you post your menu.lst? Just the 431 part, please.

2) What are all the files in C:\puppy431 ?

[noryb009]

I just uploaded a pre-compiled Puppy Linux 520: http://db.tt/FJcXCZF

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

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