Puppy Linux Discussion Forum

[noryb009]

Hi Don,

Sorry, I should have included more details in my last reply.

First, it looks like you were trying to enter the path to lick, not the path to a puppy ISO file. I recommend putting the ISO file in the root of the C drive, then you can just enter C:/puppy-iso-name.iso.

For the ID and name, you can type any id or name you want. You can also just press enter to use the default (in your case, LICK=1.3.1-win32).

A complete example is:

[Donncha]

Luke: absolutely brilliant (after I had tracked down my own dislexic typos)!
So thank you not only for a wonderful utility but for your fast five star help.
In hindsight I feel a bit stupid not to have worked out the solution for myself
Don

[noryb009]

Hi Don, I'm glad to hear you got it working! I now see that it's not so clear why the GUI doesn't work in 9x, or how to use the CLI (I thought I had documentation for each, but I guess not). Anyway, I've created an issue for both of these, which will hopefully help people in your situation in the future.

Thanks!

[Ron911]

Hello everyone,

I am a daily user of Puppy (Quirky, Precise, now Xenial, etc) but up until now always on older hardware with old BIOS. I used Grub4dos on those systems.

Last week I bought a new Acer Aspire 1 A111 - 31 with UEFI and it seems that it has no "legacy" option. (I did dis-activate fast boot)
So I searched the web and found (and used) LICK to help me dual boot Windows 10 and FatDog 64.

The boot options are there when I turn on the machine but when I click on Fatdog 721 (with or without savefile) I get following result:
loadig base sfs form initrd: file /fd64.sfs
cannot load base sfs
Windows 10 option still works, so I can boot into it.

Since I am not very technical adept, does somebody know how I can remedy that problem?
In the future I count on deleting windows 10 altogether but since this is a new computer and I can (for the moment) only boot puppy from USB I would first like to get this thing right.

Thank you very much
Ron

[noryb009]

Hi Ron,

It looks like LICK gets confused from FatDog's two initrd files (initrd and initrd-nano.xz). You should be able to open up your C:/lickgrub.cfg and switch the two initrd lines from

[Ron911]

Hi Noryb009,

That did it!
I can now boot into Fatdog64 without a problem.
Thank you very much for your help and tool.
Ron

[noryb009]

LICK 1.3.2 has been released. This fixes support for recent Fatdog distributions, and documents Windows 9x issues.

As always, you can download it from here.

Edit: 1.3.3 has just been released. This fixes a small bug in 1.3.2.

[Ron911]

Hello,

I still have a small problem for which I do not find a solution.
When I turn on the laptop and choose the Fatdog64 option, then at a certain moment I see:

loading save file from local, searching for /fd64save.ext4
(this although I have a save folder named "fd64save800")

Then starts a search in all partitions for save files/folders and I get to choose from 2 possibilities. (I have 2 save folders, 1 for FD64 frugal and 1 for a USB FD64).
(My save folder is at the same level as the Fatdog64-800 folder, not inside it)

I tried to load the right file with savefile=direct:device... but that seems not to work. See my lickgrub.cfg :

***********************************************************************
## start section Windows
menuentry "Windows" {
insmod chain
search --set=root --file /efi/microsoft/boot/bootmgfw-backup.efi
chainloader /efi/microsoft/boot/bootmgfw-backup.efi}
## end section Windows

## start section Fatdog64-800
menuentry 'Fatdog64 800' {
search --set=root --file /Fatdog64-800/vmlinuz
linux /Fatdog64-800/vmlinuz pfix=fsck psubdir=Fatdog64-800
initrd /Fatdog64-800/initrd
savefile=direct:device:mmcblk0p3:/fd64save800
}


menuentry 'Fatdog64 800 (no save file)' {
search --set=root --file /Fatdog64-800/vmlinuz
linux /Fatdog64-800/vmlinuz pfix=ram savefile=none psubdir=Fatdog64-800
initrd /Fatdog64-800/initrd
}
## end section Fatdog64-800
***********************************************************************


I also tried with /dev/direct/device... and dev/direct:device... but to no avail.

Where did I go wrong???

Thanks
Ron

[jamesbond]

Assuming you get the mmcblk0p3 right, then your

[Ron911]

Hi JamesB,

Thank you once again.
No problem booting automatically with the Fatdog 800 save folder now.
Have a nice weekend

Ron

[number77]

Hello
Is there any way that I can install Puppy to an ext4 file with lick.
I have win7 on an ntfs partition and have three ext4 partitions on the hdd and would like to install xenial64 to one of them but lick running on win7 will not show any ext4 partitions. Is there any way round this or must I use ntfs partitions.
Thanks
number77

[noryb009]

Windows doesn't have the ability to read from or write to ext4 drives, so LICK won't help you in your case. Sorry!

[number77]

Thanks norby009, I will put up with ntfs. Lick is pretty amazing and easy to use, thanks for it.
number77

[bigpup]

[tallboy]