search for: 1325055

...write(1, buf, 512); if(ret != 512) break; } return 0; } ------------------------------------------------------------------ (It could be shorter if i did not insist in big endian words.) To be compiled by cc -o block_seq block_seq.c and used like ./block_seq | dd bs=512 skip=1 count=1325055 seek=1 of=/dev/sdc to overwrite the ISO except the MBR. (1325056 blocks is the size of the Debian ISO in question. One could of course fill the whole stick until it throws an i/o error.) The block at LBA 1 bears as content 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00 01 ... The...

Thomas Schmitt wrote: > So if we had a MBR which prints the content of the first 512 read bytes > we could tell whether they are block aligned and from which block they > come. Ok. I'll try. Is it the isohdppx or isohdpfx (or both) that is relevant? Meanwhile I have a hacked isohdppx.bin that prints: G if GPT M if MBR <nothing> if no partition info E if EBIOS C if not EBIOS

...ystem ID : First : Last : Relative : Number of: > Flag :Cyl Head Sec:Cyl Head Sec: Sector : Sectors : > 80h 00h : 0 0 1 : 646 63 32 : 0: 1325056: > 00h EFh ?? :1023 254 63 :1023 254 63 : 8524: 608: The last sector 1325055 and its C/H/S (646, 63, 32) address tell that the partition table was made under the assumption H/C= 64 and S/H= 32. That's what hpa prescribed to me for smaller sized isohybrids. The EFI partition bears the CHS value which says that it is not valid. See: https://en.wikipedia.org/wiki/Master...

...block_seq block_seq.c to get a locally compiled binary. When Martin posted his MBR binary, the test stick shall be composed by: dd if=martins_mbr.bin bs=1 count=432 of=/dev/sdc dd if=debian-8.7.1-i386-xfce-CD-1.iso bs=1 count=80 seek=432 of=/dev/sdc ./block_seq | dd bs=512 skip=1 count=1325055 seek=1 of=/dev/sdc You will have to copy the screen output by hand or by photo camera. The hopefully lengish hex output of the block content can be truncated to 4 bytes, if all groups of 4 bytes are the same. If you see a change in the 4 byte pattern in the reported text, then all different groups...

...Last : Relative : Number of: > > Flag :Cyl Head Sec:Cyl Head Sec: Sector : Sectors : > > 80h 00h : 0 0 1 : 646 63 32 : 0: 1325056: > > 00h EFh ?? :1023 254 63 :1023 254 63 : 8524: 608: > > The last sector 1325055 and its C/H/S (646, 63, 32) address tell that the > partition table was made under the assumption H/C= 64 and S/H= 32. > That's what hpa prescribed to me for smaller sized isohybrids. > But that's my point. In theory, the geometry assumed in the MBR should match the one assumed...

................| * 00000800 > When Martin posted his MBR binary, the test stick shall be composed by: > > dd if=martins_mbr.bin bs=1 count=432 of=/dev/sdc > > dd if=debian-8.7.1-i386-xfce-CD-1.iso bs=1 count=80 seek=432 of=/dev/sdc > > ./block_seq | dd bs=512 skip=1 count=1325055 seek=1 of=/dev/sdc > > You will have to copy the screen output by hand or by photo camera. > The hopefully lengish hex output of the block content can be truncated > to 4 bytes, if all groups of 4 bytes are the same. If you see a change > in the 4 byte pattern in the reported text, t...

...he util > > fdisk doesn't support GPT. > > That's actually a bug in fdisk. The GPT is invalid because it is not > announced by a "Protective MBR". > > > Device Boot Start End Blocks Id System > > /dev/sdc1 * 0 1325055 662528 0 Empty > > "Empty" is not a realistic statement but just a human readable representation > of partition tye 0x0. It is unusual but needed to avoid that UEFI sees > partition 2 as nested partition inside partition 1. > > > # parted /dev/sdc u s p &gt...

...) detected on '/dev/sdc'! The util > fdisk doesn't support GPT. That's actually a bug in fdisk. The GPT is invalid because it is not announced by a "Protective MBR". > Device Boot Start End Blocks Id System > /dev/sdc1 * 0 1325055 662528 0 Empty "Empty" is not a realistic statement but just a human readable representation of partition tye 0x0. It is unusual but needed to avoid that UEFI sees partition 2 as nested partition inside partition 1. > # parted /dev/sdc u s p > Warning: /dev/sdc contains G...

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

Thomas Schmitt wrote: > My main point of interest is which block is really loaded as first one > of isolinux.bin. [Program snipped.] > (It could be shorter if i did not insist in big endian words.) Why insisting? Anyway appended is a dumper version. I could put up a binery version if needed. Let me know if so. -- MartinS /*

...cylinders, total 7821312 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x59f54072 Device Boot Start End Blocks Id System /dev/sdc1 * 0 1325055 662528 0 Empty /dev/sdc2 8524 9131 304 ef EFI (FAT-12/16/32) 2017-03-18 13:02:08 root at cd2533 ~ # parted /dev/sdc u s p Warning: /dev/sdc contains GPT signatures, indicating that it has a GPT table. However, it does not have a valid fake msdos partition tab...

syslinux at zytor.com: I have two older computers with Intel D865GBFLK motherboards (~2003) and Pentium 4 HT CPU's. They both have the latest available BIOS installed. I would like to put Debian on them. I have downloaded: http://cdimage.debian.org/debian-cd/current/i386/iso-cd/debian-8.7.1-i386-xfce-CD-1.iso When I put debian-8.7.1-i386-xfce-CD-1.iso on a CD-R, it boots correctly.