LICK is a Puppy Linux installer for Windows. It configures Windows and Puppy Linux to create a dual-boot environment in just a few clicks. This makes it perfect if you want to try out Linux without the hassle of installing.

LICK is versatile: it can be run on almost any version of Windows, from Windows 95 to Windows 10, on BIOS or UEFI.

LICK is easy to use: It does not require a CD to be burnt or a USB drive to run. Download a Puppy Linux ISO and select it in the program to install it.

LICK is developer-friendly: If you want to bring the power of LICK to your application or distribution, a command line utility and a library are available. LICK is licensed under the MIT license, so feel free to use it however you like.

The predecessor to LICK is PLIC - the Puppy Linux Installer Creator. It has been deprecated. For reference, the original first post of this thread can be found here.Last edited by noryb009 on Sun 20 Mar 2016, 16:12; edited 16 times in total

One thing for the installer creators:
Extracting the zip, the foler named 'Puppy Linux Installer Creator V1.0'.
There is another folder named 'Puppy Linux Installer Creator' under the 'Puppy Linux Installer Creator V1.0'.
You can extract the zip anywhere. Then move the inner folder 'Puppy Linux Installer Creator' to C:\.

Created the Quickset Wary/LupQ Windows installer.
Do not support Windows Me.
Quickset_Wary_Puppy_Linux-511.exe from here
md5sum: d5bc0c6361d2516c54cec78d8bb281bc

Lucid-Puppy-Quickset-edition-511-Installer.exe from here
md5sum: 6c7dba6b5dfe49a09ee785ce3dc22b36_________________Downloads for Puppy Linux http://shino.pos.to/linux/downloads.htmlLast edited by shinobar on Sun 24 Apr 2011, 07:56; edited 1 time in total

I have a Windows 7 computer now but I am naturally reluctant to mess its booting up by running an installer when I don't know what it does! (Lin'N'Win has not been updated to cover Windows 7 yet).

Is it possible to briefly describe how the scripts in the installer achieve the boot on a Windows 7 machine? Does it copy grldr somewhere? How does it edit the BCD to refer to grldr - what tools used - what lines added?

Hopefully, you will allow me to include your description in Lin'N'Win in return for an acknowledgement.

My second query relates to what happens if someone installs a SECOND puppy by an installer that has been created by your method. Will the installer recognise that all the bits are in place and simply add a block to the menu.lst?

Is it possible to briefly describe how the scripts in the installer achieve the boot on a Windows 7 machine? Does it copy grldr somewhere? How does it edit the BCD to refer to grldr - what tools used - what lines added?

Hopefully, you will allow me to include your description in Lin'N'Win in return for an acknowledgement.

Of course! You were the one who did most of the work for this project. I would have never gotten 9x working.

Quote:

My second query relates to what happens if someone installs a SECOND puppy by an installer that has been created by your method. Will the installer recognise that all the bits are in place and simply add a block to the menu.lst?

Yes, it will just add to the menu.lst. It checks C:\ and C:\boot\grub for a menu.lst, and adds itself to it. It also only asks to uninstall grub if it's the last puppy installed.

Quote:

I have a Windows 7 computer now but I am naturally reluctant to mess its booting up by running an installer when I don't know what it does! (Lin'N'Win has not been updated to cover Windows 7 yet).

Is it possible to briefly describe how the scripts in the installer achieve the boot on a Windows 7 machine? Does it copy grldr somewhere? How does it edit the BCD to refer to grldr - what tools used - what lines added?

First of all, it copys grldr and grldr.mbr (both in the grub4dos zip file, I'm not sure if you need grldr) to C:\, then runs the following commands in command prompt:

Code:

bcdedit /export "C:\BCD Backup"
(backs up the BCD, for safety)

bcdedit /create /d "Start Puppy Linux" /application bootsector
(Adds the puppy entry)
This command returns an ID, like in this image: http://murga-linux.com/puppy/viewtopic.php?mode=attach&id=33758
The installer gets the ID. You have to use the { } brackets for it to work.

Thank you Noryb for the explanation of how the windows 7 install works. That was just what I needed and will suffice while I investigate around some issues I have (understanding windows 7).

Your post encouraged me to read again some stuff I had collected ready for when I had Windows 7 - most notably the Grub4dos_tutorial and the README_GRUB4DOS.txt that is part of the Grub4DOS package. These are the only 2 docs I have found for grub4DOS. The readme is technical and written by someone who does not have English as a first language, although it is pretty good! The tutorial is more user friendly.

I see your technique is basically that from the readme with the crucial step about noting the {id} and substituting it in subsequent commands made clear! The tutorial neglected this and confused me a bit.

By the way, this line in the tutorial is shown as:
bcdedit /set {ID} device boot
which I think is out of date. Your line is more correct according to Microsoft and the readme. I don't know the subtleties of BCEDIT yet. Must download Microsoft's manual to BCEDIT, but it is in their appalling docx format only.

One thing I can tell you. With this approach you need both grldr.mbr AND grldr. The latter is called up by the former.

What I would like to know at some point is whether one can dispense with grldr.mbr and call up grldr directly, but that is one for me to play with, (as is the rather more drastic renaming of bootmgr to winbootmgr and grldr to bootmgr and then chainload winbootmgr from grub when windows is required!).

Go to makensisw, open (top left, under File), then select main.nsi (make sure it's from C:\, not Z:\).

EDIT: also make sure /root/.wine/drive_c/Puppy Linux Installer Creator/Puppy Linux Install.ico is a file. I am currently using 501, which might also have something to do with it.Last edited by noryb009 on Fri 05 Nov 2010, 19:51; edited 1 time in total

The tutorial should be right if the grldr.mbr is on the boot partition.
But our case, the grldr.mbr is copied on the C:\, so we need to use "partition=C:" instead of 'boot'. (I am not sure the quotation is required or not,)

We are better to be aware of the Windows 7 installation style.
The standard style of the Windows 7 installer makes a small(100-200MB) boot partition and the system in the next partition.
The first partition is ntfs but hidden from the Windows system, so the second is 'C:".
Therefore, the boot partition and 'C:' can be the same and can be different depending on the installation style.

If we can put the grldr.mbr on the boot partition, it must be more simple.
But our installer works on the Windows system, which cannot access the boot partition in this case.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum