http://git.kernel.org/?p=boot/syslinux/ ... e0c15ead03chain.c32 sethidden option fix
Hidden sectors value was applied at the wrong offset.
I compiled chain.c32 with this patch:
http://ubcd.stopspazzing.com/downloads/ ... /chain.c32
Moderators: Icecube, StopSpazzing
http://git.kernel.org/?p=boot/syslinux/ ... e0c15ead03chain.c32 sethidden option fix
Hidden sectors value was applied at the wrong offset.
Code: Select all
map /ubcd/custom/AVGRescue.iso (hd32)
map --hook
chainloader (hd32)
Yeah, that's the error I get. I'll go look at that thread and have a go at including one of those drivers. Cheers!Icecube wrote: If you want to boot Windows based ISO's directly (grub4dos or MEMDISK mapping), you need to include a driver (WinVBlock or Firadisk), else you probably will get the "Stop 0x0000007B" error:
http://www.boot-land.net/forums/index.php?showforum=94
No.naebeth wrote:Ah, okay. So when I tell Grub4Dos something like this:It invokes chain.c32, which contains info on how to find, determine and call the boot sector of the particular image?Code: Select all
map /ubcd/custom/AVGRescue.iso (hd32) map --hook chainloader (hd32)