(old)Puppy Linux Discussion Forum

Thank you shinobar for the extra info.

I finally got the bcedit manual (original version, not the latest) in pdf form. A quick look did not help me to understand when 'device boot' was needed. Your info did!

This little extra 100M partition is a bit of a nuisance. I knew about it before and I also know it can be avoided if you install Windows 7 very carefully. Even though I used a dedicated computer retailer I find my machine has this little extra partition. Apart from wasting one of the 4 allowed primary partitions I hope that somewhere there is some info I can find which explains in detail the Win 7 boot process and what the purpose of this little extra partition is.

ICPUG: I think it's so that people can't delete the boot loader, so it's easier to repair if people start deleting everything.

Thanks noryb.

I have been doing some more searching and apparently the small partition incorporates the Windows Recovery Environment. If Windows 7 does not boot properly a flag does not get reset. Next time you boot the flag is detected and you are booted into that small partition.

Since, with Windows XP, one needed an install disk to get the recovery environment, which lots of PCs didn't have, this small partition is an improvement!

If you install Windows 7 in a set way this environment will be placed in a folder on the main partition instead of creating a separate partition.

The small partition may also be used for bitlocker encryption but as I don't have an enterprise edition Windows 7 that is not something I am going to investigate!

A success report from bodbozzle of the Lucid-Puppy-Quickset-511-installer.exe with Windows Xp.
http://www.murga-linux.com/puppy/viewto ... 9&start=53

lupu Quickset is a treat which revived my old laptop with no international keyboard setting hassles (the reason why I gave up lupu 511)! You made me an happy environment friendly pc user! Anyway, I tried the installer on WinME but unfortunately it didn't work.
Best regards and I'll keep in touch!
Olga Ritmo

I just looked it up, and while it runs the same way as 9x, Microsoft removed the boot loader to save a few seconds on startup. This makes it almost impossible to have GRUB installed without editing the MBR, which means I will have to not support Windows ME.

noryb009 wrote:I will have to not support Windows ME.

Thanks olgaritmo and noryb. Important information.
Found Wubi also does not support Windows ME.
https://wiki.ubuntu.com/WubiGuide#Unsupported set-ups
Unetbootin ... Ah, does not support any of Windows 9x/Me.
http://unetbootin.sourceforge.net/

Thank you noryb009,

short success-story; I used the method to make an exe installer from an 580 MB pupplet. I tested it successfully now on a XP and a Windows 7 machine.

Technically I had no problem, but I had to resize peronal storage file 2 times, because everything runs in folder /root/.wine (and you need place for puppy-sfs AND exe file)

is there any possibility to use another directory for the build process (i.e on out of the personal storage file).

