grub4dos
grub4dos copied to clipboard
Try (hd0): non-MS: skip
I'm using the latest version of Grub4Dos.
My users have reported that he has encountered this issue. This issue has occurred to me before, but not now. He tried using v0.4.5c and it worked fine.
It looks like it can not read the partition table?

Please upload MBR
Sorry grldr.mbr.txt
Not this one. Is the (HD0) MBR, LBA(0) sector .
I skipped the partition table. 0x1B8-0x1FF will not be overwritten.
Please upload the partition table. (0x1B8-0x1FF)
This problem does not occur frequently grldr.mbr.txt
Unable to communicate
Sorry mbr.bin.txt
Your improved partition table: 80 20 21 00 0C FE FF FF 00 08 00 00 34 0E BA 03 The image of 1# will never appear.
You try this: 80 20 00 00 0C FE FF FF 00 08 00 00 34 0E BA 03 The 1# image appears immediately .
conclusion: The partition table is wrong or illegal.
Thanks! Grub4Dos using CHS? But this information is returned by Windows. You can create a partition using DiskPart to test it. Grub4Dos is currently working well on this partition table. I do not understand why the same partition information, but the results are different. The partitions that I create begin at 2048 sectors.
No Just for example. Grub4dos check partition table.
80 20 21 00 0C FE FF FF 00 08 00 00 34 0E BA 03 and 80 20 00 00 0C FE FF FF 00 08 00 00 34 0E BA 03
Each time I recreate the partitions, though they are the same, Grub4Dos has not worked the same. My partition table is valid, on Windows and Linux and both Grub2 and Syslinux.
Cut the top 5MB of the U disk into files and send it up.
This is what you need. 5mb.bin.txt
The root directory does not have "grldr"?
I renamed it aiogrldr. This file is located in the root of the drive.
The information you provided is inaccurate. If the partition table is wrong, it is 'Try (hd0): non-MS: skip'. If the partition is correct, it is 'Try (hd0): NTFS5: No aiogrldr'.
The problem is that you change the file name. The grldr-0.4.6a.mbr version you used was too old.
Please use this to replace 0-0x1fff.: 5mb.bin.txt
It's version 0.4.5c. I also encountered this error in this version.