So assuming that the boot menu shows up (let me know if it doesn't) and trying to boot LICK still returns the error "file: \pupldr.mbr could not be loaded" (let me know if it doesn't):

I originally saw this error when trying to run the BIOS install method on UEFI systems. At the time I thought the ...

Hi Charlie,

Your system configuration seems a bit odd. Could you run Command Prompt as an admin, and copy/paste the output of:
I'm mostly interested if there's a section about LICK, and what the normal boot procedure uses (paths that end with a EFI extension or not).

wiak,

If the squashfs/initrd.gz/vmlinuz can boot from a directory on an NTFS drive, it should work. There's a way to install from a directory, just give the directory when it asks for an ISO, I suspect that will work for you.

Other distros are half supported by LICK - there's support in the ...

Hi charlie6,

First, sorry that I didn't respond earlier, I never got an email notification from the forum :(

The pupl.exe is not for your system, it's only used for Windows 95/98/ME. I'm not surprised it gives an error on Windows 10.

pupldr.mbr is only created if LICK thinks your system uses BIOS ...

Jake, thanks for the info. It sounds like I haven't tested LICK with a configuration similar to yours, so one of the pre checks or checks during installation saw something it didn't expect, so everything was reversed. Unfortunately, finding and testing these more exotic setups is time consuming and ...

Hi again DuMar,

The default beginning to lickgrub.cfg can be found here . You should be able to add everything in that file before your current contents.

I'll try to figure out what went wrong. Lick should be safe to use whenever, it looks like you fell into an edge case that isn't handled ...

Hi DuMar,

It sounds like that's an issue with the X configuration or installation, so you're better off asking in the beginner's help or users forums. There's no real difference between LICK and other install methods that should have an effect on X.

Hey jake29,

I haven't been able to reproduce the issue. I've added more tracing to the program, so hopefully this will point us towards the problem.

Please download this file , and try using it (it's built off of this branch , if you care). Hopefully it gives a more accurate error message.

If it ...

Hey jake29,

Sorry for not replying earlier. I'm trying to reproduce the issue. I'll let you know if I can reproduce the issue, or if I'll require you to run something for me. In the mean time, let me know if you figure it out.

Hey Wognath,

It's good to hear that you still use LICK!

The "Nothing happens on reboot" menu item does something like steps 4-6. So after you reinstalled Windows, if you just reinstalled LICK and clicked that extra button, you would essentially be in the same spot

linux28: Did you specify a `-j` flag for `make`? Don't do that, there are some issues when you compile with multiple threads. Otherwise, you should be able to just run something like:


cd build
cmake ..
make


You will still get errors when compiling FLTK, but the tests and CLI will be compiled ...

The cfg file is drive-agnostic. Each boot, it searches all your partitions for certain files associated with a puppy, which makes partition mapping a lot easier (especially from old versions of Windows). So the cfg file is expected here.

You might need to add
insmod fat

to the beginning of the ...

phredo :

The simplest way I can think of is have a puppy that is slightly different from one on your hard drive, then manually edit the boot entry each boot. For example, if you have "puppy-123" on your hard drive, you can have "puppy-1234" on your SD card (regardless of the name of the actual ...

is it possible to request another tool that can rw an sfs?

That's beyond my skill set. I only manage LICK, it's the rest of the community that does all the heavy lifting. I don't know the correct place to ask for that.

okkebasin: If you're in the USB version of puppy, can you see whatever is on ...

If grub can't find something, it returns an error saying that the file can't be found. It might be hanging, waiting for a partition to become ready to be searched.

To check which partition is which, just ls them (the trailing slash gives you file names, without the slash you get info about the ...

Hi okkebasin,

Do you get to the UEFI boot menu, or the grub boot menu?

If you only get to the UEFI boot menu, where is LICK installed? If it's on the SD card, you might need to move it to an internal partition or USB drive, then have puppy on an SD card.

If you get to the grub boot menu but can't ...

First, in the future, please be careful following instructions in posts, and if you deviate from the instructions, please note how in your post. In this case, I specifically asked about "C:/lickgrub.cfg" because it has a very different purpose than "C:/Program Files/lick/res/lickgrub.cfg".

For your ...

There's a few things in your post which are odd to me, let's figure out those first so I can help you set the default.

1) You mention you have Windows XP, but your lickgrub.cfg file seems to be set up for a newer Windows bootloader. Are you sure LICK generated this file?

2) Is that your entire ...

Sorry, but Linux Mint isn't supported by LICK

In that case, the process is somewhat confusing, so I won't write it out in text. Follow this video, but look for the bcdedit entry with the description "LICK Boot Loader".