Puppy Linux Windows Installer - LICK v1.3.3 released

A home for all kinds of Puppy related projects
Message
Author
noryb009
Posts: 634
Joined: Sat 20 Mar 2010, 22:28

#511 Post by 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:

Code: Select all

  Main menu:
  1) Install ISO or from CD
  2) Entry submenu (view/delete)
  3) Install/uninstall boot loader
  4) Quit
  Choice:
1<enter>
  ISO file or CD drive:
C:/xenialpup64-7.5-uefi.iso<enter>
  Install to drive:
  1) C:/
  2) D:/
1<enter>
  Enter ID [xenialpup64-7.5-uefi]:
<enter>
  Enter Name [xenialpup64 7.5 uefi]:
<enter>
This should install the ISO and send you back to the main menu. From there, you can go to the entry submenu and see the puppy you just installed.

Donncha
Posts: 34
Joined: Sun 02 Oct 2011, 10:01

#512 Post by 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 :oops:
Don

noryb009
Posts: 634
Joined: Sat 20 Mar 2010, 22:28

#513 Post by 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
Posts: 14
Joined: Fri 22 Feb 2019, 12:40

Problem with LICK and Fatdog 64 om Acer Aspire 1 A111

#514 Post by 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
Posts: 634
Joined: Sat 20 Mar 2010, 22:28

#515 Post by 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

Code: Select all

initrd /whatever/initrd-nano.xz
to

Code: Select all

initrd /whatever/initrd
In the mean time, I've created an issue, I'll try to fix it soon.

Ron911
Posts: 14
Joined: Fri 22 Feb 2019, 12:40

#516 Post by 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
Posts: 634
Joined: Sat 20 Mar 2010, 22:28

#517 Post by 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
Posts: 14
Joined: Fri 22 Feb 2019, 12:40

#518 Post by 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
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#519 Post by jamesbond »

Assuming you get the mmcblk0p3 right, then your
Ron911 wrote:## 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
}
should be

Code: Select all

## start section Fatdog64-800
menuentry 'Fatdog64 800' {
search --set=root --file /Fatdog64-800/vmlinuz
linux /Fatdog64-800/vmlinuz dofsck savefile=direct:device:mmcblk0p3:/fd64save800
initrd /Fatdog64-800/initrd
}
and your
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
}
shoud be

Code: Select all

menuentry 'Fatdog64 800 (no save file)' {
search --set=root --file /Fatdog64-800/vmlinuz
linux /Fatdog64-800/vmlinuz savefile=none 
initrd /Fatdog64-800/initrd
}
Notes:
1. Fatdog doesn't understand psubdir, it doesn't need it. All savefile-related parameters are specified in "savefile".
2. Fatdog doesn't understand "pfix=ram", however "savefile=none" has exactly the same meaning
3. Fatdog doesn't understand "pfix=fsck" but "dofsck" means exactly the same thing.
4. All boot parameters must be specified in the same line as the "vmlinuz" line, no line breaks in between.

Good luck.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

Ron911
Posts: 14
Joined: Fri 22 Feb 2019, 12:40

#520 Post by Ron911 »

Hi JamesB,

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

Ron

number77
Posts: 804
Joined: Fri 22 Oct 2010, 19:30

#521 Post by 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
Posts: 634
Joined: Sat 20 Mar 2010, 22:28

#522 Post by 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
Posts: 804
Joined: Fri 22 Oct 2010, 19:30

#523 Post by number77 »

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

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#524 Post by bigpup »

noryb009 wrote:Windows doesn't have the ability to read from or write to ext4 drives, so LICK won't help you in your case. Sorry!
There are third party programs that can read/write to ext formats in Windows.
They add the ability to Windows.
This is one of them:
https://www.diskgenius.com/how-to/ext4-windows.php

There are many other third party programs out there.

I guess, for Lick to write to ext4. It would need to know to do it, using one of these programs.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

User avatar
tallboy
Posts: 1760
Joined: Tue 21 Sep 2010, 21:56
Location: Drøbak, Norway

#525 Post by tallboy »

number77 wrote:Lick is pretty amazing and easy to use, thanks for it.
I totally agree! :D
I have just used Lick to install 3 Puppys for testing, into Win 10. On shutdown I was asked if I wanted to make a savefile, and was given a choice of size, which I set to 1Gb, and which format to use for it. The default was ext2, which I chose, but when I look at the savefile from Puppy, I see that it is ext3.
I also have split the ntfs partition, and made a ext3 partition for my files in work. I cannot see any problems right now, by having the program files in an ntfs partition, as long as it works!
Question: As far as I know, the Puppy is loaded into RAM in compressed files. Will the Puppy run faster if they are loaded into RAM uncompressed, as in my live Puppies?
True freedom is a live Puppy on a multisession CD/DVD.

number77
Posts: 804
Joined: Fri 22 Oct 2010, 19:30

#526 Post by number77 »

bigpup wrote:[know to do it, using one of these programs.[/color]
I did try that but it didn't help lick to find the ext4 partition so I formatted to ntfs. But somehow I don't feel safe with ntfs as its microsoft.

noryb009
Posts: 634
Joined: Sat 20 Mar 2010, 22:28

#527 Post by noryb009 »

As far as I know, the Puppy is loaded into RAM in compressed files. Will the Puppy run faster if they are loaded into RAM uncompressed, as in my live Puppies?
That should probably be asked elsewhere on the forum. But between the obvious savings of not needing to continuously decompress things, and the cost of having less RAM free for other things (such as file buffers for persistent disks), I'm not sure.
But somehow I don't feel safe with ntfs as its microsoft.
Linux distros use NTFS-3G, which is open source.

If you still don't like it, you should be able to move the files in C:/your-puppy to the root of an ext3 disk and it should "just work". (Keep in mind that if you do this, LICK won't be able to delete the files when you uninstall the distro).

User avatar
tallboy
Posts: 1760
Joined: Tue 21 Sep 2010, 21:56
Location: Drøbak, Norway

#528 Post by tallboy »

Thank you, noryb009.
True freedom is a live Puppy on a multisession CD/DVD.

User avatar
tallboy
Posts: 1760
Joined: Tue 21 Sep 2010, 21:56
Location: Drøbak, Norway

#529 Post by tallboy »

I am unfamiliar with Windows, but I know that it is not exactly famous for it's security. The savefile for my Puppy in Win 10 is ext4, and is, as far as I know, not normally accessible from within Windoze. Are there any special security issues regarding the use of Lick? Any situations not usually met when using a Puppy?
True freedom is a live Puppy on a multisession CD/DVD.

noryb009
Posts: 634
Joined: Sat 20 Mar 2010, 22:28

#530 Post by noryb009 »

Sorry, I didn't get an email notification for your message :(

The simple answer: no, you don't need to worry about that.

The detailed answer:

The only thing I can think of possibly happening is a ransomware locking down your save file. But even then, a lot of ransomwares only care about stuff in "My Documents", since that's where the user's data usually is. Encrypting everything on hard drives would just make encrypting and decrypting take a lot longer.

There's a theoretical attack of malware detecting a Linux install and modifying it. However, since LICK-style installs are so rare, it's more likely that a malware would search for an EXT4 partition and change things there.

Post Reply