Hello,

I loaded the legacy OS 2 files from the ISO (vmlinuz, initrd.gz and pup_214.sfs) into a CF card (on an IDE adapter in my old PC). This CF card can be mounted on an USB adapter later for booting diverse PCs.

It boots..
and stop later with an error.
... looking for Puppy in .. (diverse devices) DONE
... looking for pup_save.2fs in .. (diverse devices) DONE
... (STOP TO PROMPT) cannot find Puppy in idehd.

Question: what is the reason of stop? should I perhaps use a specific boot code?

my syslinux.cfg has
label puppy
kernel vmlinuz
append initrd=initrd.gz PMEDIA=usbflash

It's not finding your root partition after it loads the kernel and initrd. Are you having this problem when the CF card is in the ide adapter or only afterwards when you try to boot with the card in a USB adapter? If the lateer, it may be that your initrd does not contain the necessary kernel modules for usb mass storage devices. If the former, I can only note that this line:

append initrd=initrd.gz PMEDIA=usbflash

would normally look like:

append initrd=initrd.gz root=<insert root partition device file>

I'm not sure to what extent syslinux supports the use of partition labels so that may be a problem. Also, If your ide adapter requires special driver modules, again, your initrd may not include them.

Hello,
I only tested it in the IDE adapter (I have no PC home which are USB boot compatible).
I will test with a root path. In this case is root=/dev/hdb1 the correct path?
Because in my other system TinyCoreLinux the CF on IDE is recognized as hdb1.
But perhaps not here. Is it perhaps a sdb1 .. or other?

It will be one or the other depending on how your kernel on the CF card is compiled. If it uses the legacy ide modules, the device will be designated hdb1. If it uses the modern libata modules, the device will be designated sdb1. It may be that your CF card to ide adapter requires the older legacy modules to function properly or it may just be Tiny Core uses legacy instead of libata by default. All modern linux distros that I'm aware of switched to libata a long time ago.

If your system is capable of booting from a cdrom, you may want to download Parted Magic here:

http://partedmagic.com/doku.php

Burn it to a CD-R as an image, boot up with it with the CF-card attached and see how the Parted Magic partition editor detects your CF-card.

Get rid of the cf to usb and get a usb flash drive maybe.

ok, but 5 other distros boots. so, this one should boot.

That is not logical. Another distro does not prove that this one will work. It only proves others will work.

See kilgoretrout's reply.

ok ok. I mean I would get rid of .. the distro (not the card) if it dont work. This thread is not a question of live or dead, just a test of legacy-os-2. If it dont boot, then it dont boot (I could see legacy-os-2 qith qemu on a laptop: this is a good thing and could potentially be interesting for a colleague where I am installing linux in parallel to his windows xp).
And: the legacy-os-2 of the CF card dont either boot on the IDE nor on the USB adapter (with the error message in the beginning of the thread). GPARTED recognize it. TinyCoreLinux, Slitaz, PartedMagic etc. boots.
Legacy-OS-2 not. Perhaps extracting the files of Legacy-OS-2 out of the ISO (with ISOMASTER), then placing them on a drive like PuppyLinux, is not working at all (perhaps it only works on the CD). I could not contact the Legacy-OS-2 developper till now. I will search again for ihm.

EDIT: by searching the developper, my problem was described and a fix seems to exist; use of the boot code "pfix=ram". I will test and post the result here. Sorry for disturbing the whole communinity: Mr. Google could already know the solution. http://www.murga-linux.com/puppy/viewtopic.php?t=68397

forget pfix=ram. dont work,
I have now to try psubdir=/dev/hda2

Solved.
See http://www.linuxquestions.org/questi...on-usb-903156/