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 is a place to - for once - state how a "normal"

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 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, > > 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

Hi, > 1_ "create a new DOS partition table"; > 2_ create a new partition; > 3_ format it. This could be added to http://www.syslinux.org/wiki/index.php/SYSLINUX#Creating_a_Bootable_Disk statement: "In order to create a bootable disk using SYSLINUX, prepare a normal MS-DOS formatted disk." Like "If in doubt, make a backup of your disk content, create

In message <32488642060905516076 at scdbackup.webframe.org>, "Thomas Schmitt" <scdbackup at gmx.net> wrote: >I am unhappy with "disk" too. >But that change would have a much wider scope in the text. s/disk/mass storage device/g >"Disk" is the term used by the starting point of the partitioning >endeavor in SYSLINUX#Creating_a_Bootable_Disk

Hi, hpa: > The mkdiskimage tool in the Syslinux distribution exists for this reason. Then http://www.syslinux.org/wiki/index.php/SYSLINUX#Creating_a_Bootable_Disk should point to a tutorial for mkdiskimage. I cannot spot any occurence of "mkdiskimage" in http://www.syslinux.org/wiki/index.php/SYSLINUX http://www.syslinux.org/wiki/index.php/HowTos Is there already a

Hi, Ronald F. Guilmette: > > Doesn't the Syslinux project provide (hopefully strong) specific > > reccomendations, [...] hpa: > We try (see our wiki), The general wiki http://www.syslinux.org/wiki/index.php/SYSLINUX#Creating_a_Bootable_Disk says "In order to create a bootable disk using SYSLINUX, prepare a normal MS-DOS formatted disk." which would not have

Hi, Dean Graff wrote: > Also, I am trying to use the syntax: > > mkdiskimage -z -F -4 binary.img 1000 > > To get that zip drive geometry for my images and increase the > portable ness of their boot ability. Will this work, to make the zip > drive geometry and then dd or cat this to the 'mass storage device' ? The copy program should not care what is in the image

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

> 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

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

Hi, i now realized that http://www.syslinux.org/wiki/index.php/Hardware_Compatibility#USB-Geometry http://www.syslinux.org/wiki/index.php/Hardware_Compatibility#USB-Miscellaneous are the new wiki sections by Gene Cumm. (Sorry for not reading them when they were announced.) So i ask especially him whether the statement "An examle is a drive of 128,64,32 with a partition ending at

> 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

> > 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, > > Ronald F. Guilmette: > > > Doesn't the Syslinux project provide (hopefully strong) specific > > > reccomendations, [...] > > hpa: > > We try (see our wiki), > > The general wiki > http://www.syslinux.org/wiki/index.php/SYSLINUX#Creating_a_Bootable_Disk > says > "In order to create a bootable disk using SYSLINUX, prepare

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

On 01/19/2014 03:47 PM, Ronald F. Guilmette wrote: > > Doesn't the Syslinux project provide (hopefully strong) specific > reccomendations, to its user base, for how these things should best > be done, you know, in order to insure maximal interoperability? > We try (see our wiki), but those recommendations can only come from mass testing across many, many systems -- which we

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

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