The latest official version of Syslinux can be downloaded in.tar.gz,.tar.bz2,.tar.xz, and.zip formats from kernel.org.This download includes both the source and official pre-compiled binaries that should work for most users (See also Official Binaries).Version changes are available in the.LSM files.
I have tried many ways to solve this problem, but only your way works fine.

0 blueprints and 0 bugs targeted. There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release. In this case, there is NO NEED for a special syslinux-6.2 version because the binaries that can already be found in syslinux-6.03 will work just as well, therefore there is no 20151222 subdirectory on the server, as Rufus will be smart enough to fall back to the parent directory provided you don't have network issues, which you do. Bugzilla will be offline for an upgrade to version 5.0 and migration to new hardware starting at 23:00 UTC, 2018-09-07. The outage is expected to last 12 hours.

re requiring a Syslinux version that is not listed under https://rufus.akeo.ie/files/syslinux-6.03/

That's because the default version of Syslinux 6.03 will work.

Please understand that, because distros tend to recompile their own version, but most of the times with minimal changes, Rufus uses a fallback mechanism when it looks for Syslinux and there will only be a specific Syslinux-x.y_##### directory IF it happens that the version from the distro is ACTUALLY incompatible with the official Syslinux-x.y binary. If not, then Rufus will fall back to using the official binary.

In this case, there is NO NEED for a special syslinux-6.03_20151222 version because the binaries that can already be found in syslinux-6.03 will work just as well, therefore there is no 20151222 subdirectory on the server, as Rufus will be smart enough to fall back to the parent directory provided you don't have network issues, which you do.

Moreover, even if you have a network issue, the version of Syslinux that would have been downloaded in your case is exactly the same as the one found on the server, because the 6.03 embedded in Rufus is the same as the one at https://rufus.akeo.ie/files/syslinux-6.03/, so this is a non issue.

Unless you actually experience an issue with Syslinux during boot, you shouldn't assume that there is an issue with the Syslinux downloads (though I have to state that getting a The server name could not be resolved. message indicates a network error on your side, which has nothing to do with Rufus). The fact is that:

The directories you mention don't exist because they aren't needed
The fallback mechanism worked exactly as expected, even with your network issue, and you did end up with a drive that boots as expected.

Therefore I will close this (non) issue.

SYSLINUX
Preview release
Developer(s)	H. Peter Anvin
Stable release	6.03 / October 6, 2014; 4 years ago
Repository
Operating system	Linux
Type	Boot loader
License	GNU GPL version 2 or later
Website	www.syslinux.org

The SYSLINUX Project is a suite of lightweight master boot record (MBR) boot loaders for starting up IBM PC compatiblecomputers with the Linux kernel. Primarily developed by H. Peter Anvin, the SYSLINUX bundle consists of several separate systems used for different purposes, including ISOLINUX, PXELINUX and EXTLINUX.

2Use
3COMBOOT

List[edit]

The original SYSLINUX, used for booting from FAT and NTFS filesystems (such as floppy disks and USB drives).
ISOLINUX, used for booting from CD-ROMISO 9660 filesystems.
PXELINUX, used for booting from a network server using the Preboot Execution Environment (PXE) system.
EXTLINUX, used to boot from Linuxext2/ext3/ext4, XFS, Btrfs, or UFS/UFS2 filesystems. FAT and NTFS are also supported.
MEMDISK, used to boot older operating systems like MS-DOS from these media.
Two separate menu systems.
A development environment for additional modules.

Use[edit]

Syslinux Package

SYSLINUX and ISOLINUX[edit]

SYSLINUX is not normally used for booting full Linux installations since Linux is not normally installed on FAT filesystems. Instead, it is often used for boot or rescue floppy discs, live USBs, or other lightweight boot systems. ISOLINUX is generally used by Linux live CDs and bootable install CDs.

A minor complication is involved when booting from CD-ROM. The El Torito standard allows booting in two different modes:

Floppy emulation mode – the boot information is stored in an image file of a FAT-formatted floppy disk, which is loaded from the CD and then behaves as a virtual floppy disk. This mode uses SYSLINUX.
No emulation mode – the boot information is stored directly on the CD (not in a floppy image). This mode uses ISOLINUX.

To have this choice is sometimes useful, since ISOLINUX is vulnerable to BIOS bugs; for that reason, it is handy to be able to boot using SYSLINUX. This mostly affects computers built before about 1999, and, in fact, for modern computers no emulation mode is generally the more reliable method.

The use of SYSLINUX for the creation of Live USBs is growing, though, and allowing the creation of distributions like Slax that allow users to try Linux with complete interactivity and persistent changes without needing to install it on their hard disk.

Newer ISOLINUX versions allow creation of so-called 'hybrid ISO' images, that put both CD el-torito and HDD MBR boot records into an ISO image, which lets users use a single image as either a CD/DVD boot or USB boot.^[1]

PXELINUX[edit]

PXELINUX is used in conjunction with a PXE-compliant ROM on a network interface controller (NIC), which establishes a PXE environment that uses DHCP or BOOTP to configure its minimalistic networking stack capable of UDP/IP networking, and then downloads a bootstrap program using TFTP. This bootstrap program loads and configures an operating system kernel according to directives that are also downloaded from the TFTP server; after the kernel is booted, it sets up its own drivers for network devices, establishes networking configuration, etc. and carries out desired tasks on its own.^[2]

Typically, PXELINUX is used for performing Linux installations from a central network server or for booting diskless workstations.

EXTLINUX[edit]

EXTLINUX is typically used as a general-purpose bootloader, similar to LILO or GRUB.Since Syslinux 4, EXTLINUX has been merged with SYSLINUX.

COMBOOT[edit]

SYSLINUX can be extended by COMBOOT modules written in C or assembly language. 32-bit modules typically use file extension .c32. Since version 5 16-bit .com modules are no longer supported.^[3]

Hardware Detection Tool (HDT)[edit]

Since the 3.74 release, the Syslinux project hosts the Hardware Detection Tool (HDT) project.

This tool is a Syslinux com32 module, licensed under GNU GPL, which displays low-level information for any x86-compatible system. It provides both a command-line interface and a semi-graphical menu mode for browsing. HDT is available as a com32 file, a bootable ISO and a 2.88 MB floppy disk image.

List[edit]

Use[edit]

Syslinux Package

SYSLINUX and ISOLINUX[edit]

PXELINUX[edit]

EXTLINUX[edit]

COMBOOT[edit]

Hardware Detection Tool (HDT)[edit]

Syslinux For Windows

See also[edit]

Syslinux 6.03 Download

References[edit]