Using Lick installer, i think i permanatly modified important files and cant install fossapup

[fixedfury505]

help! i cant get rid of the LICK bootup and cant install! i am really in a panic hoping i didnt just trash my computer. when i try to boot into linux (i did "install" with lick) its a black screen with a line (like the line in cmd) but it dosent blink and freezes my computer. im really worried for my computer i dont want to destroy it. ive tried 5 times but i can boot into windows like i did just now. please reply fast

[Phoenix]

• Where is menu.lst, grub.cfg, etc? What's in it?

• As well where is the puppy located at?

• Also what puppy?

[fixedfury505]

• Where is menu.lst, grub.cfg, etc? What's in it?

• As well where is the puppy located at?

• Also what puppy?

well, i dint exactly know, im just really in a panic. and fossapup

[wiak]

• Where is menu.lst, grub.cfg, etc? What's in it?

• As well where is the puppy located at?

• Also what puppy?

well, i dint exactly know, im just really in a panic. and fossapup

Main thing at this stage is to avoid that 'panic' (though it is understandable) and don't hack away at your system trying to fix it - the more you change the more difficult anyone on this forum will find it to get you out of the situation. I'm not myself an expert on dual-booting with Windows whatsoever, but plenty others on this forum are.

What you should do at the moment is post as many technical details as you can about your system, what is installed onto it, and in as much detail all the steps you did that resulted in the issue. The more accurate your technical report is the easier anyone who knows how to fix it will find things (i.e. fix will come quicker). Hard to do, but be patient, relax and ignore the feeling of panic - if you haven't dropped the machine or hit the screen with a hammer chances are someone will manage to help you recover it fully.

[Phoenix]

You still assuredly has windows so all of the questions given are answerable. Any extra details though are appreciated! Don't panic, and calm down. Your data won't go anywhere until you chose so.

[fixedfury505]

• Where is menu.lst, grub.cfg, etc? What's in it?

• As well where is the puppy located at?

• Also what puppy?

well, i dint exactly know, im just really in a panic. and fossapup

Main thing at this stage is to avoid that 'panic' (though it is understandable) and don't hack away at your system trying to fix it - the more you change the more difficult anyone on this forum will find it to get you out of the situation. I'm not myself an expert on dual-booting with Windows whatsoever, but plenty others on this forum are.

What you should do at the moment is post as many technical details as you can about your system, what is installed onto it, and in as much detail all the steps you did that resulted in the issue. The more accurate your technical report is the easier anyone who knows how to fix it will find things (i.e. fix will come quicker). Hard to do, but be patient, relax and ignore the feeling of panic - if you haven't dropped the machine or hit the screen with a hammer chances are someone will manage to help you recover it fully.

well, i first went through every distro by linux until i came to fossapup (i almost chose slackel) and downloaded. i found the read me and saw lick being recomended to use when installing. of course im gonna use what the sofware recomends me to use to do something im not used to. i fix computers as a hobby but only on the inside. never learned a lot about ghe code and os. i download and install no problem. it was very simple and i thought this was gonna be way easir than i thought. boy was i wrong! i reboot and follow the intstructions from the read me (i took a picture from my phone) nothing bad happened while i was setting up lick. i restart my computer again to run fossapup. i select fossapup in the os select screen and get all exited to check out what it didnt show in the videos aaaaaand..? black screen with that command prompt like line. i thought i was about to install like the videos but no. it froze. i tried 5 times and still nothing. the only thing i havent tried was re downloading fossapup. but im tired and ill read your responses in the morning if i have the time. thanks

[wiak]

well, i dint exactly know, im just really in a panic. and fossapup

Main thing at this stage is to avoid that 'panic' (though it is understandable) and don't hack away at your system trying to fix it - the more you change the more difficult anyone on this forum will find it to get you out of the situation. I'm not myself an expert on dual-booting with Windows whatsoever, but plenty others on this forum are.

