similar to: Feature request

Hi to all, this is my first post to this list. First I apologize for my English. I opened a site with a lot of contents about Isolinux (some programs for Win32 and some documents for newbies). Please visit my site because I need a feedback if all there is right (IsoLinux HowTo for newbies). Maybe somebody can find some mistakes in my texts and provide me with right informations. Site adress is :

On 07/09/2014 04:00 PM, H. Peter Anvin wrote: > > So this would seem consistent that this is the FAT12/FAT16 boundary that > breaks stuff. Perhaps FreeDOS has a problem with FAT16 on floppies? If I understand things correctly, a bootable floppy has two key pieces of executable code: the 512-byte boot sector, and the kernel loaded by that boot sector. The kernel can be large, and thus

Recently (and for ages, I'm sure) folks have suffered partition destruction and had to try and recover. In the recent thread, the victim eventually had to resort to Google and fond some package that I can not remember now. Well, I was perusing my YumInfo.lst.05, for general info, and I discovered this (potential) little gem. Thought I would pass it on and make it "more googleable"

On 07/09/2014 01:54 PM, Alexander Perlis wrote: > > Ah, this might explain things although I don't know what is meant by > "intended". First, to clarify, newmkfloppyimg calls mkdosfs 3.0.12, and > grabs H/S from the output and then computes C. For all the sizes I've > tried, newmkfloppyimg always tells me H=64 S=32 and then C is the > approximately the number

Hey Peter! Great work on the SYSLINUX project! I spent three days noodling over how to accomplish *exactly* what your ISOLINUX/MEMDISK combination does! Even a blind hog finds an acorn from time to time. I have it working great using the crpack utility suite from http://www.nu2.nu and one of Bart Lagerweij's techniques employs your SYSLINUX utilities - you probably already know all about

> 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

> Hello, > > Ady via Syslinux said on Sun, Oct 25, 2015 at 08:15:37PM +0200: > >_ Creating filesystem that _does_ conform to ISO-9660; > > I think the only issue is with a tag. That same image boots with grub > 0.99 I understand. My point is, in theory, "everything" is frequently expected to work as it was designed; in practice, it is not. So my suggestions

The narod.ru images are super outdated (FreeDOS kernel 2028) unfortunately. If you are interested I could provide a 5MB FDD image template based on FreeDOS 2041 kernel (the latest available at that time in 2014) where you would just inject your ROM and EXE (and possibly adjust autoexec.bat to autostart/apply the FW update). It's a minimal FreeDOS FDD image that defaults to a clean boot with

Hi, I did found the problem, a combination of 2 factor. 1- I taught that I did install the latest syslinux, but in fact it was the 3.36 version. 2- Thank to kevin Connelly, he point me to a problem he got with mkdosfs command. The default FAT16 do not work, but the FAT12 do. By adding -F12 to the mkdosfs command fix the problem. The default F16 do seem to work for <8M floppy image. Thank you

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

On Sat, Jan 6, 2018 at 12:34 PM, Avi Deitcher <avi at deitcher.net> wrote: >> > Is the build process documented? Or am I just going to have to plod >> > through >> > the makefiles? >> >> I don't think so. > Oh well... >> > 1. Run installer >> > 2. Installer loads ldlinux.sys onto the filesystem (and copies >> >

> > > Is the build process documented? Or am I just going to have to plod > through > > the makefiles? > > I don't think so. > Oh well... > > 1. Run installer > > 2. Installer loads ldlinux.sys onto the filesystem (and copies > ldlinux.c32, > > but irrelevant for now). > > 3. Installer calculates which blocks in the filesystem contain

Hi all: I'm new here. Sorry if my question is so stupid. I want to make a cd bootable whit 3-4 floppys (to install msdos for ex.) My fisrt disk boots fine but when it wants the next disk check to a: not to cdrom /isolinux dir and not to cdrom root... :-( How do I do wrong? Thanks Regards Chema

On Wed, Jan 3, 2018 at 2:38 AM, Avi Deitcher <avi at deitcher.net> wrote: > Gene, thanks for doing "Reply-All". I only get digest, so this keeps me in > the loop. Appreciated. > >> > which appears to be included in diskstart.inc. I will have to dig in and >> > see >> > how this all gets compiled (pointers always appreciated :-) ). >>

Latest syslinux 2.00 stable version from freshmeat. Are the programs that will just copy boot sectors or create boot sectors for /dev/hda1, /dev/hda2 etc.. that I can simply copy with a dd command? Mohan -----Original Message----- From: leaf-user-admin at lists.sourceforge.net [mailto:leaf-user-admin at lists.sourceforge.net]On Behalf Of Luis.F.Correia Sent: 05 November 2002 15:01 To: leaf-user

-----Original Message----- From: S Mohan [mailto:smohan at vsnl.com] Sent: 05 November 2002 16:13 To: Luis.F.Correia; leaf-user at lists.sourceforge.net Subject: RE: [leaf-user] (no subject) I know that is the proper way. Unfortunately, I'm stuck and am mad at myself for that. Error message: ERROR 440D: Unable to lock drive for exclusive access - when I use syslinux 2.00 from freshmeat.

I downloaded DOS6.22 image from putergeek.com. Used fdisk from that floppy and format from that floppy. Still no luck. If I execute fdisk under leaf (monkeynoodle.org) as fdisk/dev/hdc, and give p for print partition table, I get the following: Disk /dev/hdc: 16 heads, 32 sectors, 123 cylinders. Units = cylinders of 512 * 512 bytes Device Boot Start End Blocks Id System /dev/hdc1

Hi, I just found syslinux gives corrupt data when reading files from a FAT16 partition. The fat16 implementation was using the reserved Dir_FstClusHi (offset 20 in the directory entry, name quoted from VFAT spec from Microsoft) which is supposed to be 0 for FAT12 and FAT16. Linux ignores this and never uses the Dir_FstClusHi cluster with 0 for FAT16/12, so it works fine. >From the spec:

> Hi, > > Didier Spaier wrote: > > http://slint.fr/testing/slint64-14.1_syslinux.6.03/slint64-14.1_syslinux.6.03.img > > This looks like the content of an EFI system partition. > Exactly what i need for experiments. Thanks a lot. > I'm sorry to say that, for testing the possibility of booting optical media in UEFI X64 mode by means of syslinux.efi, that image

I'm home at last. I did a mixture of things. I downloaded DOS6.22 floppy from putergeeks.com, extracted my old syslinux 1.75 (dos version) into the same boot floppy and made my CF /dev/hda1 as suggested by Luis (Hail O King - my saviour). Lo and behold it went thro' like a hot knife thro' butter. syslinux did not complain at all. I did an xcopy /s of my D: (hard disk) to my C:(CF) and