(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:56
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 40 of 40 [593 Posts]   Goto page: Previous 1, 2, 3, ..., 38, 39, 40
Author Message
wiak

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

PostPosted: Wed 24 Jun 2020, 02:46    Post subject:  

noryb009 wrote:
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).


Thanks nory, I'll give it a try sometime.

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: Wed 24 Jun 2020, 16:29    Post subject:  

Hi nooryb009,
The following might help for understanding ... Rolling Eyes
About my windows 10 session: in year 2016, I bought as second hand that PC (Dell) with windows 10 installed (bought in a very professional shop that refurbishs and reconfigures PCs).

Since, it got several updates automatically.

I remember (but forgot how...) once having set the system in order to be able to acces read-write the hdd partitions (i.e. sda1 and sda2) using a puppy live-cd. I did that trick just one time.

Now I run bionicpup64-8.0 on that PC (with BIOS set to "Legacy") using a usb key. I then noticed sda1 and sda2 are read-only mounted.
I used that windows 10 PC for running some specific graphic apps for my job.

HTH, 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: Thu 25 Jun 2020, 03:09    Post subject: cannot get «secure boot» enabled on windows 10  

Hi noryb009,
attached the command line comments when running ReAgentc from cmd.exe inside the windows 10 graphic environment
Quote:
C:\WINDOWS\system32>ReAgentc /info


to notice: while in the TROUBLESHOOT environment, the 'reagentc' command does not start: I get:
Quote:
X:\windows\system32>reagentc /info
'reagentc' not recognized as external nor internal command, executable program nor command file


last edited:
Another issue: I cannot get «secure boot» enabled anymore on windows 10
I have googled the web, found some tutorials to fix this; but once in TROUBLESHOOT environment command line, I get the same comment as above when running a command...!?
Thanks in advance for any help!
Best regards, Charlie
reagentc.png
 Description   
 Filesize   89.13 KB
 Viewed   319 Time(s)

reagentc.png

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

Joined: 20 Mar 2010
Posts: 636

PostPosted: Sat 27 Jun 2020, 18:14    Post subject:  

Hi Charlie,

Your system configuration seems a bit odd. Could you run Command Prompt as an admin, and copy/paste the output of:

Code:
bcdedit


I'm mostly interested if there's a section about LICK, and what the normal boot procedure uses (paths that end with a EFI extension or not).
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 29 Jun 2020, 02:44    Post subject:  

Hi noryb009,
I'm happy reading from you! Smile
Here is the copy/paste of the bcdedit run from command line (cmd.exe as Admin. rights):
Quote:
Microsoft Windows [version 10.0.18362.900]
(c) 2019 Microsoft Corporation. Tous droits réservés.

C:\WINDOWS\system32>bcdedit

Gestionnaire de démarrage Windows (translated: windows boot manager)
---------------------------------
identificateur {bootmgr}
device partition=C:
description Windows Boot Manager
locale fr-FR
inherit {globalsettings}
resumeobject {1cf20c12-41c5-11ea-89b3-ebdcf1a75ae2}
displayorder {current}
{1a1f5534-b9d1-11ea-83a0-18037345ff4c}
toolsdisplayorder {memdiag}
timeout 5

Chargeur de démarrage Windows (translated: windows boot loader)
-----------------------------
identificateur {current}
device partition=C:
path \WINDOWS\system32\winload.exe
description Windows 10
locale fr-FR
inherit {bootloadersettings}
recoverysequence {aa34709e-b6b2-11ea-8397-18037345ff4c}
displaymessageoverride CommandPrompt
recoveryenabled Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {1cf20c12-41c5-11ea-89b3-ebdcf1a75ae2}
nx OptIn
bootmenupolicy Legacy

Secteur de démarrage en mode réel (translated: real mode boot sector)
---------------------------------
identificateur {1a1f5534-b9d1-11ea-83a0-18037345ff4c}
device partition=C:
path \pupldr.mbr
description LICK Boot Loader

C:\WINDOWS\system32>


Thanks again! Charlie
Back to top
View user's profile Send private message 
noryb009

Joined: 20 Mar 2010
Posts: 636

PostPosted: Tue 30 Jun 2020, 00:51    Post subject:  

So assuming that the boot menu shows up (let me know if it doesn't) and trying to boot LICK still returns the error "file: \pupldr.mbr could not be loaded" (let me know if it doesn't):

I originally saw this error when trying to run the BIOS install method on UEFI systems. At the time I thought the error was from Windows not being able to chainload from a UEFI to pupldr.mbr correctly, but since it's happening on your system, it might be that the system UEFI can't run pupldr.mbr correctly.

Unfortunately, I think the only way LICK could work on your system is if you can switch it to a UEFI system, which I know you're running into issues with, and I unfortunately cannot help with those issues, since I don't know enough about what that program is trying to do.
Back to top
View user's profile Send private message 
bigpup


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

PostPosted: Tue 30 Jun 2020, 02:16    Post subject:  

charlie6,

After running Lick in Windows to do the install.
Did you do a complete normal shutdown of Windows 10?

I know if you shutdown Windows 10 in hibernation.
It will cause all kinds of strange problems, trying to do anything but boot Windows 10.
I have no idea how it could or would not affect Lick, but just an idea to consider.

_________________
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)
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 30 Jun 2020, 03:13    Post subject:  

Hi noryb009 and bigpup Wink !
Thanks for your replies!
noryb009 wrote:
...
I originally saw this error when trying to run the BIOS install method on UEFI systems. At the time I thought the error was from Windows not being able to chainload from a UEFI to pupldr.mbr correctly, but since it's happening on your system, it might be that the system UEFI can't run pupldr.mbr correctly.
...

About UEFI: my current Win10 system cannot boot any longer on UEFI (which was the case before I might have done something..."wrong" but I do not remember how/what :-/) So I believe my Win10 needs some "repair", and perhaps a reinstall. Unfortunatelly I have no rescue disk...but only a disk image I have saved upon PC purchase on an external usb HDD.

bigpup wrote:
...Did you do a complete normal shutdown of Windows 10? ...

Thanks bigpup! I have already read your previous about this among this thread, and took care to each time do a complete shutdown (Menu/Shutdown) of Win10.

Again tons of thanks to you both for your time!
Best regards, Charlie (! 12 years running Puppy today! Very Happy )
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 40 of 40 [593 Posts]   Goto page: Previous 1, 2, 3, ..., 38, 39, 40
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.0837s ][ Queries: 12 (0.0434s) ][ GZIP on ]