Hi,
TightCoderEx wrote:
On Lenovo ThinkCenter, it did not make any difference. DL came back as floppy. I've enclosed an image that can be used without altering existing contents of BPB
I'm not too sure what happened to this disk image; but the "bootable marker" (0xAA55) isn't where it should be (at the end of the sector):
Code:
000001b0 90 90 90 90 90 90 90 90 90 ea 00 00 8a 00 55 aa |..............U.|
000001c0 8c c8 8e d8 8e c0 b8 03 00 cd 10 6a 02 68 1e 02 |...........j.h..|
000001d0 68 60 02 e8 ee 00 6a 04 68 0a 05 50 e8 e5 00 89 |h`....j.h..P....|
000001e0 c6 bb 0f 00 b8 00 02 ba 09 05 cd 10 b8 cd 09 b9 |................|
000001f0 1b 00 cd 10 bf b3 02 ba 0a 08 8d 5e fe ad 83 f8 |...........^....|
The first 2 entries of the partition table would decode as:
Code:
Partition 1:
Status = 0x55 = INVALID
Starting CHS: head = 0xAA, sector = 0x0C, cylinder = 0x2C8
Partition type = 0x8E
Ending CHS: head = 0xC0, sector = 0x38, cylinder = 0x203 = INVALID (end before start)
Starting LBA = 0xCD0003B8
Number of sectors = 0x10CD0003 = 0x68026A10
Partition 2:
Status = 0x1E = INVALID
Starting CHS: head = 0x02, sector = 0x68, cylinder = 0x160
Partition type = 0x02
Ending CHS: head = 0xE8, sector = 0x2E, cylinder = 0x300
Starting LBA = 0x0A68046A
Number of sectors = 0xE5E85005 = INVALID (overlaps with LBA+size of first partition)
I didn't decode the other 2 entries, but they don't look like sane partition table entries either.
The BPB is harder to decode (as there's multiple versions of it and half the fields are for FAT only and not used by anything else), but it begins with "Bytes per sector = 0xC000".
Basically; the "bootable marker" isn't present, the partition table doesn't look valid, and the BPB doesn't look valid. Under those conditions; a good BIOS shouldn't attempt to boot it at all, and everything else won't know if it should treat it as floppy (because there's no partition table) or as hard disk (because there's no BPB).
Cheers,
Brendan