similar to: SYSLINUX 2.04 released

In the light of the rather serious MEMDISK bug in 2.03, I would like to promote 2.04-pre2 to 2.04 some time this evening, California time. Please try it out -- especially PXELINUX and MEMDISK -- if you have the opportunity. Thanks! -hpa

It seems that 2.03-pre1 resolves PXELINUX problem on a reasonable number of hosts. Perhaps somewhat importantly this seems to include the RBFG PXE boot floppy, which did not work with 2.02. This was somewhat of a surprise, since it didn't exhibit the failure mode that I would have thought would have been the trigger of the bug. Instead, it was one of those stacks that would transmit packets

Hi.. Well i've tried each and every method to insert any winme command.com into any bootable image and its really giving me problems.... I even further tested the same image with reinserting the 98 command.com and the image worked just fine.. So acc to me the problem has to lie in me command.com as there is no real mode dos in ME.. Also try using umbpci.sys and lowdma.sys for managing

Hi, The link given in your http://syslinux.zytor.com/pxe.php#config page points to the http://www.argontechnology.ca/rbfg/index.shtml site. This site talks only of Win2k and .Net server. There is no mention of GNU/Linux. Is it possible to use rbfg.exe to create a pxelinux bootable stack on a floppy. If so how ? Rom-O-Matic has a pxe loadable ROM image. Is there a way to use this to

Hi.. I'm Jaspreet Oberoi and i'm new to this forum.. Actually i am using Bootscriptor to make multibootable cd's and it is using your 2.04 version of syslinux and memdisk.. What my problem is that when i boot any image i.e .img file which has a Win98 command.com it works alright but when i try to boot any image with a WinME command.com it just hangs on Loading .. then Starting....

Hi, "Jaspreet oberoi" <jaspreetoberoi at hotmail.com> schrieb am 02.06.03 06:27:13: > Actually i am using Bootscriptor to make multibootable cd's and it is using > your 2.04 version of syslinux and memdisk.. > > What my problem is that when i boot any image i.e .img file which has a > Win98 command.com it works alright but when i try to boot any image with a

Hi, I've got the same Problem. Not with WinMe but Win 98SE. But what I figured out is, that it doesn't realy apply to the Command.com rather to the Way the BootImage was created. It took me a long time to get my Hands on a Image with 2.8MB that's working. Since creating one my self, was allways failling. I downloaded the Bootutils 4.3 from 3com and used the Imageedit tools. With these

Is there a way for isolinux/syslinux to execute a list of comboot files immediately at startup, and only once? I have a bunch of small comboot .com files that I want to batch run immediately, then after that do a DISPLAY boot.msg similar in some ways to an autoexec.bat. For example: DEFAULT mycd APPEND ramdisk_size=100000 init=/etc/init lang=us .... TIMEOUT 300 ONSTARTUP mybatch <- ???

Thanks for Remko for his help to solve the fractional cylinder problem. But there is the second problem, the boot disk failure (see below << [B]) # but when booting via PXE (pxelinux.cfg/default) ... LABEL t KERNEL memdisk c=2 h=256 s=63 APPEND initrd=disk.img # the following things occur boot: t Loading memdisk Loading disk.img ...................................(16MB)......... Ready.

Greetings, I had a quick question about lower memory usage by memdisk. I've read through the mail archives and found a couple of posted questions but unfortunately no answers. I know the documentation states: "MEMDISK simulates a disk by claiming a chunk of high memory for the disk and a (very small - 2K typical) chunk of low (DOS) memory for the driver itself, then hooking the INT 13h

Hi, I just tried to boot my token ring devices with 2.05 - to no avail, it hangs after loading the kernel. I then tried older versions, and found 2.03 booting like a charm, and every 2.04-pre including 2.04 hanging. Here's the config of the devices: - Networkstation 2800 with IBM PCI Token Ring card 2 - IBM Thinkpad T21 with IBM PCI Token Ring card 2 Maybe this has to do with the changes

From: Sylvain Gault <sylvain.gault at gmail.com> Some linker scripts were splitted into i386 and x86_64 versions in commit d8eede3f2a360163235fad222a0190cd7c5bef38 but older scripts were left there. Signed-off-by: Sylvain Gault <sylvain.gault at gmail.com> --- core/syslinux.ld | 414 ------------------------------------------------ core/x86_64/syslinux.ld | 389

Hi... I'm Jaspreet. I've been having the memdisk memory overlapping problems since 2.04 Its always seen in the compressed images whereas the uncompressed images works just fine !!! It just stops at the error "Ran out of input data".. Even the memdisk 2.05 dint solve my problem !!! maybe there r still some bugs remaining. !! My motherboard is Intel 845GEBV2 and i've got

Hi all, I have just released SYSLINUX 2.03-pre4; this is the same as SYSLINUX 2.03-pre3, except: a) I have -- I hope -- finally fixed the Perl scripts so they work in UTF-8 locales; b) MEMDISK now supports gzip compressed images. For those who have requested it... you should really thank me for the last one. It took quite a bit of work, mostly because I had to move the installer to be a

Hello again and thanks for your support. I am trying out the pxe floppy - rbfg that you mentioned in your previous email for some machines that are not pxe capable but have supported network cards. It looks like it is going to work but then hangs. The dialog below is from a vmware session just for testing but I have the exact same problem on an old IBM box with a Intel e100 card. Here is

This release is identical to 1.67-pre1. Unfortunately the people who reported problems with 1.66 never got back to me to indicate if it solved their problem or not, but since it fixes a real bug, regardless, I decided to release it as 1.67. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/ -hpa 1.67 is a trivial bug fix release affecting a fairly small number of systems. 1.66 is an

Hi I have ported syslinux to win2k/winxp. It is attached. It has been tested with floppies and flashcards, but not on harddisks. On harddisks I'm not sure if I should use \\.\PHYSICALDRIVEX or \\.\X: as arguments to CreateFile (I'm no windows wiz) and I do not currently have a system to test this on. The program can be compiled using mingw or in cygwin using the option -mno-cygwin

Yes, it is in the docs... All i need to do is load the memdisk image with the 'keeppxe' option. so, the default file should look like this: -------------------------------------------------------------------- default linux label linux kernel memdisk append initrd=client.ima keeppxe -------------------------------------------------------------------- That is all! Again, thanks for

Syslinux 3.84 has been released. This is a mixed minor new features/minor bug fixes release. Changes in 3.84: * SYSLINUX: make the DOS installer work for MS-DOS 7.x/8.x (Win9x/ME) again. * HDT: updated to version 0.3.6 (numerous changes.) * mboot.c32: now supports video mode setting if requested by the image. * MEMDISK: Fix floppy images of

Sorry, I originally send this message to H. Peter only... -----Original Message----- Hi! Strangely enough, I have again the same Fujitsu-Siemens machine which (still) has the same darn PXE bug. This time I have tested it with Pxelinux 2.02 . Just to suite it to my specific needs, I have recompiled it, changed only this line: (2036) ;cfgprefix db 'pxelinux.cfg/' ; No final null!