search for: chs

Hi, I?ve got the following problem: When accessing a share on a Samba server from Win2000 or Windows XP this fails. The access is denied. All the shares are visible within ...\Network Neighbourhood\Workgroup\Chs-server.chs.\share1 ...\Network Neighbourhood\Workgroup\Chs-server.chs.\share2 ... ...\Network Neighbourhood\Workgroup\Chs-server.chs.\Drucker und Faxdienste Besides this I see the following ...\Network Neighbourhood\sonntag\station1\c-station1 ...\Network Neighbourhood\sonntag\station1\Daten ......

...ree would look like > "normal" MS-DOS disks. So people buy pitfalls. The filesystem might be OK, but not ideal for a broad compatibility for booting purposes. Factory-default settings are not necessarily focused on bootability. > > I cannot tell whether any of the FATs uses CHS. But the > weird H/C and S/H factors of 2 GB and 8 GB stick are > suspicious alone. > As said, their partition ends (LBA,C,H,S) have no integer > solution (X,Y) of the equation > LBA = C * X * Y + H * X + (S - 1) > > > > If we take the ENDing CHS values as valid: >...

...three USB sticks. A small observation: producers of USB drives care about sales :). Since most USB drives are used for goals other than booting, generally speaking the partitioning and formatting factory-set details are focused on parameters such as speed and disk capacity. Having a different CHS (among other details) can add some additional capacity. This additional usable space could be considered as "derisory" or "irrelevant in practical terms", but it could also be seen as good publicity when common (non-technical) people compare products to decide their next buy...

...ing. For instance, the (U)EFI standard is about a decade (or more) in the making, and it is not stable / consistent enough yet. Another one: for years the whole "booting with USB drives" was, from the point of view of the final user, almost an "art" of trial an error between CHS geometry, USB-HDD, USB-FDD, USB-ZIP,... A USB drive would work in one BIOS version, and after a BIOS update it would not; or it would work in one system but not in the other. By the time we finally have a more-or-less "commonly-used" "well-known" "most-frequently-worki...

On 01/21/2014 12:22 AM, Thomas Schmitt wrote: > >> If we take the ENDing CHS values as valid: >> 982 / 254 / 63 >> and we calculate the corresponding LBA: >> ( ( 982 + 1 ) >> x ( 254 + 1 ) >> x ( 63 ) ) >> - 1 >> ___________ >> 15'791'894 > > Is this calculation generally valid ? It seems to assume...

Hi, > I am assuming that the CHS values that you posted are not the > "amount" (Nx255x63), but the "position" The CHS values which i reported were read directly from the partition table by a hex editor. (fdisk's CHS complaints match my reading.) > "CHS 982 / 254 / 63" = "LBA 15'...

> > Ady: > > I also "forced" a FAT32 LBA filesystem, > Ronald F. Guilmette: > > *) with respect to Ultimate Boot CD (5.2.7), the answer is "CHS". > > *) with respect to OpenELEC (3.2.3, I think), the answer is "CHS". > H. Peter Anvin: > > OK, it is "CHS"... which most likely means this is a geometry problem. > Just to clarify, the two "CHS" messages were seen when booting with th...

Hi All, I had to reboot a machine as I lost the ssh connectivity to it. I could ping to it though. On rebooting, the dmesg buffer showed the following messsage hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440 end_request: I/O error, dev 16:02 (hdc), sector 1820440 hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7576/0/183, sector=1834800 end_request: I/O error, dev 16:02 (hdc), sector 1834800 hdc: dma_intr: sta...

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

...those who seek help for their troubles. I still have the factory-set contents of my three USB sticks. Maybe you can tell which of them would be a pitfall for Ronald's board: -------------------------------------------------------------- 2 GB Intenso: Partition type 0x06 (Wikipedia: FAT 16, CHS or LBA) Start LBA 32 = CHS 0 1 1 End LBA 3915775 = CHS 956 128 32 The latter has no integer solution pairs for H/C and S/H. (Neither have neighboring LBAs.) Partition content according to command "file": x86 boot sector, Microsoft Windows 98 Bootloader IO.SYS+MSDOS....