What you should do at the moment is post as many technical details as you can about your system, what is installed onto it, and in as much detail all the steps you did that resulted in the issue. The more accurate your technical report is the easier anyone who knows how to fix it will find things (i.e. fix will come quicker). Hard to do, but be patient, relax and ignore the feeling of panic - if you haven't dropped the machine or hit the screen with a hammer chances are someone will manage to help you recover it fully.

well, i first went through every distro by linux until i came to fossapup (i almost chose slackel) and downloaded. i found the read me and saw lick being recomended to use when installing. of course im gonna use what the sofware recomends me to use to do something im not used to.

I am not the creator of LICK or Puppy Linux, fixedfury505. I'm just advising you that no-one can help you fix your problem without screenshots and technical information about how you installed LICK (I understand you followed its README exactly). Whoever has ideas to fix it needs more now than 'black screen', which really is a working in the dark situation, but hopefully someone will ask you to try some exact step by step boot procedures. I suspect you have somehow corrupted the MS Windows boot loader configuration so some sort of boot load rescue will be required. The underlying Windows OS is bound to be there, so hopefully someone knows a good reliable rescue mechanism to give you. But be careful not to innocently try every suggestion you might be given - this is just a hobby forum and some will be more expert about Windows booting than others. Certainly a tricky situation. Hoping the best for you. Supply screenshots as a first stab at providing technical info (even if just taken with a camera whilst system tries but fails to boot).

Don't expect immediate replies from potential boot experts. This is an international forum and much of the world may still be asleep and sometimes replies take a while (even a day or two if only a few are 'expert' enough at the problem being asked about). You could also try sending a Private forum Message (PM) to the creator of LICK. I forget who that is, but search for the LICK thread and that info is surely there. Be patient and most usually fixes end up being provided - just wait till you get enough relevant advice, which will surely come (but try the PM too).

[Phoenix]

