nayame wrote: ↑12 Dec 2024, 03:53
mbr boot machine ,using grub,install it in puppylinux by using the install script porteux/s images supplied,partition type :ntfs,for porteus i can access boot menu,but for porteux i can not
Ok
nayame, lets deal with one machine at a time.
The machine/computer has puppylinux on it, you downloaded the porteux/s iso files, some how extracted the iso files someplace and ran the porteux-installer which loaded the boot files & folders to the computer's harddrive. You then ran the porteus-installer which loaded the porteus boot files & folders to the same harddrive overlaying the same named boot files and folders previously installed. Yes?
The output of a "ls -hon" command run on the harddrive would be helpful. And a "ls -hon /boot/syslinux/*.cfg" one would be useful also.
I suspect if you look at the /boot/syslinux/ folder you should see a porteu
s.cfg file and a porteu
x.cfg file. Copy lines 30-41 of the porteu
x.cfg file to after line 68 in the porteu
s.cfg file and edit the LABEL and MENU lines to be unique. Basically ending up with something like this:
Code: Select all
LABEL GRAPHICAL
MENU LABEL Graphics mode
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND changes=/porteus
TEXT HELP
Run Porteus the best way we can.
Try to autoconfigure graphics
card and use the maximum allowed
resolution. If booting from a
non-posix (FAT/NTFS) drive,
see the Saving Changes Help
below for how to save changes.
ENDTEXT
LABEL fresh
MENU LABEL Always Fresh
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND nomagic base_only norootcopy
TEXT HELP
Normally Porteus saves all changes
to the /porteus/changes/ directory
on the boot media (if writable)
and restores them next boot.
Use this option to start a fresh
system, changes are not read from
or written to any device
ENDTEXT
LABEL graphicalx
MENU LABEL Porteux Graphics Mode
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.zst
APPEND changes=EXIT:/porteux
LABEL freshx
MENU LABEL Porteux Always Fresh
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.zst
APPEND nomagic base_only norootcopy
No guarantee this will work but it may.
If you post the grub menu for your puppylinux system we can see if it can be added also.
On a puppylinux system see if it's grub supports the loopback command.
Multi-booting is possible, just not by installing one on top of another.
Added in 18 minutes 1 second:

I
just saw this posting
nayame.
nayame wrote: ↑12 Dec 2024, 02:34
I have two laptops that are grub bootstrapped, and one A has Win7 and Lick installed, and Lick boots into a lot of puppylinux distributions, This computer uses the Porteux1.6 installation script to install Porteux under Puppy,After installation, I found that I can only enter Porteux,Can't enter Grub,Naturally, I can't enter Win7 or other PuppyLinux,Another laptop B,It's also Win7+Lick,Use Lick to guide into PuppyLinux, However, after installing porteus5.0 under puppy, you can choose to enter grub on the boot screen, that is to say, you can also enter win7 and puppy. I hope to get back the grub of the computer with Porteux, so that Porteux, Win7, and coexist, and I can freely choose the system I want to enter when I boot up.
I've never heard of Lick and will investigate later but your setup sounds much more normal. So basically Porteux screwed up your system's boot process. Lets ask
porteux if porteux backups up the mbr code when doing an install. If not hopefully you have a backup of the system handy.
Did you install the porteux/s systems into separate partitions?
Added in 2 hours 17 minutes 17 seconds:
An interesting app
Lick. Do you ever converse with it's developer?
When Lick installed puppylinux did you have to run a puppylinux-install app too?
Seeing your Lick boot menu would definitely be helpful.
Added in 1 hour 7 minutes 33 seconds:
When booting your systems press the BIOS key, the BIOS key is usually F2, F10, F12, F1, or DEL, but it depends on the computer's manufacturer, and post a screen shot of the window, if you can. I post screen shots to
https://postimages.org/ and post the image's Forum link here.
Then see if this helps.
https://lorimer.dev/lick/doc/ wrote:Uninstall a Distribution
Use list_installed to get a list of all installed distributions.
Uninstall one using uninstall.
If this is the last installation, you may want to use uninstall_loader