Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Fri 24 May 2019, 13:22
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
Puppy Linux Windows Installer - LICK v1.3.3 released
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 35 of 36 [538 Posts]   Goto page: Previous 1, 2, 3, ..., 33, 34, 35, 36 Next
Author Message
noryb009

Joined: 20 Mar 2010
Posts: 618

PostPosted: Mon 17 Dec 2018, 22:31    Post subject:  

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:
  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.
Back to top
View user's profile Send private message 
Donncha

Joined: 02 Oct 2011
Posts: 34

PostPosted: Tue 18 Dec 2018, 11:28    Post subject:  

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 Embarassed
Don
Back to top
View user's profile Send private message 
noryb009

Joined: 20 Mar 2010
Posts: 618

PostPosted: Tue 18 Dec 2018, 15:58    Post subject:  

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!
Back to top
View user's profile Send private message 
Ron911

Joined: 22 Feb 2019
Posts: 16

PostPosted: Fri 22 Feb 2019, 09:14    Post subject: Problem with LICK and Fatdog 64 om Acer Aspire 1 A111
Subject description: Cannot load Base SFS
 

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
Back to top
View user's profile Send private message 
noryb009

Joined: 20 Mar 2010
Posts: 618

PostPosted: Fri 22 Feb 2019, 14:54    Post subject:  

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:
initrd /whatever/initrd-nano.xz

to
Code:
initrd /whatever/initrd


In the mean time, I've created an issue, I'll try to fix it soon.
Back to top
View user's profile Send private message 
Ron911

Joined: 22 Feb 2019
Posts: 16

PostPosted: Sat 23 Feb 2019, 03:47    Post subject:  

Hi Noryb009,

That did it!
I can now boot into Fatdog64 without a problem.
Thank you very much for your help and tool.
Ron
Back to top
View user's profile Send private message 
noryb009

Joined: 20 Mar 2010
Posts: 618

PostPosted: Sat 23 Feb 2019, 14:17    Post subject:  

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.
Back to top
View user's profile Send private message 
Ron911

Joined: 22 Feb 2019
Posts: 16

PostPosted: Thu 07 Mar 2019, 03:50    Post subject:  

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
Back to top
View user's profile Send private message 
jamesbond

Joined: 26 Feb 2007
Posts: 3347
Location: The Blue Marble

PostPosted: Thu 07 Mar 2019, 10:02    Post subject:  

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:
## 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
Quote:
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:
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, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.
Back to top
View user's profile Send private message 
Ron911

Joined: 22 Feb 2019
Posts: 16

PostPosted: Sat 09 Mar 2019, 05:36    Post subject:  

Hi JamesB,

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

Ron
Back to top
View user's profile Send private message 
number77

Joined: 22 Oct 2010
Posts: 728

PostPosted: Wed 27 Mar 2019, 14:07    Post subject:  

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
Back to top
View user's profile Send private message 
noryb009

Joined: 20 Mar 2010
Posts: 618

PostPosted: Thu 28 Mar 2019, 00:21    Post subject:  

Windows doesn't have the ability to read from or write to ext4 drives, so LICK won't help you in your case. Sorry!
Back to top
View user's profile Send private message 
number77

Joined: 22 Oct 2010
Posts: 728

PostPosted: Thu 28 Mar 2019, 05:00    Post subject:  

Thanks norby009, I will put up with ntfs. Lick is pretty amazing and easy to use, thanks for it.
number77
Back to top
View user's profile Send private message 
bigpup


Joined: 11 Oct 2009
Posts: 12146
Location: S.C. USA

PostPosted: Thu 28 Mar 2019, 07:34    Post subject:  

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 Shocked
YaPI(any iso installer) http://www.murga-linux.com/puppy/viewtopic.php?t=107601
Back to top
View user's profile Send private message 
tallboy


Joined: 21 Sep 2010
Posts: 1339
Location: Oslo, Norway

PostPosted: Thu 28 Mar 2019, 10:39    Post subject:  

number77 wrote:
Lick is pretty amazing and easy to use, thanks for it.
I totally agree! Very Happy
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.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 35 of 36 [538 Posts]   Goto page: Previous 1, 2, 3, ..., 33, 34, 35, 36 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0550s ][ Queries: 13 (0.0113s) ][ GZIP on ]