(OLD) (ARCHIVED) Puppy Linux Discussion Forum Forum Index (OLD) (ARCHIVED) Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info

This forum can also be accessed as http://oldforum.puppylinux.com
It is now read-only and serves only as archives.

Please register over the NEW forum
https://forum.puppylinux.com
and continue your work there. Thank you.

 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups    
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sat 05 Dec 2020, 18:31
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
Puppy Linux Windows Installer - LICK v1.3.3 released
Moderators: Flash, JohnMurga
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies. View previous topic :: View next topic
Page 39 of 40 [593 Posts]   Goto page: Previous 1, 2, 3, ..., 37, 38, 39, 40 Next
Author Message
DuMar

Joined: 28 Jan 2016
Posts: 79
Location: Apeldoorn, Netherlands

PostPosted: Thu 30 Apr 2020, 02:56    Post subject:  

Thank you noryb009,

I managed to get the machine going with the newest fossapup.

However I made a mistake by installing lick after a windows system repair without shutting the machine down first. Now here is no windows entry anymore in lickgrub. All the windows data is there. I can't start the machine anymore in windows.

This how my lickgrub.cfg looks.

## start section fossapup64-9.0.1
menuentry 'fossapup64 9.0.1' {
search --set=root --file /fossapup64-9.0.1/vmlinuz
linux /fossapup64-9.0.1/vmlinuz pfix=fsck psubdir=fossapup64-9.0.1
initrd /fossapup64-9.0.1/initrd.gz
}

menuentry 'fossapup64 9.0.1 (no save file)' {
search --set=root --file /fossapup64-9.0.1/vmlinuz
linux /fossapup64-9.0.1/vmlinuz pfix=ram savefile=none psubdir=fossapup64-9.0.1
initrd /fossapup64-9.0.1/initrd.gz
}
## end section fossapup64-9.0.1

Can somebody complete it for me with the part about windows that belongs to the top of this?
Back to top
View user's profile Send private message 
noryb009

Joined: 20 Mar 2010
Posts: 636

PostPosted: Thu 30 Apr 2020, 04:29    Post subject:  

Hi again DuMar,

The default beginning to lickgrub.cfg can be found here. You should be able to add everything in that file before your current contents.

I'll try to figure out what went wrong. Lick should be safe to use whenever, it looks like you fell into an edge case that isn't handled correctly.
Back to top
View user's profile Send private message 
DuMar

Joined: 28 Jan 2016
Posts: 79
Location: Apeldoorn, Netherlands

PostPosted: Thu 30 Apr 2020, 06:44    Post subject:  

Thank ypu noryb009,

That worked very well, I now have the option for windows in the menu. Not that I intend to use it a lot Laughing

I was not familiar with Lick, I use puppy since tahrpup. I always used frugal from USB stick. I'm very used to that and it works great.

But I think this is the future for Puppy Linux to be used on the newest machines. It's not possible anymore to make a machine like I have now boot from USB.

So suddenly I became a sort of testing Fossapup. I will continue in that topic and I hope that soon we have a nice and new and save new puppy member to work with.

Thnx for your help so far.

Kind regards, Marc
Back to top
View user's profile Send private message 
jake29

Joined: 24 Jul 2015
Posts: 253

PostPosted: Sat 02 May 2020, 04:53    Post subject:  

Hi noryb009.

My apologies for the delay in replying. I have since done another clean install of Windows and the issue did not occur this time. The origin of the problem - I believe - was due to the configuration of this PC. I have a boot SSD and a data HDD. I normally disconnect the HDD prior to installing Windows / Linux, but it appears on this occasion I had not done so. This resulted in Windows Boot Manager being installed on the HDD and I suspect was the cause of the error.

Thanks for taking the time to look into this.

Jake
Back to top
View user's profile Send private message 
DuMar

Joined: 28 Jan 2016
Posts: 79
Location: Apeldoorn, Netherlands

PostPosted: Sun 03 May 2020, 08:27    Post subject:  

