similar to: syslinux write intended bootsector to bootsectorfile support?

Mr Anvin, is there a specific loading address used with the Syslinux bootsector (to load ldlinux.sys)? like msdos 0x70, freedos 0x60 we're trying to have a SYS program that can create bootsector for other OS's than FreeDOS only. not much luck though :( this way I'm trying to avoid the use of syslinux.exe/com (need the diskspace that it would save by not including this program) I

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

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

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

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

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

>information a bit closer; it'd find that it's marked accordingly. UDMA2.SYS author now worked around it, it seems you do something with "DPTE" in isolinux.asm but not using it (probably for memdisk or direct floppy/harddisk emulation?). also something about EDD v1.1 and v3.0 specifications and setting bits to 1. Anyway, the driver works now on: BIOS -> cdrom ->

On Tue, Jan 21, 2014 at 2:41 PM, mike setzer <qualityana at sbcglobal.net> wrote: > hello Gene, > > good to get your message > > I have not seen a link to reply to a particular thread, > so I am replying to you right now > hopefully the thread can be made to look right, also I double posted since my connection was lost > right during the first posting. Sorry, I

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

Hi, I've coded loading NT cdrom bootsector into isolinux 1.68 myself (http://www.nu2.nu/bootcd/#multimemdisk) and I now see you have included it in isolinux 1.73 and higher. Great!!! I tried it using isolinux 1.74 and 1.75pre2, but I cannot get it to work. It says: -- Loading Invalid or corrupt kernel image. -- I use the file extension ".bin" as I see in the isolinux.asm source,

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

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

(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

Dear Everybody! I want to export data to LaTeX. As I want to employ the data as freely as possible I want to avoid the xtable-command and instead generate some List like \MyOwnPrettyCommand{Adam}{Auer}{17} \MyOwnPrettyCommand{Bertram}{Bauer}{14} \MyOwnPrettyCommand{Christoph}{Huber}{75} \MyOwnPrettyCommand{Damian}{Dorfer}{69} \MyOwnPrettyCommand{Emanuel}{Eder}{43} with \MyOwnPrittyCommand

Jessica Mydek is a hoax. Check outthe American Cancer Society pages to confirm this if you wish: http://www.cancer.org/chain.html Regardless of that, such a message had/has no place on a list devoted to the discussion of Samba. Please do NOT use this list for ANY purpose other than the discussion of Samba, no matter how worthy the cause may seem. Thanks, K (assistant list admin)

Hi, I very new to wine and do not have much knowledge. Sorry for that, but I'm trying to spend more time on wine. I want to run the Checkpoint FW-1 for NG Policy Editor under Linux. So I thought, maybi it's possible with wine to do so. I downloaded the wine-20011106-1.i386.rpm and the wine-devel-20011106-1.i386.rpm on my RedHat 7.1 System and installed it. I'm using the standard

Hello Bernd, I think you might wanna known this. Cheers Geert Stappers ----- Forwarded message from postmaster at fontys.nl ----- From: postmaster at fontys.nl To: stappers at stappers.nl Subject: Delivery Status Notification (Failure) Date: Sun, 13 Mar 2005 23:56:03 +0100 This is an automatically generated Delivery Status Notification. Delivery to the following recipients failed.

Hi Mr Anvin, after downloading the Freedos bootable cd, which now uses your projects (ISOLINUX & MEMDISK) instead of Bart Lagerweij's DISKEMU (www.nu2.nu), I contacted the creator of the freedos cdrom. I was interested in how he did make that cd bootable. Now I understand it a bit. As I'm a MS Windows user, I had to figure some things out. However, upon booting I get a beautiful

>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