similar to: Advice/directions to users of Syslinux

> Hi, > > Ady wrote: > > I personally don't like this "hiding" [of CHS], but I understand > > their reasons to do so. > > > > I think that the "USB-Geometry" section in the wiki should try to > > point to the same kind of users. > > But it is in wiki page Hardware_Compatibility. > Check out the neighborhood. > If there

I'm playing with syslinux 3.0x to get PC to boot from USB key... In particular, I'm giving a look at the "ZIP geometry hack" to get some more BIOS boot working with USB... Some question: - if we have a usbkey with a single partition, can we change the geometry without requiring to reformat the partition? Or is a reformat unavoidable? - at the moment we can use the "ZIP

Hi, me: > > But MiB alignment does not match 255x63 cylinders. (Or at least > > only in very large steps. They share no prime factors except > > the block size.) Ady: > It doesn't matter. My test.img for Ronald had Nx255x63 geometry, and > STARTing LBA of 2048. Yeah. It has end CHS 89,69,35. But it lacks the other ingredient of the mess: a CHS driven filesystem.

Hi, Ady wrote: > I personally don't like this "hiding" [of CHS], but I understand > their reasons to do so. > > I think that the "USB-Geometry" section in the wiki should try to > point to the same kind of users. But it is in wiki page Hardware_Compatibility. Check out the neighborhood. If there is a place to - for once - state how a "normal"

In message <2008564557425199875 at scdbackup.webframe.org>, "Thomas Schmitt" <scdbackup at gmx.net> wrote: >Ronald F. Guilmette wrote: >> what exactly did we determine that GA-M55Plus-S3G is failing >> to support? > >It appears to be related to the choice of CHS addressing with >the FAT filesystem. This opens the door for misperceived factors >of

Tying up lose ends, and adding the ethersel module for the Etherboot folks. -hpa Changes in 3.02: * SYSLINUX: The "unix" installer now sets the MS-DOS attributes (hidden, system, readonly.) * COM32 library: build the .lnx (test modules for running under Linux) as architecture native modules, in case i386 devel libraries aren't

> > Both sticks show very unusual factors for heads and sectors > > which are hardly intentional. If BIOS gets confused like fdisk, > > then the failure to find files is quite plausible. > > > > ------------------------------------------------------------- > > > > Could you please exercise what is described for Linux in > >

Hi, Ady: > > > I would suggest not using the work "disk". me: > > I am unhappy with "disk" too. > > But that change would have a much wider scope in the text. Ady: > You can still use a different wording in a linked section. If "disk" > is not the best choice for the new section, then choose a better > term. Two problems: There are

> I meanwhile united the section "USB Miscellenous" with > http://www.syslinux.org/wiki/index.php/Hardware_Compatibility#USB-Geometry > Now it is a bit too long but does not show an artificial > separation of general statements and examples. > It is a vague as needed and as tangible as possible, i think. > > Please have a look and criticize. Any objection is

Hi, Ady wrote: > I would suggest adding an internal link to respctive sections of the > wiki, not more text in the same page. This is reasonable. Please have a look at http://www.syslinux.org/wiki/index.php/User:Scdbackup The first section shall become the new text of http://www.syslinux.org/wiki/index.php/SYSLINUX#Creating_a_Bootable_Disk The second section shall become a new

Hi, Ronald F. Guilmette wrote: > what exactly did we determine that GA-M55Plus-S3G is failing > to support? It appears to be related to the choice of CHS addressing with the FAT filesystem. This opens the door for misperceived factors of heads per cylinder and sectors per heads. My current suspicion is that the partition end did not expose the effective factors in its end CHS address, so

I played with `mkdiskimage' some last night, here is what i came up with: mkdiskimage -z -F binary.img 1000 i="$(losetup -f --show binary.img)" j="$(kpartx -savu "${i}" | awk '{print "/dev/mapper/"$3 }')" mount "${j}" /mnt cp /usr/lib/syslinux/vesamenu.c32 /mnt cat > /mnt/syslinux.cfg <<EOF UI vesamenu.c32 DEFAULT linux LABEL

On 01/21/2014 11:13 AM, Thomas Schmitt wrote: > > My current theory is that vendors prefer to record > a cylinder aligned end CHS address over recording > an end CHS address which exploits the whole capacity. > This is used as an (inofficial ?) protocol to publish > the CHS factors H' and S'. > Indeed it is -- at least some BIOSes "deduce" the H/S to use

Hi, I'm trying to make a USB-ZIP bootable filesystem on my USBkey, which is 2GB. The problem is that "mkdiskimage -4 /dev/sda 0 64 32" fails due to the large size. The number of sectors is 4005888/(64*32) = 1956, which is more than the maximum 1024. Is there any way around this or is it just not possible to make this USBkey look like a Zip drive? Regards, Ole Jacob

Some people have reported portability problems with SYSLINUX 3.00, mostly due to the use of HDIO_GETGEO_BIG, which is deprecated; additionally, the advanced menu system wouldn't build for everyone due to a spurious reference to %ebp. This release fixes these things, plus makes the extlinux installer default to zipdisk geometry (64 heads, 32 sectors) if it can't guess anything else.

btw, that works with mkfs.vfat as well. just have to use syslinux with a syslinux.cfg file instead of extlinux with an extlinux.conf. On Tue, Jan 21, 2014 at 11:58 AM, Dean Graff <graff97 at gmail.com> wrote: > the closest i have gotten to a consistent way to test a MS-DOS filesystem > setup is: > > dd if=/dev/zero of=binary.img bs=1M count=500 > i="$(losetup -f --show

Hi, i have now sparsely modified the last paragraph of http://www.syslinux.org/wiki/index.php/SYSLINUX#Creating_a_Bootable_Disk added a new section http://www.syslinux.org/wiki/index.php/Common_Problems#Bad_Heritage_on_MS_DOS_disk and a new article http://www.syslinux.org/wiki/index.php/What_is_a_SYSLINUX_disk_%3F My proposal is to place a link to the new article at all wiki occasions,

I was trying to setup dsl (damn small linux) to boot off a usb drive. I found my BIOS wasn't booting from it when using a USB-HDD mode so I found a page for using SYSLINUX to set it up in USB-ZIP mode (http://syslinux.zytor.com/usbkey.php). I made a mistake and (doing exactly what the page warned against not doing) used the mkdiskimage command on the wrong drive (a 230Gb NTFS external

the closest i have gotten to a consistent way to test a MS-DOS filesystem setup is: dd if=/dev/zero of=binary.img bs=1M count=500 i="$(losetup -f --show binary.img )" parted binary.img mklabel msdos -s -m dd if=/usr/lib/syslinux/mbr.bin of="${i}" parted binary.img mkpart primary -a optimal -s -m 0% 100% parted binary.img set 1 boot on mkfs.ext4 $(kpartx -savu "${i}"

> Hi, > > me: > > > But MiB alignment does not match 255x63 cylinders. (Or at least > > > only in very large steps. They share no prime factors except > > > the block size.) > > Ady: > > It doesn't matter. My test.img for Ronald had Nx255x63 geometry, and > > STARTing LBA of 2048. > > Yeah. It has end CHS 89,69,35. > But it