similar to: USB-Storage after perfect booting

Only to inform that I've just released the version 1.2 of makebootfat. makebootfat is a GPL command line utility able to create bootable USB disks for Linux and Windows using the FAT filesystem and syslinux. As far I know it's the most advanced tool available able to make bootable USB disks. It's able to autodetect/partition/format/populate the USB disk in a single step without any

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

Hello list, any try the new memtest86 v3.2 with isolinux 3.11 cd and pxeboot? How is the proper way to chainload memtest86 I was tried: label memtest kernel memtest.bin but, nothing happens just a weird hang (my older versions of memtest hangs too). Anyway chainloading in a floppy image with memdisk on CD or pxeboot was fine but if I use memory to emulate a floppy I was not using this memory

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

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

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.

I would like to document adding multi-cardreader USB support. I would think that USB support should be added to tips & tricks: http://wiki.centos.org/TipsAndTricks Then a link to multi-cardreader support. My wiki name is RobertMoskowitz

Hello, David Following the link below, you wrote: http://syslinux.zytor.com/archives/2004-June/003639.html [syslinux] Isolinux booting to /root on USB Drive David Forslund forslund at mail.com <mailto:syslinux%40zytor.com?Subject=%5Bsyslinux%5D%20Isolinux%20booting%20to%20/root%20on%20USB%20Drive&In-Reply-To=> Sun Jun 13 00:11:10 PDT 2004 * Previous message: [syslinux]

Hello all, A few months ago I saw a statement that L2ARC writes are simplistic in nature, and I got the (mis?)understanding that some sort of ring buffer may be in use, like for ZIL. Is this true, and the only metric of write-performance important for L2ARC SSD device is the sequential write bandwidth (and IOPS)? In particular, there are some SD/MMC/CF cards for professional photography and

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

SAMBA 2.2.8A I am automounting a 6-in-1 smartmedia reader such as: /etc/auto..master /mnt/auto /etc/auto.misc --timeout=1 /etc/auto.misc carda -fstype=msdos,rw,nosuid,nodev,umask=000 :/dev/sda1 I am also making that a samba share: [card_a] comment = Removable Card Media path = /mnt/auto/carda browseable = yes public = no read only = no

With the new 3.01 and 3.07 version I found a big slowdown booting from USB devices. On my PC it takes more than 2 minutes to load the kernel and the initrd filesystem. Compared with the previous behaviour of syslinux 2.13 with takes only 10 seconds or little more. The BIOS boots in FDD mode (DriveNumber variable is 0). I've also tried to disable the EDD support in the source. But the boot

Well, I consider icecast as a testing application server. You just cant deploy it all of a sudden becuse it needs a lot of work still and the UI needs to be friendlier. Lets wait till the top programmers come up with a central solution which i am sure that they will. I myself have been using SHOUTcast and its ok. User count reached at 460 a time ago but with icecast, i dont think that it can at

On my new Dell system, it's got a cardreader. More to the point, it's got an idiot menu key... *right* next to the right control key, and just where the annoying keyboard design has it cut down from the oversize space bar ASCII art <ctrl><WinDoze> <tall[ ]<tall<tall<tall <ctrl> Alt>[ tall spacebar ] alt> Win>

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

Dear Opus developers. This is the first time I write here, so hello to everybody! Sorry to disturb you but I would like to ask you something I could not answer by googling and by looking at this mailing list archive. I have just started investigating this new and promising codec for real-time audio transport over the internet for industrial applications. I was previously experimenting with RTP

This patch fixes ISOLINUX/SYSLINUX when using the kernel mem= option with a value greater than the effective memory on the system. At present, in this condition the kernel doesn't boot correctly. The default Linux behaviour (verified on 2.4.22) is to ignore this option if the BIOS reports less memory than the value manually specified. This patch force the same behaviour for ISOLINUX/SYSLINUX.

Hi, I am trying to assemble a preety simple program, but the assembler is giving parse errors: =========================== %.LC0 = internal constant [17 x sbyte] c"Hello World %d \0A\00" %.LC1 = internal constant [17 x sbyte] c"yyyyyyyyyyyyyyy\0a\00" declare int "puts"(sbyte*) int "main"() { %cast1 = getelementptr [17 x sbyte]* %.LC0, long 0, long 0

Arjen, Wow, that was quick... Thanks! (It was taking me a while to sort out all of the different CFLAGS settings; hence, the tracker item.) I would take issue with the following assertion in Makefile.am: "In any case, CFLAGS are only -I options, so there is no harm." since this is what got us into trouble in the first place... but I guess that was there before you edited it as

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