Puppy Linux Windows Installer - LICK v1.3.3 released
It is an HP pavillon 15incbh. An Intel 1.9giga CPU. Only just over a year old but it does not have those lights unfotunately.
One for Caps. 1 for charging mains. On/off . Wifi. That's it.
I'll try to get another PC up and at it. If I could flash the bios with USB... which means at least one of the now 2 o.o.o. PCs working.
I really messed up on this. And it has info that I must get back in it. As well I want to change screen in time...
Or as it has been on 24/7 for 15 months maybe... I can'thear the disk even....
One for Caps. 1 for charging mains. On/off . Wifi. That's it.
I'll try to get another PC up and at it. If I could flash the bios with USB... which means at least one of the now 2 o.o.o. PCs working.
I really messed up on this. And it has info that I must get back in it. As well I want to change screen in time...
Or as it has been on 24/7 for 15 months maybe... I can'thear the disk even....
Boot.ini located in a different partition.
I cant seem to get LICK to work with my particular system configuration. I am running Windows XP which is installed on D: drive but for some reason the boot.ini is located in C: drive. Is there any way to point LICK towards the actual boot.ini location? I have included a screenshot illustrating the exact error. Thanks in advance!
P.S. On this very config I had earlier got Puppy running via Lin' and Win' method. But I would much rather automate it. Plus the Puppy Windows installer worked as well.
P.S. On this very config I had earlier got Puppy running via Lin' and Win' method. But I would much rather automate it. Plus the Puppy Windows installer worked as well.
- Attachments
-
- lick.jpg
- (67.91 KiB) Downloaded 600 times
amn87: Thanks for the bug report. I've created a patch that should fix your issue. You can download a zip file here. Let me know if it resolves your issue. If all goes well, I'll make a new official release.
starlyte: Could you please answer the other questions in my last post:
starlyte: Could you please answer the other questions in my last post:
When you turn on your computer, does the power button / power light turn on? If you don't press anything for a few minutes, does it turn off at some point?
Press the caps lock key a few times throughout the startup. Does the light respond to the button? When does it become responsive or unresponsive?
Many thanks for the quick response. I managed to get Puppy installed via the command line interface. There was a new entry in the boot.ini file and upon reboot I was prompted with an option to "Start LICK loader" but it merely presented with a new error, along the lines of " Windows installation is corrupt. hal.dll is missing" But my original Windows was not affected.noryb009 wrote:amn87: Thanks for the bug report. I've created a patch that should fix your issue. You can download a zip file here. Let me know if it resolves your issue. If all goes well, I'll make a new official release.
starlyte: Could you please answer the other questions in my last post:
When you turn on your computer, does the power button / power light turn on? If you don't press anything for a few minutes, does it turn off at some point?
Press the caps lock key a few times throughout the startup. Does the light respond to the button? When does it become responsive or unresponsive?
I hope this is OK?noryb009 wrote:amn87: There's a few ways that error can appear. Could you post the contents of your boot.ini, both with the bootloader installed and uninstalled? (you can do it from the menu in the GUI, or I believe one of the options in the CLI).
Before: [boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /NoExecute=OptOut
After: [boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /NoExecute=OptOut
D:\pupldr="Start LICK Boot Loader"
Hey amn87,
I've replicated your setup and am going to investigate more to find the best solution. I will hopefully fix it in the next week or so.
In the mean time, to fix your setup:
0) Install an iso you want in lick.
1) Make boot.ini writable: open command prompt and run:
2) Edit boot.ini in notepad and change
4) Optionally make boot.ini read-only with
I've replicated your setup and am going to investigate more to find the best solution. I will hopefully fix it in the next week or so.
In the mean time, to fix your setup:
0) Install an iso you want in lick.
1) Make boot.ini writable: open command prompt and run:
Code: Select all
attrib -S -H -R C:\boot.ini
toD:\pupldr="Start LICK Boot Loader"
3) Copy pupldr and lickmenu.lst from D:\ to C:\. (If you install/uninstall an iso, you will have to copy over lickmenu.lst again).C:\pupldr="Start LICK Boot Loader"
4) Optionally make boot.ini read-only with
Code: Select all
attrib +S +H +R C:\boot.ini
This worked just fine. Thanks a lot. I can now directly boot to a minimal Puppy install without having to hunt for a USB key.noryb009 wrote:Hey amn87,
I've replicated your setup and am going to investigate more to find the best solution. I will hopefully fix it in the next week or so.
In the mean time, to fix your setup:
0) Install an iso you want in lick.
1) Make boot.ini writable: open command prompt and run:2) Edit boot.ini in notepad and changeCode: Select all
attrib -S -H -R C:\boot.ini
toD:\pupldr="Start LICK Boot Loader"3) Copy pupldr and lickmenu.lst from D:\ to C:\. (If you install/uninstall an iso, you will have to copy over lickmenu.lst again).C:\pupldr="Start LICK Boot Loader"
4) Optionally make boot.ini read-only withCode: Select all
attrib +S +H +R C:\boot.ini
Hey,
Noryb, thanks so much for the lick boot-loader. I have an eeepc 1100 which refuses to boot off of a usb key and because there is no optical drive, I was using Slacko 5.7 which came as a .exe file. But with your boot-loader I was able to upgrade my system to Slacko 6.3.0 32 bit. Lick worked like a charm and it was very, very easy to use. Did I mention that the pc came with Win 7 installed. I'm posting from Slacko now.
Thanks again for your hard work on this as it is greatly appreciated.
Noryb, thanks so much for the lick boot-loader. I have an eeepc 1100 which refuses to boot off of a usb key and because there is no optical drive, I was using Slacko 5.7 which came as a .exe file. But with your boot-loader I was able to upgrade my system to Slacko 6.3.0 32 bit. Lick worked like a charm and it was very, very easy to use. Did I mention that the pc came with Win 7 installed. I'm posting from Slacko now.
Thanks again for your hard work on this as it is greatly appreciated.
amn87: I've made changes in lick that should fix the issue completely, and remove the need to copy over lickmenu.lst whenever it changes. It would be greatly appreciated if you could follow the instructions below and let me know how it goes.
0) Make a backup of C:/lickmenu.lst. This file should contain entries for all of your puplets.
1) Open lick 1.0.0b (the one linked to earlier on this page), and go to "file" > "install/uninstall bootloader", and confirm you want to uninstall it.
2) Download 1.0.0c, and go to "file" > "install/uninstall bootloader", and confirm you want to install the bootloader.
3) Move C:/lickmenu.lst to the D drive (overwrite the nearly-empty one with your actual configuration).
If all goes well, I'll make this a new release.
cypher51: Thanks for the feedback. It's encouraging to hear stories like that
0) Make a backup of C:/lickmenu.lst. This file should contain entries for all of your puplets.
1) Open lick 1.0.0b (the one linked to earlier on this page), and go to "file" > "install/uninstall bootloader", and confirm you want to uninstall it.
2) Download 1.0.0c, and go to "file" > "install/uninstall bootloader", and confirm you want to install the bootloader.
3) Move C:/lickmenu.lst to the D drive (overwrite the nearly-empty one with your actual configuration).
If all goes well, I'll make this a new release.
cypher51: Thanks for the feedback. It's encouraging to hear stories like that
It worked just fine. No problems at all.noryb009 wrote:amn87: I've made changes in lick that should fix the issue completely, and remove the need to copy over lickmenu.lst whenever it changes. It would be greatly appreciated if you could follow the instructions below and let me know how it goes.
0) Make a backup of C:/lickmenu.lst. This file should contain entries for all of your puplets.
1) Open lick 1.0.0b (the one linked to earlier on this page), and go to "file" > "install/uninstall bootloader", and confirm you want to uninstall it.
2) Download 1.0.0c, and go to "file" > "install/uninstall bootloader", and confirm you want to install the bootloader.
3) Move C:/lickmenu.lst to the D drive (overwrite the nearly-empty one with your actual configuration).
If all goes well, I'll make this a new release.
cypher51: Thanks for the feedback. It's encouraging to hear stories like that
LICK v1.1 has been released. It includes a few fixes, and a new feature.
Most of the changes are to fix when Windows 9x/NT is installed on a different drive than config.sys/boot.ini (thanks to amn87 for submitting this bug report).
It's recommended to upgrade because of the other fix: on v1.0 and before, uninstalling the bootloader from the menu while having puplets installed cause the grub menu to be recreated, loosing the menu entries for those puplets. This has been fixed in v1.1.
A reminder that you do not need to uninstall anything before upgrading, simply install the exe to the same location as your current installation, or unzip the zip file.
Most of the changes are to fix when Windows 9x/NT is installed on a different drive than config.sys/boot.ini (thanks to amn87 for submitting this bug report).
It's recommended to upgrade because of the other fix: on v1.0 and before, uninstalling the bootloader from the menu while having puplets installed cause the grub menu to be recreated, loosing the menu entries for those puplets. This has been fixed in v1.1.
A reminder that you do not need to uninstall anything before upgrading, simply install the exe to the same location as your current installation, or unzip the zip file.
I have just downloaded V1.1 and it seems to install Tahrpup64 correctly on a new Acer notebook with windows 10. But when I shutdown and restart the computer there is no menu to select Puppy - it just goes straight to Windows.
Has anyone any suggestions before I get really mad and just wipe Windows.
In case it matters, the ACER has a solid state drive and the partitions appear in Puppy (from a USB stick) as mmcblk0pX rather than as sdaX that I was used to on the laptop I am typing this on.
Thanks.
...R
Has anyone any suggestions before I get really mad and just wipe Windows.
In case it matters, the ACER has a solid state drive and the partitions appear in Puppy (from a USB stick) as mmcblk0pX rather than as sdaX that I was used to on the laptop I am typing this on.
Thanks.
...R
Hey Robin2,
I'm going to assume that you have a UEFI bootloader. I'll also assume you know how to access the UEFI bootloader menu, since you could boot a USB.
Somewhere in the menu, you should see "Windows Boot Manager" (like this photo, but only 1). Beside it, you may see "LICK Boot Manager" - if so, what happens when you boot into it? (Note that if this boots puppy, you can likely switch the boot loader order here to resolve your issue. I would appreciate if you could follow the rest of the steps to help figure out how this happened, but it's completely optional)
If you don't see "LICK Boot Manager", or if it doesn't open Puppy, boot back into Windows. Open a command prompt window as an administrator, and run:
What is the output of this command?
I'm going to assume that you have a UEFI bootloader. I'll also assume you know how to access the UEFI bootloader menu, since you could boot a USB.
Somewhere in the menu, you should see "Windows Boot Manager" (like this photo, but only 1). Beside it, you may see "LICK Boot Manager" - if so, what happens when you boot into it? (Note that if this boots puppy, you can likely switch the boot loader order here to resolve your issue. I would appreciate if you could follow the rest of the steps to help figure out how this happened, but it's completely optional)
If you don't see "LICK Boot Manager", or if it doesn't open Puppy, boot back into Windows. Open a command prompt window as an administrator, and run:
Code: Select all
bcdedit /enum all
Thanks for your reply. I did not see that boot menu at all.
I have booted from the USB stick in legacy mode.
I suspect my question may have been overtaken by events. Last night I was trying to implement the lin'n'win system and I seem to have screwed up the disk. GParted now reports the entire SolidState drive as "unallocated" I have now fixed this with a program called gdisk.
In case it is any help I did not see any sign that your Installer made any changes to the BCD file. The command bcdedit /v produced the same result before and after.
I have made progress with the lin'n'win instructions and have got menu options but it is not completely working yet with grub.
...R
I have booted from the USB stick in legacy mode.
I suspect my question may have been overtaken by events. Last night I was trying to implement the lin'n'win system and I seem to have screwed up the disk. GParted now reports the entire SolidState drive as "unallocated" I have now fixed this with a program called gdisk.
In case it is any help I did not see any sign that your Installer made any changes to the BCD file. The command bcdedit /v produced the same result before and after.
I have made progress with the lin'n'win instructions and have got menu options but it is not completely working yet with grub.
...R
To confirm, this was after the ISO was installed, not lick itself, correct? (you can have the same effect by going to "file" > "install/uninstall bootloader")In case it is any help I did not see any sign that your Installer made any changes to the BCD file
The lin'n'win method doesn't yet actually support UEFI - you probably get an error similar to this.
Anyway, here is the UEFI-compatible instructions that lick more or less performs. You can go through them and see what parts don't work:
Now try to reboot, and you should see different screen when you boot (the only thing in it will be Windows, but we can add puppy to it later). If you run into any issues in the process, please post whatever errors you get. If you get through everything and it still doesn't work, post the output of running# disable fast boot in an admin command prompt
powercfg -h off
# mount your UEFI partition as the z:/ drive (note this won't show up in windows explorer, but you can run `Z:` to go to the Z drive):
mountvol z: /S
# Next, download grub2 for windows, and unzip it somewhere. Next, run:
path/to/grub2/grub-install --target=x86_64-efi --bootloader-id=LICK --efi-directory=z: --boot-directory=z:/EFI/LICK --recheck
# Set the default grub.cfg file to read a grub.cfg file on your C drive for easier editing. In an admin command prompt, run:
notepad Z:/EFI/LICK/grub/grub.cfg
And paste in:# Next, open up (or create the text file) C:/lickgrub.cfg, and paste in the contents here.Code: Select all
insmod part_gpt insmod part_msdos insmod ntfs search --set=root --file /lickgrub.cfg configfile ($root)/lickgrub.cfg
Code: Select all
bcdedit enum /all
Thanks. That is very helpful.
Your image seems to be the exact error I was getting with another approach to dual boot. I have tried 4 different ones today so I am a bit confused. With LICK I did not see any menu to allow me to select anything - Win10 just booted as if I had never tried LICK
Yes, I was talking about the absence of changes to the BCD file after the ISO was installed.
I am a bit wary of your suggestion "mount your UEFI partition" - and a bit confused. Win10 itself seems to use 3 partitions and I have added 3 more for Linux. Which partition do you mean? and if it is one of the Win10 partitions will it cause trouble.
Earlier today I came across this Blog entry for UEFI boot
http://blog.puppylinux.com/?viewDetailed=00009
and it seems very simple and nearly works with TahrPup64 (there is a problem with graphics even though the same TahrPup works fine with legacy boot and syslinux). If I can get the graphics working I suspect it would fit well with BCD - now that I think I know how to use BCD Edit.
I will think more about your suggested solution tomorrow - time for bed now.
Thanks again
...R
Your image seems to be the exact error I was getting with another approach to dual boot. I have tried 4 different ones today so I am a bit confused. With LICK I did not see any menu to allow me to select anything - Win10 just booted as if I had never tried LICK
Yes, I was talking about the absence of changes to the BCD file after the ISO was installed.
I am a bit wary of your suggestion "mount your UEFI partition" - and a bit confused. Win10 itself seems to use 3 partitions and I have added 3 more for Linux. Which partition do you mean? and if it is one of the Win10 partitions will it cause trouble.
Earlier today I came across this Blog entry for UEFI boot
http://blog.puppylinux.com/?viewDetailed=00009
and it seems very simple and nearly works with TahrPup64 (there is a problem with graphics even though the same TahrPup works fine with legacy boot and syslinux). If I can get the graphics working I suspect it would fit well with BCD - now that I think I know how to use BCD Edit.
I will think more about your suggested solution tomorrow - time for bed now.
Thanks again
...R
Last edited by Robin2 on Fri 29 Apr 2016, 22:41, edited 1 time in total.