I installed Lick now on my other laptop, an Acer with windows 7.

When the machine boots I first have a choice between windows and Lick.
When I choose lick I get a new menu to make a choice between the installed Puppy versions.

I would like to change the first menu so it picks Lick after 5 seconds instead of windows.

How can I do that?
Back to top
View user's profile Send private message 
noryb009

Joined: 20 Mar 2010
Posts: 636

PostPosted: Sun 03 May 2020, 15:37    Post subject:  

Jake, thanks for the info. It sounds like I haven't tested LICK with a configuration similar to yours, so one of the pre checks or checks during installation saw something it didn't expect, so everything was reversed. Unfortunately, finding and testing these more exotic setups is time consuming and usually doesn't benefit many people, so I have avoided doing much for them. However, your setup seems like it might be common, so I'll try to replicate it some time.

Marc: Follow this video, but look for the description of "LICK boot loader".
Back to top
View user's profile Send private message 
charlie6


Joined: 30 Jun 2008
Posts: 1231
Location: Saint-Gérard / Walloon part of Belgium

PostPosted: Fri 12 Jun 2020, 10:55    Post subject: no file C:/lickgrub.cfg and no dual boot on win10  

Hi noryb009,
This is my first trial to run a dual boot on a windows OS!

I have installed LICK-1.3.3.exe on win10 with UEFI setting (..I believe, as the "Legacy" label is greyed in the settings window);
then copied the xenialpup64-8.0.iso in C:/;
got xenialpup64-8.0 installed as explained here http://www.murga-linux.com/puppy/viewtopic.php?p=1013295#1013295;
everything looks to be at the right place ...

... BUT ... the PC keeps rebooting on win10.
and no file C:/lickgrub.cfg has been created.

I resist to apply the workaround under "Nothing happens on reboot" in the LICK gui, because I don't have any liveCD (and till now don't want to... Confused ).

And prefer to ask you what to do to eventually fix it.

Thanks in advance for your time!

Charlie
Back to top
View user's profile Send private message 
charlie6


Joined: 30 Jun 2008
Posts: 1231
Location: Saint-Gérard / Walloon part of Belgium

PostPosted: Mon 15 Jun 2020, 03:09    Post subject:  

