similar to: Proper way to boot memtest86

Hello list, I'm having problems with newest BIOS updates from Gigabyte to my Mother Boards, they don't want to boot syslinux, extlinux y usb-hdd mode. Then I need to know if someone else are having same problem, and can send me the Mother Board versions and bios versions to report as a bios bug. this is from the support, I'm awaiting for answer.

This is really OT, I got jave to paint some prety Ascii Fonts on my terminal server message file, But I'm not able to find out a simple way to paint ansi coulors than escaping and check a table segment by segment. ?Wich editor you use to use if any? Sorry for the OT :) -- Gustavo Guillermo P?rez Compunauta uLinux www.compunauta.com

Can someone point me to instructions on how to build a pxeboot/initrd.img with updated drivers. I would like to pxe boot and install rh8 on a newer machine, and the pxeboot files that come with rh8 (2.4.20-8) don't support my e1000 NIC. I believe that the newer 2.4.20-28.8 drivers will, but I'm having trouble finding instructions in rebuilding the pxeboot initrd.img + vmlinuz to

Hi, I am trying to create an image that is larger than 1.44MB to be used with PXE boot (Ghost 8 requires 2 floppys). My current attempts result in the boot hanging at : Loading boot sector... booting... Starting... My config just says the following: default memdisk append initrd=smalldos.img I created the image following http://syslinux.zytor.com/archives/2005-August/005573.html (I am unsure

I send to the list the perl script to make the inverse of sys2ansi.pl and convert any ansi file to syslinux format. I recommend jave editor to deal with ascii arts and ascii fonts www.jave.de and for painting colours over the ascii file, the ansieditor from http://www.win.ua.ac.be/~wschrep/ansied/ with the patch attached for import and export to syslinux directly and for colour paint mode to

I am not certain that this is the right place to post this, but maybe some kind soul can point me in the right direction if not. And I apologize if this is the wrong spot...The reason I posted here is that I recall running across a syslinux changlog that said "..added support for reading .spl..." files. I want to customize the suse boot up splash screens (for a CD install). I have been

I researched on Archive, but the instruction says to copy startrom.com to startrom.0, so I changed boot program to startrom.0 instead of pxelinux.0, it gives me a TFTP error saying file not found. then I keep startrom.0, change boot program back to pxelinux.0, then I do not see F12 key and boot directly to PXE. then I change the boot program to startrom.com it asked me to press F12, but can

Hi! At first thanks for your great work! I started to make multiboot CDs 1,5 years ago, with Bart Lagerweij 's utils. I have a problem with the memtest86 floppy image, made by the authors in the .zip file, downloadable from it's homepage, when I use diskemu. Some days ago I found on Bart's page a new method to select boot images on CD with syslinux/isolinux/memdisk. I thought this is

Hello, many of our platforms do not have a integrated floppy, some even don''t have a floppy controller. As pxelinux still has a problem with machines without a floppy in combination with some bios versions I need to chainload a different bootstrap loader which works on the floppyless platforms. But I also need to load a BartPE and the other BS loader does not support that. So I tried to

I'm building a custom bootdisk that I would like to boot linux or boot memtest86 (www.memtest86.com). And I'm running into some difficulties with recent versions of syslinux. All I'm doing is making a new label in syslinux.cfg called memtest and giving it kernel memtest.bin. This has worked on and off for several recent versions of memtest. It worked in 1.67, broke in 1.70(loads

Dear Colleagues, memtest86 does not work any more after upgrading PXELINUX to 6.01. When trying to boot, I get the following message: PXELINUX 6.01 2013-07-04 Copyright (C) 1994-2013 H. Peter Anvin et al Loading memtest86... ok Booting kernel failed: invalid argument boot: The config is simple: DEFAULT memtest label memtest kernel memtest86 Any ideas? What additional information can I

My system is hanging up when attempting to boot a bootable floppy disk image Does the following info tell any story as to what's happening? Thanks. LABEL dosdiskimage KERNEL memdisk APPEND keeppxe initrd=dos.img floppy Loading dos.img ............. Ready. MEMDISK 3.11 2005-09-02 e820: 0000000000000000 000000000009fc00 1 e820: 000000000009fc00 0000000000000400 2 e820: 00000000000e0000

Hi, I have boon Googling quite a bit on this, but is it possible: I want to build an ISOLINUX boot CD, but want one of the option to be "Continue booting from hard drive" and thus disregard booting from the kernel on the CD. Is it possible? Or what can I do to force a HD boot from ISOLINUX.CFG? Thanks Herman Starship Systems

Hello all, Forgive me if this has been asked before, I've been googling for two days now and the only thing that I've learned is that bootsplash is a total black art. I'm booting off of a USB stick and I've finally gotten a splash screen to appear before vmlinuz and initrd load, but once they load the splash screen scrolls off the screen. Is there any way to make it behave and

Hi I am an engineer who is making communication systems. I have a board(made by Kontron ltd, Intel CPU, currently with diskless ) that is used in compactPCI. I boot that board with network PXELINUX method and currently using NFS. But I don't want to use NFS and I want to make and use ram disk image. That means I want to use a ram disk as /. Currently I made a initrd by ltsp_initrd_kit. What

I realize this is probably the wrong list but since some of the principals this list deals with are similar in nature I figured it could't hurt. What I am looking to do: Provide a solution to either boot from a floppy disk, establish a network connection, give user the ability to run utilities such as fdisk and dd. as well as provide the same solution as a PXE bootable image. My

Hello list, My set up is almost complete in booting DOS through PXELinux, but I need to create a DOS boot image from (2 )DOS floppies. I've search the archives and google but didn't find any relavant info... My current set up now works with the standard setup (with one DOS floppy): kernel: memdisk append: initrd=floppy.img ramdisk=10000 My goal to is create a floppy.img from 2 DOS

Hi, some time ago I tried to boot an isolinux boot loader from another one to be able to boot e.g. a Knoppix CD with its original boot loader and menus from a "main" isolinux on a multiboot DVD. This works for isolinux <= 3.07 now! However, newer isolinux boot loaders have some problems and the isolinux (e.g. of the Knoppix CD) loaded from the multiboot DVD's main isolinux

I'm having a problem booting Slackware 10.1 boot CD's as well as an isolinux image of my own. The system is a VIA Epia M10000 and the drive is an AOpen ISU-8424E CD/DVD writer. If I use a Toshiba CD-RW/DVD-ROM Drive SD-R2612 in place of the AOpen DVD writer, the cd boots fine and everything works as expected. What's the best course for further debugging of this problem? The only

Hello, I've got several machines which I'm trying to netboot, the setup is a bootserver using dhcpd3 and tftpd-hpa. When a machine boots up, it gets an ip address and downloads pxelinux.0 from the server, then it starts searching for pxelinux.cfg/[MACADDRESS] pxelinux.cfg/0A0000F0 and so on. On the server side I see in the syslog the client's DHCP-request and the client downloading