Are you still able to boot to Windows? As well, can you type in this 'black screen'? Please answer the questions, in a orderly fashion. (Including the ones I've already posted. Those files are located on your C: drive by default unless changed, perhaps under a folder named fossapup or simply laying about on C:/)

If you are absolutely unable to boot into any working operating system, please press 'e' on the menu entry you wish to boot from and upload a photo of it. (Please make it clear)

[fixedfury505]

Are you still able to boot to Windows? As well, can you type in this 'black screen'? Please answer the questions, in a orderly fashion. (Including the ones I've already posted. Those files are located on your C: drive by default unless changed, perhaps under a folder named fossapup or simply laying about on C:/)

im about to post a video that should probably help a lot

[fixedfury505]

this is a unlisted video by me

[Phoenix]

Ok so yes, you'll need to press 'e' as I said and take a shot of the contents displayed from that menu entry. See you in about 9 hours!

[bigpup]

By your posted video.

Windows still boots.
The lick boot menu still works.

Lick seems to be correctly installed.

The Fossapup64 9.5 install does not boot or actually start to boot.
So something is wrong with it's install.

Possible causes:
1. Bad download of the Fossapup64 9.5 ISO.
It happens.
Delete the bad install.
A fresh new download of the ISO.
A clean new install using this new download.
Can fix it.

2. The ISO was placed in a location that had a lot of fragmentation. Thus, it fragmented the ISO package file.
Fragmentation issue can also apply to the actual install of Fossapup64.

Do you know how to run Windows defrag program to check and defrag the drive you are storing and installing on?

When you first tried to boot Fossapup64.
Did you have to do this:

UEFI Systems with Secure Boot

LICK supports secure boot, but requires a manual step during the first reboot.

On the first reboot, if you see a blue screen with writing, press enter to select OK.
Press enter again to select Enroll Hash.
Use the up and down arrow keys to highlight loader.efi, and press enter.
Press the down arrow to select Yes, then press enter.
Use the down arrow to highlight Exit, then press enter.

On subsequent reboots, these steps will not need to be taken.

[fixedfury505]

about to try again with a new download wish me luck!

[fixedfury505]

weird.. still wont work with the new download

[fixedfury505]

anyone have any other ideas? im sure im compatible

[bigpup]

If Windows 10 is on this computer.
Do not shutdown in hibernate mode.
Do a complete normal shutdown and power off.
Hibernate does not fully release control of the internal drive so other operating systems can use it.

No one Puppy Linux version is designed to work on every possible computer.

Maybe try a different Puppy Linux version.

Bionicpup64 8.0
Scpup64

If you would tell us specifically the make and model of the computer.
That is a big clue.

When using Lick to do the install.
Are you selecting to install to C drive or some other place?

You never told us if you had to do this?

On the first reboot, if you see a blue screen with writing, press enter to select OK.
Press enter again to select Enroll Hash.
Use the up and down arrow keys to highlight loader.efi, and press enter.
Press the down arrow to select Yes, then press enter.
Use the down arrow to highlight Exit, then press enter.

On subsequent reboots, these steps will not need to be taken.

You did use the latest version of Lick?
Lick v 1.3.4
You got it from here?
https://github.com/noryb009/lick/releases/tag/v1.3.4

[wiak]

this is a unlisted video by me

So grub comes up okay as the bootloader, and you have entry for Windows and another (one or two) for Fossapup. The computer is working clearly so just a problem with it finding the boot files. I don't use Windows so can't help you with that but someone should be able to (certainly the author of LICK should know) and perhaps @rockedge

When you are at that grub boot menu, you should highlight "Windows" and press key e
and post the result to this forum

Pressing key e should take you to the grub edit boot menu where we can see what grub config has in its entry for finding where the Windows system is. Hopefully someone will then see where the problem is and instruct you what to alter.

Similarly, you can later try highlight Fossapup boot entry and press key e. If Fossapup was in fact installed okay onto the drive too, then someone can help you fix the grub boot entry then to get that to also boot. But I expect you want to get Windows booting first.

[fixedfury505]

If Windows 10 is on this computer.
Do not shutdown in hibernate mode.
Do a complete normal shutdown and power off.
Hibernate does not fully release control of the internal drive so other operating systems can use it.

No one Puppy Linux version is designed to work on every possible computer.

Maybe try a different Puppy Linux version.

Bionicpup64 8.0
Scpup64

If you would tell us specifically the make and model of the computer.
That is a big clue.

When using Lick to do the install.
Are you selecting to install to C drive or some other place?

You never told us if you had to do this?

On the first reboot, if you see a blue screen with writing, press enter to select OK.
Press enter again to select Enroll Hash.
Use the up and down arrow keys to highlight loader.efi, and press enter.
Press the down arrow to select Yes, then press enter.
Use the down arrow to highlight Exit, then press enter.

On subsequent reboots, these steps will not need to be taken.

You did use the latest version of Lick?
Lick v 1.3.4
You got it from here?
https://github.com/noryb009/lick/releases/tag/v1.3.4

1. i never use hibernate mode after what it did my previous computer
2.i use a dell inspiron 7300 2 in 1
3. yes thats the exact link i used to install
4. its only going to my c drive i havent tried anything else unless i should

[wiak]

Why haven't you posted the needed result of highlighting Windows boot choice in grub menu and pressing key 'e' as Phoenix first suggeted? Or have I missed you posting the answer?

[rockedge]

I use a modified boot stanza for finding the Windows boot mechanism on dual boot systems using Grub4Dos.

Code: Select all

title Windows 10 (sda1) PBS
  uuid <your_HDD_uuid>
  chain +1

[bigpup]

After you did the Lick install of Fossapup64 9.5 and rebooted.

When you selected to boot Fossapup64.

Did you ever see this and do it?

On the first reboot, if you see a blue screen with writing, press enter to select OK.
Press enter again to select Enroll Hash.
Use the up and down arrow keys to highlight loader.efi, and press enter.
Press the down arrow to select Yes, then press enter.
Use the down arrow to highlight Exit, then press enter.

On subsequent reboots, these steps will not need to be taken.

[fixedfury505]

Why haven't you posted the needed result of highlighting Windows boot choice in grub menu and pressing key 'e' as Phoenix first suggeted? Or have I missed you posting the answer?

i did but idk what to do after that

[fixedfury505]

After you did the Lick install of Fossapup64 9.5 and rebooted.

When you selected to boot Fossapup64.

Did you ever see this and do it?

On the first reboot, if you see a blue screen with writing, press enter to select OK.
Press enter again to select Enroll Hash.
Use the up and down arrow keys to highlight loader.efi, and press enter.
Press the down arrow to select Yes, then press enter.
Use the down arrow to highlight Exit, then press enter.

On subsequent reboots, these steps will not need to be taken.

yes but then it showed it refusing to boot. ive never gotten pass that black screen

[dogcat]

Why haven't you posted the needed result of highlighting Windows boot choice in grub menu and pressing key 'e' as Phoenix first suggeted? Or have I missed you posting the answer?

i did but idk what to do after that

You did not. That info is not posted in this thread.
You are avoiding answering the question that will help you fix the issue.
Very odd that you want to reinstall everything and redownload everything when changing a line of text will probably get you where you want to go?

Let the helpers know if you do not speak english.

[Phoenix]

What I need now since we verified the computer is not toast is you to press 'e' when you have highlighted Fossapup's entry in the GRUB menu, and then send a photo of its contents!

[fixedfury505]

What I need now since we verified the computer is not toast is you to press 'e' when you have highlighted Fossapup's entry in the GRUB menu, and then send a photo of its contents!

[wiak]

I don't know grub very well really, but can't see anything particularly wrong there so maybe the OS didn't install to disk?

The following seems to be an on-one-page copy of the manual for the version of grub you are using: https://www.chedong.com/phpMan.php/info/grub

Code: Select all

16.3.64 search
--------------

 -- Command: search ['--file'|'--label'|'--fs-uuid'] ['--set' [var]]
          ['--no-floppy'] name
     Search devices by file ('-f', '--file'), filesystem label ('-l',
     '--label'), or filesystem UUID ('-u', '--fs-uuid').

     If the '--set' option is used, the first device found is set as the
     value of environment variable VAR.  The default variable is 'root'.

What about MS Windows, could you similarly highlight that grub entry and press 'e' and take photo and post? I would have thought getting MS Windows to work again would be your prime concern at the moment. Personally, I know nothing about this really - I don't use Windows and don't know what applies to only old BIOS MBR situations and what applies to modern (GPT UEFI and so on partitions) nor the difference with newer MS WIndows distro boot mechanisms that presumably LICK tries to configure.

Code: Select all

5.1.2 Chain-loading an OS
-------------------------

Operating systems that do not support Multiboot and do not have specific
support in GRUB (specific support is available for Linux, FreeBSD,
NetBSD and OpenBSD) must be chain-loaded, which involves loading another
boot loader and jumping to it in real mode.

   The 'chainloader' command (*note chainloader::) is used to set this
up.  It is normally also necessary to load some GRUB modules and set the
appropriate root device.  Putting this together, we get something like
this, for a Windows system on the first partition of the first hard
disk:

menuentry "Windows" {
	insmod chain
	insmod ntfs
	set root=(hd0,1)
	chainloader +1
}

[fixedfury505]

I don't know grub very well really, but can't see anything particularly wrong there so maybe the OS didn't install to disk?

The following seems to be an on-one-page copy of the manual for the version of grub you are using: https://www.chedong.com/phpMan.php/info/grub

Code: Select all

16.3.64 search
--------------

 -- Command: search ['--file'|'--label'|'--fs-uuid'] ['--set' [var]]
          ['--no-floppy'] name
     Search devices by file ('-f', '--file'), filesystem label ('-l',
     '--label'), or filesystem UUID ('-u', '--fs-uuid').

     If the '--set' option is used, the first device found is set as the
     value of environment variable VAR.  The default variable is 'root'.

What about MS Windows, could you similarly highlight that grub entry and press 'e' and take photo and post? I would have thought getting MS Windows to work again would be your prime concern at the moment. Personally, I know nothing about this really - I don't use Windows and don't know what applies to only old BIOS MBR situations and what applies to modern (GPT UEFI and so on partitions) nor the difference with newer MS WIndows distro boot mechanisms that presumably LICK tries to configure.

Code: Select all

5.1.2 Chain-loading an OS
-------------------------

Operating systems that do not support Multiboot and do not have specific
support in GRUB (specific support is available for Linux, FreeBSD,
NetBSD and OpenBSD) must be chain-loaded, which involves loading another
boot loader and jumping to it in real mode.

   The 'chainloader' command (*note chainloader::) is used to set this
up.  It is normally also necessary to load some GRUB modules and set the
appropriate root device.  Putting this together, we get something like
this, for a Windows system on the first partition of the first hard
disk:

menuentry "Windows" {
	insmod chain
	insmod ntfs
	set root=(hd0,1)
	chainloader +1
}

what do you mean boot into windows? i could use it this whole time

[Wiz57]

By "boot into Windows" means just that, since you had to be running some version of Windows to utilize Lick!
What happens if you "cold reboot", you know, turn the power off, wait about 30 seconds, then power on...
press and hold the F8 key while power coming on...it should give you a screen with various Windows Boot Options.
While on this topic of cold boot...have you tried getting into the EUFI/BIOS setup? IIRC, with Dell Latitude you
press the F2 repeatedly after powering off, then turning power back on. Try that too, making sure the correct
disk for booting is selected. You may also need to disable "Secure Boot"...if you didn't get the EUFI security keys
installed properly for FossaPup. First thing, lets see if you can boot Windows (I'm assuming Windows 10, if this
is not correct, PLEASE TELL US THE WINDOWS VERSION!

ps...I'm presently using my little Dell Latitude 3190 11.6 inch laptop, Windows 10...the boot sequences I referenced
above are the ones it utilizes. NOTE: I have NOT installed a Puppy Linux on this laptop yet, but have read a bit
about Lick...my old (ancient) Acer Aspire One does have Puppy "installed", multiple versions, but I did those
"manually" using 7Zip in WinXP since I already had grub4dos installed.

Wiz

[mikeslr]

Rather than continuing to beat an unresponsive horse, perhaps it's time to try a different approach to obtaining what appears to be your objective: dual-booting Windows and fossapup64.

What you are experiencing may result from three problems. There may be others. But these are the three most common: (1) a bad download; (2) Lick didn't function as expected; or (3) Fossapup64 doesn't 'play-well' with your hardware;

The following avoids (1) and (2) and will expose the existence of (3),

I always recommend trying any operating system (including any Puppy) first from a USB-Key. If it won't run from the Key, why waste time locating it on a hard-drive?

Boot into your Windows. Install rufus. https://rufus.ie/en/

Download Fossapup64, again and check that you have a good download. That's what the md5 and sha256 files are for, http://distro.ibiblio.org/puppylinux/puppy-fossa/

See this post about how to use rufus to 'burn' Fossapup64 to the USB-Key. viewtopic.php?p=40522#p40522.

Set your computer to boot into an OS on a USB-Key before looking for OSes on its hard-drive.

Boot into Fossapup64 on the Key. If it doesn't boot, you'll know you have problem (3). If it does boot, use it to find the Fossapup64 files on the hard-drive and delete them from their folder. Copy the following files from your USB-Key into the folder from which you just deleted files:
initrd.gz, vmlinuz, puppy_fossapup64_9.5.sfs, adrv_fossapup64_9.5.sfs, fdrv_fossapup64_9.5.sfs, and zdrv_fossapup64_9.5.sfs. [Since they were used to boot from the Key, you know they were good. Since you are using a Linux OS to copy files, you know Windows isn't going to change them to meet 'its' expectations].

Still running from the USB-Key install, grub2config, viewtopic.php?p=29703#p29703. Restart Graphical Server so that Fossapup64 will take notice of the addition to its applications: Menu>Exit>Restart Graphical Server. Run Menu>Setup>Grub2 bootloader config. See the above post for instructions with graphics.

grub2config should create a new boot-loader with listings to boot either Windows and Fossapup64.