How to use Lick in Linux?

[boof]

hp 250 g4 no os, uefi boot, want puppy only. uefi iso's appear to just contain lick, rather than true uefi boot. do noy know how to run lick in linux.

[Geek3579]

Im not sure what you are trying to do. More details wouldhelp.

Is there an existing Windows installation on your computer, or is it a blank or unformatted HDD?

What puupy OS and what install process are you attempting ?

[mikewalsh]

@boof :-

Boof, you really have got to start supplying more detail in your posts. Your short, almost "text-style" posts are so abbreviated & hard to read that it's not surprising you don't get much help. Nobody can understand you..!!!

Mike.

[boof]

i'm booting a new, non windows install with fossapup64. need info on setting up sda and how to use wine to install the os and ufei boot tks nb iso is currently corrupted? uefi boot files from bionicpuo32 uefi iso.

[Flash]

Boof suffers from the 'curse of knowledge.'

[williams2]

When you first boot FossaPup (there is no save file)
if the wallpaper seems to be corrupted
and if the menu seems to not work properly,
then you should check the iso file with md5sum (probably using a good Puppy)

Open a text terminal (click the desktop "Console" icon.
then cd to where the iso file is located, like this:

Code: Select all

cd /tmp/
md5sum fossapup64-9.5.iso 
6a45e7a305b7d3172ebd9eab5ca460e4  fossapup64-9.5.iso

If the md5sum number is the same as the correct number that is on the webpage where you downloaded the iso file from,
then the iso file is good.

If the md5ssum number is different, then the iso file is bad and you need to download it again.

If the iso file is good, then you need to check the device you copied the iso file to.
You need to know exactly how big the iso file is. ls -s will tell you. Like this:

Code: Select all

ls -s fossapup64-9.5.iso 
418816 fossapup64-9.5.iso
#
dd if=fossapup64-9.5.iso bs=1024 count=418816 | md5sum
6a45e7a305b7d3172ebd9eab5ca460e4  -
#
dd if=/dev/sr0 bs=1024 count=418816 | md5sum
6a45e7a305b7d3172ebd9eab5ca460e4  -

dd if=fossapup64-9.5.iso ... and dd if=/dev/sr0 ... should give you the same md5sum number, if /dev/sr0 is the device that the iso file was copied to.

/dev/sr0 is typically a cd or dvd disc.
A usb flash drive is typically /dev/sdb or /dev/sdc

If the md5sum of the iso file and the md5sum number of the block device are the same, then the iso copied properly to the block device.
If the md5sum numbers are different, then you need to reinstall the iso file on the drive.

[boof]

i have uefi boot notebook, cant disable it for sda. used to have win10 installed.
sda1 512MB fat32 boot, exx
sda2 200GB btfs
sda3 170GB ext3

all empty

and flashdrive

sdb1 512MB fat32 boot, exx grub for DOS installed
sdb1 14GB ext3 bionic32 with uefi installed
sdb3 12GB ext3 xenialpup with uefi installed

uefi booting not installed, just in the packages.
have wine-stable-3.0 installed on sdb2
xenial64 iso and /Windows-_Installer/lick.exe in /mnt/home/
pls provide styntax for wine-stable /path/lick.exe.
lick.exe is 32bit, is it ik to use 64bit wine?
want to install linux on sda2. do not have windows oem boot files, lost backup pendrive.
delivered without suthentication certificate some years ago.
is it a linux path or a windows path?

i will test fossapup64 iso later. i suspect the iso is corrupted at source, not from download.
edit
md5 same.
thx

[williwaw]

want to install linux on sda2. do not have windows oem boot files, lost backup pendrive.
delivered without suthentication certificate some years ago.

is secure boot turned off in bios?

all empty

perhaps use gparted to make a new msdos partition table and re -partition sda?

"LICK is a method to install Linux distributions from inside Windows. "

use gparted and the installer on a fossa usb or cd

[bigpup]

Note:
Not sure why you have a partition formatted btrfs.
But Puppy does not come setup to support it.

Screenshot(3).jpg (14.27 KiB) Viewed 566 times

.
.
.
Lick is not designed to do what you want to do.
It is a program, to use in Windows, to do a duel OS install, with Puppy and Windows.

Boot with the Bionicpup USB and use the installers in it to do the install.

If all you want is Puppy on this internal drive and the only OS on the computer (no Windows).

The Frugalpup Installer is getting to be the one and only installer to use.
Download it, install in Bionicpup, and use it to do installs.
viewtopic.php?f=105&t=337

Drive labels are going to depend on number of drives on the computer.
So, you do need to be careful to select the correct drive label, when offered to select.

This is what I do.

Use Gparted program.
Note:
Can leave the partition table as is or do a new one. Doing a new one, for sure, will delete everything on the drive and start fresh.
If Windows was on the drive.
At least delete all partitions and make fresh new ones.

Setup the internal drive with 2 partitions.
First one, small 300MB, fat32 format, flagged boot. (location for boot loader files, boot partition)
Rest of drive, whatever other partition(s), but one ext3 or 4 format. (location to put frugal installs)
(this is UEFI standard requirement, and some computers, look for a fat32 partition, for boot loader files)
This is also OK Legacy bios.

Run Frugalpup Installer main program.
On the main window are selection buttons.
Select the Puppy button, to do the install.
Go through install process, selecting to install to the ext formatted partition.
Note:
When selecting the partition to install to.
A window pops up, giving option to make a directory, to put the frugal install in.
I make this directory and usually name it, the name of the Puppy version.
Carefully read that windows info.
Press enter, makes the directory, not the OK button.
complete the install.

When it gets back to the main Frugalpup window.
Select the boot button.
Select the location of the frugal install, on the internal drive.
Select the small 300MB partition, as location to install the boot loader. (may need to scroll the selection window)
Select the boot loader type.
UEFI
mbr ->legacy bios boot
both

You can install the UEFI for UEFI computers, mbr for legacy bios computers, or both, to boot anything.

The UEFI will also install the needed files, to support secure boot enabled in UEFI.

When you first boot the drive, on a UEFI computer, with secure boot enabled.
A process will start, to allow you to install the Puppy security key, to the computer.
It will add this Puppy key, to the other ones, loaded on the computer.

To put more frugal installs on the same drive.
Do the complete Frugalpup Installer process again, for the new Puppy version.
When you run the boot loader install.
It will make entries, for all installs it finds, on the drive.

[boof]

BIGPUP:
thank you, that sorted fossapup64. easy really.

I think I can get older lappy to load win7.iso from sd card in usb port with adapter without driver problems. then install bionic32.

[boof]

installing boot was with uefi and legacy via grub2.
hp 250 g4 demands same files as windows oem bootup systems, tho; lick worked with win10. booting sda now requires 'legacy boot order active' with internal hard drive a choice. 'uefi boot' can only choose oem boot files for hard drive. they are not the same file/directory names? usb boot requires legacy on.
i cannot tell whether the boot is actually uefi or legacy, but it works,