Puppy Linux Windows Installer - LICK v1.3.3 released
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
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
There are third party programs that can read/write to ext formats in Windows.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!
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
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected

YaPI(any iso installer)
I totally agree!number77 wrote:Lick is pretty amazing and easy to use, thanks for it.

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.
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.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?
Linux distros use NTFS-3G, which is open source.But somehow I don't feel safe with ntfs as its microsoft.
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).
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.
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.

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.
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".
-
- Posts: 120
- Joined: Thu 11 May 2017, 13:42
I tried changing the default to 1 but Windows XP still the first option and Tahrpup second.noryb009 wrote:Find the file C:/lickgrub.cfg (if you installed LICK to another drive, this might be on that drive) (if this file doesn't exist, let me know). In that file, change "set default=0" to "set default=1" (or the number of times you want it to automatically press "down" for you)
Code: Select all
## start header
insmod part_gpt
insmod part_msdos
insmod ntfs
set timeout=5
set default=1
insmod all_video
if loadfont /grub/fonts/unicode.pf2 ; then
set gfxmode=auto
set gfxpayload=keep
terminal_output gfxterm
fi
menuentry "Windows" {
insmod chain
search --set=root --file /EFI/Microsoft/boot/bootmgfw.efi
chainloader /EFI/Microsoft/boot/bootmgfw.efi
}
## end header