Hi again,
here are some more details with screenshots following my above post:
1. win10 does not start anymore when BIOS setup to UEFI: "NO BOOTABLE DEVICES" comment; pressing F1 does nothing.
The bios setup does not display the boot sequence when set to UEFI (I dont know if something is missing...?)
2. win10 starts when BIOS setup to Legacy; from my previous post above, digging into the BIOS and the setup NIC entry to "enabled" (do not why it was set otherwise...!) allowed to get displayed the dual boot screen win10 versus LICK Very Happy !
From win10 cmd.exe, the bcdedit command displays "Lick Boot loader" description (see one among the previous nooryb009's posts)
3. then choosing "LICK boot loader" results in an error message telling "windows could not start ....file: \pupldr.mbr could not be loaded ... errors"
4. choosing "Windows10" could start win10 (...if the BIOS was previosly set to Legacy). Then the LICK gui and the LICK command line tools are available.
(NB: the bionicpup64-8.0.iso laready has been copied to C:/ )
4.1. Using the LICK gui: doing File/Install Boot loader opens a dialog box "...want to install boot loader?" Answer "Yes" then...
4.2. ...displayed another box "Error installing loader! Error changing boot menu to Legacy"
question: does it mean that the boot has to be set to UEFI?
4.3. Using the LICK command line results in "Error installing the boor loader"

The boot loader cannot be created.
I suspect a possibly wrong win10 configuration as it won't boot UEFI; but no idea as now on how to fix it.

Any help on how to fix this will be very appreciated Smile.
Thanks in advance therefore.
Charlie
win10biosuefi.JPG
 Description   1.
 Filesize   26.9 KB
 Viewed   366 Time(s)

win10biosuefi.JPG

win10_nobootdev.JPG
 Description   1.
 Filesize   17.47 KB
 Viewed   367 Time(s)

win10_nobootdev.JPG

win10biosLegacy.JPG
 Description   2.
 Filesize   29.48 KB
 Viewed   369 Time(s)

win10biosLegacy.JPG

win10-LICKscreen.JPG
 Description   2.
 Filesize   15.61 KB
 Viewed   368 Time(s)

win10-LICKscreen.JPG

win10-pupldr.JPG
 Description   3.
 Filesize   47.33 KB
 Viewed   371 Time(s)

win10-pupldr.JPG

LICKgui_instBoLo.png
 Description   4.1.
 Filesize   61.89 KB
 Viewed   371 Time(s)

LICKgui_instBoLo.png

LICKgui_error_Legacy.png
 Description   4.2.
 Filesize   56.39 KB
 Viewed   372 Time(s)

LICKgui_error_Legacy.png

LICKcdline_error2.png
 Description   4.3.1.
 Filesize   10.06 KB
 Viewed   372 Time(s)

LICKcdline_error2.png

LICKcdline_error2.png
 Description   4.3.2
 Filesize   10.06 KB
 Viewed   370 Time(s)

LICKcdline_error2.png

Back to top
View user's profile Send private message 
charlie6


Joined: 30 Jun 2008
Posts: 1231
Location: Saint-Gérard / Walloon part of Belgium

PostPosted: Mon 15 Jun 2020, 03:22    Post subject:  

Hi again...
ooops....wrong 4.3.1. screenshot above Confused
here is the right 4.3.1. screenshot

to mention: on the screenshot, the windows header tells:
Quote:
C:/Program Files....\lick-cli.exe

and not
Quote:
C:/Administrator\Program Files....\lick-cli.exe


Any matter?

Sorry therefore, Charlie
LICKcdline_error1.png
 Description   4.3.1.
 Filesize   31.38 KB
 Viewed   358 Time(s)

LICKcdline_error1.png

Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 2075
Location: not Bulgaria

PostPosted: Mon 15 Jun 2020, 03:53    Post subject: Re: Puppy Linux Windows Installer - LICK v1.3.3 released
Subject description: Package your puppy as a .exe Windows installer
 

noryb009 wrote:
LICK is developer-friendly: If you want to bring the power of LICK to your application or distribution, a command line utility and a library are available. LICK is licensed under the MIT license, so feel free to use it however you like.


Whilst I myself never use Windows and don't have any version on my machine I am interested to know if LICK could be easily modified to provide dual booting with Windows for WeeDogLinux, which does not come as an iso, but instead builds the initrd.gz and squashfs files required for booting in a directory along with its vmlinuz kernel.

https://weedoglinux.rockedge.org

I'm not asking you to look into this nory since I appreciate you only support Puppy distro and from iso only(?) but I just want to ascertain if you think it is reasonably possible for your scheme to work with other Linux (after some mods I guess) that is in the non-iso form I described. If so, I might look into your system further. Having said that, I wouldn't want to support its use in WeeDogLinux since I would be worried to break anyone's Windows install and get the blame for it! So many things could go wrong...

cheers,

wiak

_________________
WeeDogLinux forum: https://weedoglinux.rockedge.org/viewforum.php?f=4
Tiny Linux Blog: https://www.tinylinux.info/
Check Firmware: http://murga-linux.com/puppy/viewtopic.php?p=1022797
Back to top
View user's profile Send private message 
charlie6


Joined: 30 Jun 2008
Posts: 1231
Location: Saint-Gérard / Walloon part of Belgium

PostPosted: Tue 16 Jun 2020, 03:17    Post subject: pupl.exe error  

Hi,
digging a bit deeper into my quest for getting puppy running on windows10...
using LICK-1.3.3.
I got the following message running (see screenshot)
Code:
C:\Program Files (x86)\lick\res>pupl.exe

Quote:
(brief translation)
16 bits application not handled
Impossible to start nor execute the program ...
...blablibla...«C:\...\pupl.exe» ...incompatibility with Windows 64 bits...
...please contact developper...

Does anyone get an analog result?

Lasr edited: also got the same messages using LICK-1.3.2.
Thanks for any answer Smile
Charlie
pupldrDORexeERROR.png
 Description   pupl.exe error
 Filesize   183.44 KB
 Viewed   299 Time(s)

pupldrDORexeERROR.png

Back to top
View user's profile Send private message 
noryb009

Joined: 20 Mar 2010
Posts: 636

PostPosted: Sun 21 Jun 2020, 16:41    Post subject:  

Hi charlie6,

First, sorry that I didn't respond earlier, I never got an email notification from the forum Sad

The pupl.exe is not for your system, it's only used for Windows 95/98/ME. I'm not surprised it gives an error on Windows 10.

pupldr.mbr is only created if LICK thinks your system uses BIOS mode (not UEFI). The "Error changing boot menu to Legacy" also only occurs if LICK thinks your system uses BIOS.

I'm a little surprised that there is a Windows 10 machine that doesn't use UEFI mode (although, it looks like it's simply disabled on your machine). I'm not sure if I tested this configuration recently, I'll try it out some time soon and see if I run into the same issues as you.

In the mean time, you might be able to convert your system to use UEFI, but there's no guarantee that this will work well. If you want to try this, this looks like a good starting place, but you may have issues, either with Windows or with LICK afterwards.
Back to top
View user's profile Send private message 
noryb009

Joined: 20 Mar 2010
Posts: 636

PostPosted: Sun 21 Jun 2020, 16:45    Post subject:  

wiak,

If the squashfs/initrd.gz/vmlinuz can boot from a directory on an NTFS drive, it should work. There's a way to install from a directory, just give the directory when it asks for an ISO, I suspect that will work for you.

Other distros are half supported by LICK - there's support in the library for them, but not in the UI. This is an example distro configuration file, it uses a blacklist of files to not copy (in distro_puppy_filter) and fills a distro_info_node_t struct with some simple info (path of vmlinuz, initrd, and options for the initrd).
Back to top
View user's profile Send private message 
charlie6


Joined: 30 Jun 2008
Posts: 1231
Location: Saint-Gérard / Walloon part of Belgium

PostPosted: Tue 23 Jun 2020, 23:46    Post subject:  

noryb009 wrote:
Hi charlie6,
... If you want to try this, this looks like a good starting place, but you may have issues, either with Windows or with LICK afterwards.


Hi noryb009!
Thanks a lot for your much appreciated post! And for the explanations. I've learned a bit more about what UEFI consists of.

I'll give it a try soon and return results.
Best regards, Charlie
Back to top
View user's profile Send private message 
charlie6


Joined: 30 Jun 2008
Posts: 1231
Location: Saint-Gérard / Walloon part of Belgium

PostPosted: Wed 24 Jun 2020, 00:56    Post subject:  

Hi nooryb009,

applying the instructions from the given link, I got:
Quote:
X:\windows\system32\>mbr2gpt /validate
MBRGPT: Attempting ...disk 0
MBRGPT: Rertrieving ...disk 0
MBRGPT: Validating ...disk size is: 512 bytes
Cannot find OS partition(s) for disk 0


I also googled the web and found this link:
https://medium.com/@revanmj/one-way-to-fix-mbr2gpt-cannot-find-os-partition-33631dfd9f5e

While in command line I have tried to save the %windir%/setupact.log file by copying it to %windir%/setupact.log.txt back.
But after shutdown and restart of windows 10, I could not find that setupact.log.txt file

According that link, I then do the command:
Quote:
X:\windows\system32\>reagentc /info

which returns that the command reagent is unknown

Thansk again for your time!
Charlie
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 39 of 40 [593 Posts]   Goto page: Previous 1, 2, 3, ..., 37, 38, 39, 40 Next
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies. 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.3299s ][ Queries: 12 (0.1609s) ][ GZIP on ]