similar to: SYSLINUX 2.07 released

Hi Peter, I don't want to waste your time. I only want to say that you do great softwares. I use SYSLINUX to build my embedded system with PC104 board and DiskOnChip flash disk, and thanks for your work it run very well. Now I want to boot it via ethernet and I think that I must use your PXELINUX. Pls keep this softwares live. Thanks for your great works Phung Chi Kien Automation

Hi Peter Anvin I tried to use open file and read file SYSLINUX API. But it always make my PC104 freeze. My snip code : ================================================ int __start(void) { int ax,cx,dx,es,si,di,t; com32sys_t inreg,outreg; memset(&inreg, 0, sizeof inreg); memset(&outreg, 0, sizeof outreg); strcopy(__com32.cs_bounce, "test.txt"); inreg.eax.w[0] = 0x0006; //

Hi all, I used syslinux to load linux on DiskOnChip in PC104 for one embbeded project suceefully for several months. But due to power lost sometime the image is corrupted. I want to develop a COM32 util to check CRC for the images and load the good ones. I read in the comboot.doc that com32 can use read file SYSLINUX API call to read a file, and the file must below 64K limit. But the image files

I have put out a 2.07-pre10; this version recognizes vendor-encapsulated (a.k.a. vendor-option-space) PXELINUX options as well as unencapsulated (a.k.a. site-option-space) PXELINUX options. Please try it out... I'd like to release 2.07 no later than Monday. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

First let me say I'm really excited about the possibility of dynamic menu creation over http using php. When this is stable it will make maintinging some of our pxelinux infrastructure much easier. Id like to thank all involved; I'm really looking forward to the gpxe intigration. After hpa's announment for 3.70pre7 I begain testing. I dropped the new gpxelinux.0 and new c32 modules

--- utils/mkdiskimage.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/utils/mkdiskimage.in b/utils/mkdiskimage.in index 533193a..a95a077 100644 --- a/utils/mkdiskimage.in +++ b/utils/mkdiskimage.in @@ -218,7 +218,7 @@ $totalsize = $c*$h*$s; $tracks = $c*$h; # If -s is given, try to simply use truncate... -unless ($opt{'s'} && truncate(OUTPUT,

Somehow, hopefully to be determined, I got my Thunderbird/dovecot Fedora Core 3 configuration into a real snit, such that I can no longer access my INBOX. When Thunderbird tries to get the INBOX content (or get new mail) it reports "The current command did not succeed. The mail server responded: Invalid messageset: -2147483648:*." Scouring logs and googling has come up empty. Now

I was trying to setup dsl (damn small linux) to boot off a usb drive. I found my BIOS wasn't booting from it when using a USB-HDD mode so I found a page for using SYSLINUX to set it up in USB-ZIP mode (http://syslinux.zytor.com/usbkey.php). I made a mistake and (doing exactly what the page warned against not doing) used the mkdiskimage command on the wrong drive (a 230Gb NTFS external

Sorry for the delay, I should not send email on an holiday week-end. I'll try to answer all the questions by explaining what does work for me right now, and what I'd like to do. I have a script to create the a USB stick or an ISO image. The boot media contains many DOS images, and I use versamenu to select one of them. If my DOS image is smaller than 8megs, everything is working fine as

Hi, I did found the problem, a combination of 2 factor. 1- I taught that I did install the latest syslinux, but in fact it was the 3.36 version. 2- Thank to kevin Connelly, he point me to a problem he got with mkdosfs command. The default FAT16 do not work, but the FAT12 do. By adding -F12 to the mkdosfs command fix the problem. The default F16 do seem to work for <8M floppy image. Thank you

Could i get an example to make a binary hard disk image with `mkdiskimage', populate it and install syslinux please? Preferably with a single FAT partition. On Wed, Jan 22, 2014 at 9:20 AM, Rich Mahn <rich at lat.com> wrote: > > > > Both sticks show very unusual factors for heads and sectors > > > which are hardly intentional. If BIOS gets confused like fdisk,

Hi, Dean Graff wrote: > Also, I am trying to use the syntax: > > mkdiskimage -z -F -4 binary.img 1000 > > To get that zip drive geometry for my images and increase the > portable ness of their boot ability. Will this work, to make the zip > drive geometry and then dd or cat this to the 'mass storage device' ? The copy program should not care what is in the image

Hi everyone I am the new user of icecast2 My problem is: On my servers, i already installed icecast2 to streaming mp3 and aac file. Now i want to make a load balancer with these icecast2. When user request a content to a balancer, this balancer will choose the icecast2 server which have less connections for scaling. What i should do now? I heard that wowza can do it. But i want to find some

hello everybody, apologies if I'm missing something here Just tried to build 6.04-pre1 test version with: make bios installer and found some problems all (seemingly) related to inaccurate paths in various Makefiles. I enclose a complete patch at the end of this email, which details the problems I found and how they got fixed for me. As an example, this is the first error I got:

I have produced a first cut of integrating gPXE with PXELINUX. This builds, in addition to the usual pxelinux.0, an image called gpxelinux.0 which includes the gPXE network stack. The result is that one can now download images via (almost) any network protocol supported by gPXE, including http. This lets one do fun things like using a CGI or PHP script for the configuration file. SAN

Hi, i too played with mkdiskimage in order to get more Linux examples. When i applied it to a real 2 GB stick with write speed 4 MB/s i had enough time to add some pacifier code to the big zeroizer loop. (-s does not prevent zeroizing on block device. Probably because truncate() fails.) My pacifier is combined with what Perl advised me when i tried "fsync(OUTPUT);". Of course this

utils/mkdiskimage.in: With option -s: Avoid zeroizing the partition even if truncate() failed. --- utils/mkdiskimage_patched_01.in 2014-01-30 20:43:02.000000000 +0100 +++ utils/mkdiskimage.in 2014-01-30 20:45:09.000000000 +0100 @@ -217,8 +217,11 @@ print OUTPUT "\x55\xaa"; $totalsize = $c*$h*$s; $tracks = $c*$h; -# If -s is given, try to simply use truncate... -unless

Hi, this is the diff which i consider a halfways reasonable solution for the following problems with mkdiskimage: 1. Ignoring option -s if the target file is not suitable for truncate(). 2. Miscalculation of truncate() size by a factor of 512. 3. The storage capacity of device files can only be measured for Linux block devices. 4. Long time of silent work when slow devices (e.g. USB

I have released SYSLINUX 2.06; it's basically identical to 2.06-pre4. I'm doing this now because the bug fixes are so major and because I am not sure I'll be around next week. -hpa 2.06 is a bug fix release. Changes in 2.06: * ALL: Fix problem that would occationally cause a boot failure, depending on the length of the kernel. * ISOLINUX: Fix problem

utils/mkdiskimage.in: New option -S to sync zeroizing after each cylinder and to issue pacifier messages. --- utils/mkdiskimage_patched_03.in 2014-01-30 20:54:27.000000000 +0100 +++ utils/mkdiskimage.in 2014-01-30 20:59:19.000000000 +0100 @@ -139,6 +139,7 @@ if ( $file eq '' || $c < 1 || $h < 1 || print STDERR " -4 use partition entry 4 (standard for