...candidate. > I await your direction. I lack the skills for explicit directions how to explore the plausible suspicions of Ady and Peter: Ady: > I also "forced" a FAT32 LBA filesystem, Ronald F. Guilmette: > *) with respect to Ultimate Boot CD (5.2.7), the answer is "CHS". > *) with respect to OpenELEC (3.2.3, I think), the answer is "CHS". H. Peter Anvin: > OK, it is "CHS"... which most likely means this is a geometry problem. But i can give some background info: CHS means Cylinder/Head/Sector addressing method. The Master Boo...

...ux.zytor.com/commit/9c8db7560e2dc83d1191bb2f90b4d4d0ae3d37d6 > Author: Michal Soltys <soltys at ziu.info> > AuthorDate: Wed, 13 Oct 2010 10:57:36 +0200 > Committer: Michal Soltys <soltys at ziu.info> > CommitDate: Wed, 13 Oct 2010 10:57:36 +0200 > > disklib: make CHS calculation match core/fs/diskio.c > > Signed-off-by: Michal Soltys <soltys at ziu.info> > I note that this code still: a) duplicates the code between read and write, and b) doesn't check for CHS overflow. This is particularly critical for write, obviously, since we could co...

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 &...

...- mbr/gptmbr.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mbr/gptmbr.S b/mbr/gptmbr.S index 7f450d3..8ab6b50 100644 --- a/mbr/gptmbr.S +++ b/mbr/gptmbr.S @@ -194,7 +194,7 @@ found_part: pushw %di /* 80 00 00 00 ee 00 00 00 - - bootable partition, type EFI (EE), no CHS information */ + - bootable partition, type EFI (ED), no CHS information */ xorl %eax,%eax movb $0x80,%al stosl -- 1.8.4.2

...t;${i}" kvm binary.img works but not with gpt -chris graff (dean) On Tue, Jan 21, 2014 at 11:07 AM, Thomas Schmitt <scdbackup at gmx.net> wrote: > Hi, > > hpa wrote: > > LBA = (C * H' * S') + (H * S') + (S - 1) > > [...] > > Start LBA 63 = CHS 0 1 1 > > End LBA 15794175 = CHS 982 254 63 > > If LBA 63 = CHS 0/1/1 then we know S'=62, but that is completely > > inconsistent with the ending sector being 63. > > Wouldn't that be S'=63 ? > 63 = (0 * H' * 63) + (1 * 63) + (1 - 1) > > W...

...tus Components mirror/m0 COMPLETE ad4 ad6 hd30# mount /dev/mirror/m0s1a on / (ufs, local, read-only) devfs on /dev (devfs, local) /dev/mirror/m0s3a on /etc (ufs, local) /dev/mirror/m0s3d on /var (ufs, local, soft-updates) hd30# boot0cfg -v /dev/mirror/m0 # flag start chs type end chs offset size 1 0x80 1: 0: 1 0xa5 1022:254:63 16065 16418430 2 0x00 1023: 0: 1 0xa5 1020:254:63 16434495 16418430 3 0x00 1021: 0: 1 0xa5 704:254:63 32852925 455539140 version=1.0 drive=0x80 mask=0xf ticks=...

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 from that. -hpa

Op 2013-12-15 om 17:39 schreef Ferenc Wagner: > Ruben Kerkhof <ruben at rubenkerkhof.com> writes: > > > /* 80 00 00 00 ee 00 00 00 > > - - bootable partition, type EFI (EE), no CHS information */ > > + - bootable partition, type EFI (ED), no CHS information */ > > Please fix the previous comment line as well. As I understand that, so in _my words_: Hello Ruben, Thank you for your patch to the Syslinux project. You spotted indeed a mismatch between code and...

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 : Las...

...uration found >> >> As far as I have been able to gather, this sort of thing is a common >> problem on various Gigabyte motherboards. >> > >What are the letters that should have been printed between SYSLINUX and >the date? There should be "EDD" or "CHS". This matters significantly. STOP THE PRESSES! Ummmm... WOW! I had to dig back into my e-mail outbox in order to reestablish enough context to be able to even try to answer your question, and it is Good that I did, because as a side-effect of trying to answer your question, I found somet...