similar to: A bug in syslinux boot code

Hello, are there known issues with some bioses not booting from Superfloppy format? All I get is the Syslinux (c) line and nothing else happens afterwords. Everything works fine if a partition is added to the device. Unfortunately however the target device can not be partitioned. Any hint? Sven -- Why are there so many Unix-haters-handbooks and not even one Microsoft-Windows-haters

On 07/08/2014 05:55 PM, H. Peter Anvin wrote: > On 07/08/2014 03:05 PM, Alexander Perlis wrote: >> >> Question: what's special about the transition from 8203KiB to 8204KiB? >> Both have CHS=8/64/32 and both involve a fractional end cylinder. > > Fractional cylinders with floppy disks is almost certainly a very bad thing. > Agreed, but that doesn't appear to

Syslinux 4.04 pre-13 and Syslinux 4.04 pre-14 are giving me these errors: SYSLINUX 4.04_pre13 CHS Copyright (c) 1994-2011 H. Peter Avin et al and SYSLINUX 4.04_pre14 CHS Copyright (c) 1994-2011 H. Peter Avin et al respectively. Syslinux 4.04 pre-12 works fine, as does 4.04 pre-11, 4.04 pre10, 4.03, and earlier. The machines I have tried this on are one with an AMI BIOS, and another one with an

On 08Jul2014--09Jul2014, Ady, Peter Anvin, Gene Cumm, Bernd Blaauw, Shao Miller, Kenneth Davis, wrote: > [...] Thank you all for your responses. You helped me solve my problem. For anyone else that runs into similar trouble and finds this thread, here follow summaries of what I've learned. To recap, our PXE server holds Dell BIOS updates in FreeDOS floppy images booted via MEMDISK.

On 07/15/2014 06:57 PM, Ady wrote: > > Finally, when using MEMDISK to boot floppy images, these images > should not use partial "cylinders". In other words, use exact CHS > values for floppy images, instead of building the images by means of > the desired megabytes size. Then use the selected CHS values as > parameters for MEMDISK. > If you have a proper set

I'm running into an issue which I didn't expect to encounter. When specifying the "nopassany" parameter to hide physical drives, I'm getting different output from ELTORITO.SYS (v1.5, syslinux distro) such that it fails. My intent is a LiveCD functionality with a DOS RAMDISK program taking over as drive C:, meaning either no FAT partitions on harddisks and removable disks

Hi all, I was using grub2 for booting Archlinux x86_64 in my GPT Internal HDD (/dev/sda) then I switched to syslinux/extlinux. It was working fine but suddenly it staring showing "Boot Error" message on screen. I googled for a solution and tried all syslinux versions from 4.04-pre4 down to 4.03-stable but non of them worked. I don't know what suddenly changed caused this

Hi. I'm working on replacing a PXELINUX/MEMDISK loaded DOS based installation image with a PXELINUX/MEMDISK loaded WinPE ISO image. So far everything seems to work well (appending "bigraw" to memdisk solved booting problems on several machines), but I kind of miss the option of using getargs.com to get/set environment variables from the memdisk command line. Is there any way to

A kind request for help please. MEMDISK is causing an issue with the Dell OptiPlex GX280 and GX620 platforms. Booting a PC-DOS/Ghost, disk image is successful (and proper) when using version 3.83. See results below: MEMDISK 3.83: Ramdisk at 0x07eeaa00, length 0x007bc000 command line: initrd=images/ghostclient/280_620/osbootc.img BOOT_IMAGE=memdisk MEMDISK: Image seems to have fractional end

Hello all, I have a boot server (running Debian Lenny x64) with a number of bootable options already configured (freedos, memtest, sysresccd etc). What I am struggling to do now is add Ubuntu and Debian netinst images so that I can boot from the network and have all the boot options available as if I was using a CD-ROM. The problem is that (as far as I can tell) the Ubuntu and Debian

IRC user ernini first noticed this. We both tried using gpxe/gpxelinux.0 from Syslinux-4.04-pre22. ernini used pxechain to a commercial NBP which RETs (the same as PXELINUX) and failed. Both of us had success with core/pxelinux.0 from Syslinux-4.04-pre22. For my test, I have a VM in VMware Server 2.0.2 (VMHW v7). I loaded gpxelinux.0 using the VM's built-in PXE ROM. Then I used

Trying to get at least my backlog of bug fixes out... I'm hoping to do a 4.03 next week. Please help by: a) giving it a whirl; b) letting me know if I have missed any low-risk bugfixes. Gene: I did not include your UI branch in this release, because it made me a bit nervous... poke me on IRC when you have a chance. -hpa

I try two ways to use syslinux for USB key (2GB USB key), and one approach can boot from machine, another approach can not. Could you review the following steps and tell me why #2 can not boot? Thanks very much! approach #1 steps: mkfs.vfat -F 16 -n USB /dev/sdb -I (pay attention, it uses "-I" here) syslinux /dev/sdb (pay attention, it is "sdb", not "sdb1" here)

On Tue, 08 Jul 2014 15:54, H. Peter Anvin wrote: > >On 07/08/2014 11:26 AM, Ady wrote: >> >> It's interesting that you ask this, because every document related to >> newmkfloppyimg.sh specifically recommends adding: >> floppy c=$CYLINDERS s=$SECTORS h=$HEADS >> to the MEMDISK arguments. >> > >It would be important for floppies to know

Hello. I've been testing pxelinux.0 (4.04-pre14) on some laptops: - HP EliteBook 6930P with BIOS F.18. - HP EliteBook 8440P with BIOS F.06. - Dell Latitude E4310 with BIOS A06. When booting pxelinux.0, the machines first display some random letters in different colors and then reboot. We've been using 4.02 for some time without problems. I've tested 4.03 too and it seems to work.

Hi, I?ve got the following problem: When accessing a share on a Samba server from Win2000 or Windows XP this fails. The access is denied. All the shares are visible within ...\Network Neighbourhood\Workgroup\Chs-server.chs.\share1 ...\Network Neighbourhood\Workgroup\Chs-server.chs.\share2 ... ...\Network Neighbourhood\Workgroup\Chs-server.chs.\Drucker und Faxdienste Besides this I see the

> Hi, > > Ronald F. Guilmette: > > > Doesn't the Syslinux project provide (hopefully strong) specific > > > reccomendations, [...] > > hpa: > > We try (see our wiki), > > The general wiki > http://www.syslinux.org/wiki/index.php/SYSLINUX#Creating_a_Bootable_Disk > says > "In order to create a bootable disk using SYSLINUX, prepare

As I said before, booting is bigger than one bootloader. I am replying to what I think was asked. I might have misunderstood the questions. Whichever the case, this email is less about Syslinux itself. If this is considered too far off-topic in the Syslinux Mailing List, please receive my apologies. > > I still have the factory-set contents of my three USB sticks. A small

On 01/21/2014 12:22 AM, Thomas Schmitt wrote: > >> If we take the ENDing CHS values as valid: >> 982 / 254 / 63 >> and we calculate the corresponding LBA: >> ( ( 982 + 1 ) >> x ( 254 + 1 ) >> x ( 63 ) ) >> - 1 >> ___________ >> 15'791'894 > > Is this calculation generally valid ? It seems to assume that > the

> Hi, > > > The current states of each of those drives seem to suggest that, with > > those particular values, they would not be ideal for booting > > purposes. > > For me as half-educated user all three would look like > "normal" MS-DOS disks. So people buy pitfalls. The filesystem might be OK, but not ideal for a broad compatibility for booting