search for: btmgr

...uperman's PXE Boot Menu MENU INCLUDE pxelinux.cfg/graphics.conf MENU AUTOBOOT Starting Local System in # seconds LABEL bootlocal MENU LABEL ^Boot local system disk localboot 0 LABEL Tools Menu MENU LABEL ^Hardware Tools Menu KERNEL menu.c32 APPEND pxelinux.cfg/tools.menu LABEL btmgr MENU LABEL ^Smart Boot Manager KERNEL memdisk APPEND initrd=btmgr/btmgr.img ---8<---------------------------------------------------- pxelinux.cfg/tools.menu: ---8<---------------------------------------------------- MENU TITLE Hardware Tools MENU INCLUDE pxelinux.cfg/graphics.conf...

perhaps the boot-from-cdrom code in Smart Boot Manager? Bernd >>> No, since booting from CD-ROM requires that the El Torito part of the BIOS is activated, which it won't be if it didn't boot from CD-ROM in the first place. ---------------------------------------------------------------- Op deze e-mail zijn de volgende voorwaarden van toepassing:

I don't know if this is even the proper place for my issue, but since the boot floppies that I have downloaded are syslinux based. I have a 97 vintage Hitachi laptop, and it won't boot newer CDs. It will, however, boot a Debian 2.1 CD. As we know, that version is quite old, and it booted off the second CD, not the first. What I want/need to know, is there a reasonable way for a

I'm considering the suggestion which was raised before about turning the debugging messages on by default in isolinux, or specifically, not building the non-debugging-messages version in the standard distribution. What do people think (especially distro maintainers?) -hpa

Is there a doc that describes how to create a floppy that will boot and then switch over to the installation CD? It looks to me like this should be possible using grub on the floppy. Charles L. Sliger, Information Systems Engineer, chaz at bctonline.com "No matter where you go, there you are..." -------------- next part -------------- An HTML attachment was scrubbed...

...th current kernels (giving me an empty /proc/cmdline for example when using kernel 2.6.23), otherwise I'd just use an old isolinux version of course. I tested several isolinux versions. Isolinux verions >=3.51 boot kernel 2.6.23 just fine - but not on old, b0rken hardware. I'm aware of btmgr's existence but that's not a solution for me, because this is a workaround involving an additional step on the user's side. :( Is there any chance to get around this situation? Is there a specific reason why isolinux >=3.51 (AFAICS) does not support older, b0rken hardware at all? A...

I would like to develop a system where by I can boot any of the machines on my system - and select from a menu what I would like that particular client to do. For example, maybe load a bootdisk image from a network share, and boot that. Or boot the first partition on the local disk.

The BIOS on my laptop does not support booting from USB. I would like to be able to have my Windows XP on a partition on a USB disk drive and be able to run from the USB disk using perhaps a CD or floppy to bootstrap the system. My questions: 1). Is there a way to use syslinux and friends to do this? 2). If not, is there some other boot loader that may work? 3). Is there any hope at all?

hpa etal, Im trying to get PIRT running on an SBC which has no CD-ROM drive. (an 8 MB ISO which demo's RTAI - RealTime Application Interface, on linux patched with Adeos) (BTW, PIRT uses isolinux) anyway, Im trying to use pxelinux to chainload / memdisk / mboot it, Im having no success. Ive also tried booting memtest86, which I can boot on my laptop using grub, ie title memtest