search for: fatxx

I have been trying to boot a kernel I compiled. I tried 2 different USB thumb drives. I tried win32 syslinux 3.31 and 3.36 with no luck. I even tried another known good kernel for testing purposes. After syslinux starts I get "Invalid or corrupt kernel image" but I don't think it is even really trying to run it. The last time I built a kernel about 1-1/2 years ago you could put a

I have read the documentation, performed the diagnostic tests, checked the archives, so if the answer is there, please accept my apologies in advance and simply direct me. I am running redhat Linux 2.0.3 and using smbmount to mount several directories from NT3.51 servers which are distributed gloablly in different timezones. Once mounted the files all have local timestamps which makes syncing

...you're going to boot the image with MEMDISK, be sure to also pass "edd" to MEMDISK so that it will respond to the LBA-based INT13 calls. 8) If you don't want to use the Perl script from the prior paragraph, you can instead use the SYSLINUX approach: running syslinux against a FATxx image file will detect the FAT type and put a tailored syslinux boot sector and syslinux kernel in the image, and then you'll also need a small syslinux.cfg and chain.c32, to then chain over to your FreeDOS kernel.sys. But note that if you run newmkfloppyimg.sh to enlarge such a syslinux-ba...

I'm potentially about to deploy a samba 3.0.11 file server on RHEL 3.4 or perhaps 4.0 and before i do i'm wondering if it can do a couple things. I read the howto and googled but didn't find exactly what i was looking for. Most importantly i'm wondering if it can implement the create dir/append to file permissions. My client wants users to be able to create files on the server

Hi there guys! I want to set up Puppy-Linux to run off a 2GB USB key-drive in native mode (I.e. not as a virtual machine, which I'm finding runs too slow on my system, under XP.) To test it out, I want to run off a 150GB USB HDD. Now this drive is NTFS formatted and way bigger than the 1GB file structure limit that I read about in the Syslinux documentation. There's only one

...the image with MEMDISK, be sure to also pass "edd" to > MEMDISK so that it will respond to the LBA-based INT13 calls. > > 8) If you don't want to use the Perl script from the prior paragraph, > you can instead use the SYSLINUX approach: running syslinux against a > FATxx image file will detect the FAT type and put a tailored syslinux > boot sector and syslinux kernel in the image, and then you'll also need > a small syslinux.cfg and chain.c32, to then chain over to your FreeDOS > kernel.sys. But note that if you run newmkfloppyimg.sh to enlarge such...

Hi all, I am at the end of my wits, after a day and a half of mucking around with this :) My intention was to take a multi-boot DVD - of the style you get with an MSDN subscription - and burn an individual installer to disc. How to do this? My theory was to take the files for the installation CD, add isolinux, add a bootsector, and away I go. Unfortunately it doesn't seem this easy. So I

> > Message: 5 > Date: Sat, 28 Apr 2007 11:37:51 -0700 > From: "J.H." <warthog19 at eaglescrag.net> > Subject: Re: [syslinux] USB stick meets ISO system > To: Geert Stappers <stappers at stappers.nl> > Cc: syslinux at zytor.com > Message-ID: <1177785471.25140.29.camel at localhost.localdomain> > Content-Type: text/plain > > On Sat,

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