Displaying 20 results from an estimated 2000 matches similar to: "wiki account request"
2014 Jan 22
0
wiki account request
On Wed, Jan 22, 2014 at 3:20 AM, Thomas Schmitt <scdbackup at gmx.net> wrote:
>
> Now in a new thread with updated subject.
>
> ----- Forwarded message from Thomas Schmitt -----
>
> Date: Wed, 22 Jan 2014 08:45:51 +0100
>>From: Thomas Schmitt
> To: syslinux at zytor.com
> Subject: Re: [syslinux] Advice/directions to users of Syslinux
> Message-Id:
2014 Jan 22
5
Advice/directions to users of Syslinux
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
2014 Jan 19
3
Advice/directions to users of Syslinux
In message <70229.1390169666 at server1.tristatelogic.com>, I wrote:
>In message <52DC29E3.7080004 at mattiasschlenker.de>,
>Mattias Schlenker <ms at mattiasschlenker.de> wrote:
>
>>To cut a log story short, we probably should write some advices for best
>>practices of creating bootable media...
>...
>
2014 Jan 22
0
Advice/directions to users of Syslinux
> 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
2014 Jan 22
2
Advice/directions to users of Syslinux
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
2014 Jan 22
2
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"
2014 Jan 21
6
After USB boot problems on Gigabyte GA-M55Plus-S3G
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
2014 Jan 17
6
USB boot problems on Gigabyte GA-M55Plus-S3G
In message <1767645779554124797 at scdbackup.webframe.org>,
"Thomas Schmitt" <scdbackup at gmx.net> wrote:
>Hi,
>
>> > debian-7.3.0-i386-netinst.iso
>> This image also boots with no problems on the GA-M55Plus-S3G.
>
>So isohybrid boots with and without additional GPT.
>It boots with partition start 0 and with partition start at 32 kB.
OK. If
2014 Jan 22
0
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
2014 Jan 20
5
USB boot problems on Gigabyte GA-M55Plus-S3G
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
2014 Jan 22
4
Advice/directions to users of Syslinux
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.
2017 Mar 22
4
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
Hi,
funny or enlightening observation:
With my qemu-system-i386 it would work if the detected Heads/Cylinder and
Sectors/Head factors would change positions !
The effective read operation seems to use H/C = 32 , S/H = 63.
The correct LBA would be addressed by H/C = 63 , S/H = 32.
--------------------------------------------------------------------------
Reasoning:
I have transplanted the
2014 Jan 22
3
wiki account request
Hi,
me:
> > Please enable editing.
Gene Cumm:
> Done.
Thanks.
I have now edited
http://www.syslinux.org/wiki/index.php/Hardware_Compatibility#USB-Miscellaneous
------------------------------------------------------------
Next i'll try to develop a user oriented hint for
SYSLINUX#Creating_a_Bootable_Disk
which takes into respect the opinions of Ady, Mattias, me,
and of any
2014 Jan 21
2
After USB boot problems on Gigabyte GA-M55Plus-S3G
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}"
2014 Jan 22
1
Advice/directions to users of Syslinux
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
2014 Jul 23
3
DELL E6510 pxelinux issues
Hello,
I have a problem with our DELL E6510 notebooks (BIOS version A05):
1. After the update from syslinux-3.71 to 4.02 LOCALBOOT no longer
works. I've read
<http://www.syslinux.org/wiki/index.php/Hardware_Compatibility#LOCALBOOT_on_Dell_Latitude_E6400>
and neither version works. The behavior differs between the laptop
rebooting automatically and getting stuck.
I checked all versions
2014 Jan 22
6
After USB boot problems on Gigabyte GA-M55Plus-S3G
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
2014 Jan 15
4
USB boot problems on Gigabyte GA-M55Plus-S3G
[disclaimer: I am the author of Rufus]
Hi,
On 2014.01.15 10:10, Thomas Schmitt wrote:
> As producer of MBRs i wonder where that LBA-flag is located.
> In bit 0 to bit 6 of byte 446 (where bit 7 means active/bootable) ?
I haven't looked at what GParted does, so I may be off mark, but I have
a strong suspicion that this LBA "flag" is a fake flag that simply
indicates if a
2013 Dec 08
1
About the google-invisibility of this list
Hi,
i wondered why our happy bug hunt about the uninitialized
register did not pop up in Google during a search for
recent mentionings of xorriso.
Wasn't there a thread about google-invisibility a few months
ago ?
So i began to watch and made an experiment.
Can it be that this HTML tag
META NAME="robots" CONTENT="noindex,follow"
in
2017 Mar 22
3
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
Hi,
Ady wrote:
> If a specific BIOS' CHS/LBA translations cannot cope with the above, it
> is no surprise that we get some mess, somewhere.
Currently my suspicion is that the isohdpfx.S code simply mishandles
the two conversion factors which it correctly got from BIOS call
INT 13H AH 8.
> Boot System ID : First : Last : Relative : Number of:
> Flag