similar to: isolinux: Extremely broken BIOS detected

Hello, Can I load setupldr.bin directly using isolinux without original CD boot sector? Thanks, Theewara

Hello! I'm trying to boot with a remastered Knoppix 3.4 CD. I burned it with debugging and I get the following output: isolinux: Starting up, DL = 9F isolinux: Loaded spec packet OK, drive = 9F isolinux: Loading main image from LBA = DEADBEF0 isolinux: Sectors to load = D5B7 isolinux: Disk error BE, AX = 42F0, drive 9F A don't understand everything in it and I can't find enough

I have a Lilo.conf file, which I have tried for many hours to convert to Syslinux. I looked around on the web for references on translating some of the components. I want to convert it to Syslinux/Isolinux. Any suggestions would be greatly appreciated. When I tried to convert it I made sure that the kernel and initrd had proper DOS names and such. -Michael =:LILO.CONF:= prompt timeout=10

Okay, spending the time to dot t's and cross i's (or something like that), I think I have something now that can be called 3.00-worthy, so let's call it a release candidate. Changes over the earlier 3.00 prereleases: - -m and -a options now supported by the DOS installer. - PXELINUX now allows IP addresses, FQDNs, and truncated hostnames when specifying an alternate TFTP server

I'd like to take advantage of the small, compressed Linux systems such as Knoppix or BeatrIX, but I can't have a CD rom on my system. (A project's marketing requirement.). So I figure I could use something like SYSLINUX or ISOLINUX to do it for me, but there is some magic in the process (the sequence of booting) that eludes me. 1/ mbr (from SYSLINUX) installed on hard drive... and

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:

Does SYSLINUX have any idea which DOS driveletter would be assigned to the disk it is booting from? At www.veder.com someone is trying to build a USB flash drive. However, FreeDOS does not seem to boot correctly from it (bootsector trouble maybe, or kernel itself is confusing drives), thus we're thinking of using Syslinux + Memdisk + bootimage, but somehow we want to be able to also access the

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

I have a 32MB HD image that I can pxelinux.0/memdisk boot without issue. I would like to both memdisk and my image on a CD and then boot from the CD with pxelinux.0. Is this possible? If so how? Thanks.

Hi, I am trying for quite some time to create a bootable hd disk image with mkdiskimage (included in the syslinux distribution) and the combination isolinux/memdisk. It just won't work:-} I have done the following: [snip] # ./mkdiskimage -d -o disk 256 32 1 640 # losetup -o 640 /dev/loop3 disk # mount /dev/loop3 /mnt/3 # mount | grep loop3 /dev/loop3 on /mnt/3 type vfat (rw) :: copy

Hello everyone, I am attempting to add another boot option to our multi-boot technical resource CD where I work. I currently have 8 working floppy disk images, but this time I need to add a piece of software which I only have access to through an ISO image. This ISO image, when burned to a CD, boots and runs the software fine. I know that isolinux does not support booting ISO images. I used

hi there, hope this is not too much out of topic here... i give it a try anyway :-) when i try to build the iso with: mkisofs i get the following error: [...] Using TTYX2000.;1 for ./dev/ttyX2 (ttyx2) Using TTYS0000.;1 for ./dev/ttys0 (ttyS0) Using TTYY3000.;1 for ./dev/ttyY3 (ttyy3) Using FD0H360000.;1 for ./dev/fd0H360 (fd0h360) Using TTYX1000.;1 for ./dev/ttyx1 (ttyX1) Size of boot

Hi, I am trying to boot a liveCD thats on my hard disc ...is there a way of doing this using lilo ? reason well rather than keep burning to CD then testing I want to be able to make changes then test by booting to liveCD.... Thanks in advance Dave T..

Western Digital Diagnostic Utilities problems... PROBLEM: Western Digital Diagnostic DOS based utility does not work with the latest ISOLinux (2.11). BACKGROUND: I utilize ISOLinux and memdisk at work to load various DOS diagnostic utilities from various floppy images. Here is my ISOLinux Configuration file (isolinux.cfg) ==========START======== default 0 display bootmsg.txt prompt 1 F1

forgive me.. i have no idea what im asking or if its possible... i have 2 partitions as follows and am using the std windows xp bootloader to boot xp - ntfs (windows xp) - fat16 stupid question is... can i use syslinux, isolinux, memdisk or some combo there of to place a bootable cdrom iso image on the fat16 partition and then have a boot menu with something to the effect of : 1) winxp as

I have just released SYSLINUX 3.00-pre9. The only change versus 3.00-pre8 is that the MEMDISK query API now reports the boot loader ID byte, per Bernd's suggestion. This is a release candidate, and I plan to release it as 3.00 *tomorrow*, unless I hear back anything bad. -hpa

Is it possible to chain isolinux and memdisk over pxelinux? If it's possible, I'd like to boot a CD Image over the network. I've been using pxelinux to boot ltsp for years, and recently upgraded to take advantage of memdisk for booting a DOS hd-image. Ideally I'd be able to boot a CD-Image. Thoughts? -- <:3)~ Michael T. Garrison Stuber

I have added instructions to memdisk.doc for how to disable MEMDISK. However, it's unlikely that this will work if you're running under DOS, since DOS will be very unhappy about drives changing underneath it. Anyway, until the next (pre)release comes out, here are the instructions: --- memdisk.doc 27 Apr 2004 06:49:36 -0000 1.10 +++ memdisk.doc 6 Jul 2004 01:29:03 -0000 @@ -122,5

HPA, a longterm reminder. See below. Can you also make a LABEL ignore other labels if no KERNEL statement is found in between? That way you could define multiple aliasses for an entry. label foo label bar label memtest kernel memtestp foo ignores 'label bar' , 'label memtest' and executes 'kernel memtest' bar ignores 'label memtest' and executes 'kernel

>information a bit closer; it'd find that it's marked accordingly. UDMA2.SYS author now worked around it, it seems you do something with "DPTE" in isolinux.asm but not using it (probably for memdisk or direct floppy/harddisk emulation?). also something about EDD v1.1 and v3.0 specifications and setting bits to 1. Anyway, the driver works now on: BIOS -> cdrom ->