search for: mbr_

...%ecx and compensate the additional bytes by e.g. shortening the error message. (All together must fit into 432 bytes.) It seems to me that the %si value is expected to be inherited from the run of the previous MBR code, which decided about the partition to be chainloaded. http://wiki.osdev.org/MBR_%28x86%29 "Typical MBR bootstrap code will do the following: [...] * [...] load the Volume Boot Record (VBR, the "bootsector" of the bootloader) from the beginning of the selected partition * set DS:SI pointing to the selected partition table entry * jump to 0x7c00 (with CS set...

On MacOS X 10.4.11 PPC /usr/local/bin/rsync --version rsync version 3.0.0pre9 protocol version 30.PR16 Copyright (C) 1996-2007 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 32-bit inums, 32-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv

Thomas Schmitt wrote: > Since we know that the isolinux.bin binary is well ok on other partitions, > i'd say that the MBR code does not load the right blocks from disk when > it wants to get isolinux.bin. Yes, these are my thoughts as well. I think the jump from GRUB to the isohybrid code on the logical partition is working fine, but when the isohybrid code is trying to jump to