Second (small) problem I had when I did "Test Installer" after the creation Process. I had Grub installed before, but this was wiped and afterwards I could only boot to XP (couldn't see my Linux partitions anymore). Luckily I had stored some Puppy iso files on my Windows Partition, so I could revive my computer via USB install. So maybe my example should be a WARNING to others.

cheers and thanks!
emil

emil: Thanks a lot for helping test.

is there any possibility to use another directory for the build process (i.e on out of the personal storage file).

I'll test a symlink to a hard drive. Thanks for the suggestion!

Second (small) problem I had when I did "Test Installer" after the creation Process. I had Grub installed before, but this was wiped and afterwards I could only boot to XP (couldn't see my Linux partitions anymore). Luckily I had stored some Puppy iso files on my Windows Partition, so I could revive my computer via USB install. So maybe my example should be a WARNING to others.

I'm not sure what happened. Did you run the installer in Puppy? It should have just crashed and burned. Do you have GRUB installed to the MBR?

I am also not sure what happend, the exe was created successfully.
But then I think I ran the installer in Puppy with wine still installed (or did I just press the "Test Installer" Button, I cant remember).

I had old grub (not grub4dos) installed on the machine and various puppies and also an old Windows XP install in the menu. My plan was to reboot, then start up Winows XP, and run the installer to test it. But it never entered Grub menu, it went directly to XP (first in sort of recovery mode).

So I reccomend: don't run the exe from inside puppy when you have wine installed and dont press the "Test installer" button of the nsis exe creator programm, until this is resolved.

I still have to reinstall GRUB and get my old boot options back , but no problem.

noryb09 - i think this is the easiest possibility to get puppy running on a computer (most have windows installed), in fact its much easier than burning CD's and messing with USB sticks. Big cudoz for this technique - BIG achievment !!! I think everybody can download a file and click on it!

emil

Will there be a problem if the installer runs on a 64 Bit Windows machine?

It should work with 64 bit, I don't see any reason why it wouldn't.

Ok, I'll just add that to the main post.

Thanks a lot!

Hello, may I just ask a quick question:

I am not sure if I got it right how it works:

It checks windows/bottloader version

if xp: it changes the boot.ini
if Vista or Windows 7: it uses bcdedit to change the boot entry (like explained above)
if 9x: I dont know
if an existing grub is found: it stops and asks you to edit the menu.lst manually

then it installs grub4dos, but after the windows bootloader, so you can have 2 menus consecutive bootmenus (1.st on from windows, 2nd one from grub)

it WILL NOT change the mbr!

is this roughly right (especially the part about not changing the mbr)? Sorry about my sloppy terminology.

emil

PS; just for the reccord, while googling yesterday I found EassyBCD which is a free windows gui for editing the boot entries.
http://neosmart.net/dl.php?id=1

That's roughly right. It DOES NOT change the MBR.

if 9x: I dont know

It does something with the config.sys or something, or only got it working because of Lin'n'Win.

if an existing grub is found: it stops and asks you to edit the menu.lst manually

Not exactly, it automaticly adds the entry to the bootloader.

I saw EasyBCD before, but I'm not using it because:
- I already have it working OK
- I'm not sure if it takes command
- I'm not sure if the installer can unzip it, and run it without touching the system much.

Emil,

Have a look at the Lin'N'Win notes to see precisely what happens for Windows 9x and Windows XP. Noryb009 has taken my manual procedure and automated it!

I will be updating Lin'N'Win soon with the Windows 7 technique of Noryb009.

The Lin'N'Win notes can be found here:
http://www.icpug.org.uk/national/linnwi ... innwin.htm

Hi all, thank you for the info!

I tried to advocate the exe installer I made from my Sage Puplet to the Sage community. I met with some support, but overall response was very sceptical. They fear to break something on users windows machines, and risk reputation.

Well, may it be so. One problem I found was really with Windows 7 on 64 bit.
The installer hangs at the bcdedit command for backup ...

I had one negative report from the sage-windows group. Bill tried really hard to get it working, but couldn't. I then walked to friend who has a 64 bit windows 7. It was exactly the same problem there.

The script couldnt get bcdedit to make a backup (there the installer stops), also there was no menu entry created in the bootloader.

I typed the commands manually in the command shell, It worked fine. Do you have an idea what can be wrong here? Can it by some sort of weird permission problem? (I ran the install script, as well as the command shell "as administrator")

All 32-bit installs were fine until now!

kind regards
emil

emil: That's not good.

Are you sure it says "bcdedit /export "C:\Backups\BCD Backup"" in the execute area? (see attached "installer" which is running cmd). Also, does the folder "C:\Backups\BCD Backup" exist?

I may see the problem, if that's the case.

At my 32 bit windows the directory Backup exists (where it worked smoothly). I am not sure on the 2 64 bit systems (where it failed). I will maybe check tomorrow.

Yes the progress bar was there. I am pretty sure that it stopped at the backup (no backup was created). (althoug the graphics of the windows 7 progress bar has pretty improved compared to your picture )

Wen I quit the installer and rerun it it skips the extraction of the lupq-511.sfs, it then creates the grldr.mbr and grldr files, but no menu.lst.

I added menu.lst manually and also the boot entry manually using bcdedit, then it booted without problem.

Hm, one thing I noticed is that I had no sound on the 2 windows machines (no woof woof), but that is probably completly unrelated.

Hm, one thing I noticed is that I had no sound on the 2 windows machines (no woof woof), but that is probably completly unrelated.

Yes, this was a problem in 511, but it's fixed in 520 beta.

noryb009,

Thanks for your installer.

I had made it succesful in puppy511 and puppy520.

and I had plused a message in grub4dos.

It's very beautiful.
and upgrade grub4dos to 0.4.5b
http://code.google.com/p/grub4dos-chena ... loads/list

windows installer.exe in http://www.minilinux.net/node/1649.

But, I just known how to plus in menu.lst
I do not known how to fix it in uninstall,
Can you help?

thanks.