similar to: syslinux bootsector info?

HPA, is it possible to add a parameter/argument to syslinux.com/syslinux.exe to specify a file? currently it's something like SYSLINUX A: I'd like the following also to be possible: SYSLINUX A: A:\SYSLINUX.BIN It still copies LDLINUX.BIN to A:, but writes the generated bootsector intended for drive A: to a 512byte user-specified file Perhaps to allow both at the same time even SYSLINUX

Okay, spending the time to dot t's and cross i's (or something like that), I think I have something now that can be called 3.00-worthy, so let's call it a release candidate. Changes over the earlier 3.00 prereleases: - -m and -a options now supported by the DOS installer. - PXELINUX now allows IP addresses, FQDNs, and truncated hostnames when specifying an alternate TFTP server

(I *really* need to learn this list is configured for replying to sender instead of the list itself..) Dinesh P. schreef: > Hi there, > I am using memdisk with pxelinux, i have created ms-dos boot disk from windows xp, but when i boot from it stops on starting.... > what is the problem can anybody tell me.. > please read Syslinux and Memdisk

I've recently purchased an SSD with the goal of having a portable MS-Windows installation, something which Windows 8's "Windows to Go" feature allows (install to, and boot/run from, USB flash device). Housing the SSD in an external Zalman VE300 case allows presenting ISO files as hardware CD/DVD/BD drive with inserted medium. Having the ISO files present, it's tempting

Hi! Facing a strange problem about not being able to access the floppy drive after booting from a rescue-floppy with 2.2.x kernel on an asus p4te mainboard, i searched the net and found a bug in the bootsector of the 2.2.x kernels. Before control is redirected to the kernel, the floppy drive is shut down in a way, that freezes the FD-Controller on recent mainboards (like the ASUS P4T-E). The

Hi there, I am using memdisk with pxelinux, i have created ms-dos boot disk from windows xp, but when i boot from it stops on starting.... what is the problem can anybody tell me.. Regards, Yogesh

HPA, I believe that support to boot windows CD bootsectors was broken in 3.05. I have tested 2.13, 3.00, 3.02, 3.05, 3.06, 3.08, 3.11, and 3.20pre6. All versions >= 3.05 are broken. All versions <= 3.02 work fine with the same config. The error message I get is: ================================================================ IOSLINUX 3.20 3.20-pre6 Copyright (C) 1994-2005 H. Peter Anvin

Hi, I am aware that it is impossible to netboot ISO files through pxelinux/memdisk and that there are multiple reasons for not even attempting it (like the operating system which will try to access a physical optical drive through its own drivers anyway, BIOS issues etc.). When people ask questions regarding ISO support in pxelinux/memdisk, they're mostly told to convert the ISO into a

Hello Recently I've been happily experimenting with syslinux, replacing grub and my old bootmanager. All works beautifully, but I have one question - in case of .bss bootsectors - what exactly and under what circumstances is patched in ? With syslinux used as main bootmanager - bootsectors from xp64, xp32 and [pre-syslinux] msdos 7.1 (98se) work perfectly fine when chainloaded natively as

Does SYSLINUX have any idea which DOS driveletter would be assigned to the disk it is booting from? At www.veder.com someone is trying to build a USB flash drive. However, FreeDOS does not seem to boot correctly from it (bootsector trouble maybe, or kernel itself is confusing drives), thus we're thinking of using Syslinux + Memdisk + bootimage, but somehow we want to be able to also access the

While playing with some less than usual configurations, I've got bitten few times by geometry settings in case of, usually, microsoft[ish] systems. First two examples, then the improvement idea. Example #1 My usb stick has zip-compatible geometry, which should work fine both in hdd and zip modes. It usually does, at least as far as syslinux and normal software is considered - excluding

The second RC build of the 10.0-RELEASE release cycle is now available on the FTP servers for the amd64, i386, ia64, powerpc, powerpc64 and sparc64 architectures. The image checksums follow at the end of this email. ISO images and, for architectures that support it, the memory stick images are available here (or any of the FreeBSD mirror sites):

Hi i want to add the FreeBSD 6.2 release to our installserver according to the manual http://syslinux.zytor.com/archives/2007-April/008420.html But if I type FreeBSD-6.2 at the pxelinux boot prompt the created image load but nothing happens. ?boot: FreeBSD-6.2 Loading memdisk.... Loading

Hello :-) I am installing the 9.2-RC1 bootonly iso which wants to download stuff from snapshots while it is in releases directory: Installer wants to get 9.2-RC1 stuff from here (where it is missing): ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/i386/ While the stuff is at: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/i386/9.2-RC1/ Please fix :-) Best regards :-) Tomek -- CeDeROM,

Does anyone know how to install the gptmbr.bin onto a USB drive with Windows? I noticed that it would be really easy to modify the source of the installer to install gptmbr.bin instead of mbr.bin with the -m flag, but I'd like a solution that doesn't require me to maintain my own custom syslinux. I'm open to writing and submitting a patch to add a new flag (say -g) to install

Hi I'm using memdisk as part of CD Shell' isolinux. I've created custom floppy disk image 8440kB size. I've put FreeDOS kernel and bootsector into the floppy. Boot process goes fine with this command: isolinux /boot/memdisk initrd=/ximg/fdos.img c=60 h=8 s=36 floppy The problems begin when I try to run FreeDOS memory manager emm386 from the floppy image. my config.sys: ...

>that image under B: or X: or whatever. This will allow us to cross the >size limit of 2.88MB floppies. Ofcourse when I say "mount" I dont expect >memdisk to mount it, just that set things up so that DOS mounts it there. I'm using a 5MB image which emulates floppydisk. label test kernel data/memdisk append initrd=data2/test.img c=80 h=8 s=18 floppy problems are

Hello all, I've been following this project with interest, and have had great fun implementing Isolinux within the FreeDOS cdrom distribution. Since I'm not that an expert at Linux, I would like to know how I can *succesfully* generate a bootable image from a partition. Situation is like this: (640MB RAM on system) 60GB IDE harddisk, primary partition 1 win98 500MB extended partition

HPA, a longterm reminder. See below. Can you also make a LABEL ignore other labels if no KERNEL statement is found in between? That way you could define multiple aliasses for an entry. label foo label bar label memtest kernel memtestp foo ignores 'label bar' , 'label memtest' and executes 'kernel memtest' bar ignores 'label memtest' and executes 'kernel

On 2019-4-13 8:45, Lu Wei wrote: > On 2019-4-13 4:23, C. Masloch via Syslinux wrote: >> MS-DOS 7.10 (first appearing in MSW 95 OSR2, later re-used in MSW 98 >> and 98 SE) and 8.00 (MSW Me, and MSW XP DOS boot diskettes) both >> support FAT32 equally well. >> >> MS-DOS 8.00 (without some patches that are around) only supports >> booting in DOS mode from