On Tue, May 5, 2009 at 12:59 AM, Patrick Georgi patrick@georgi-clan.de wrote:
I have some code for a "next" field that builds a chain without relying on "offset" and "len" (as the current chain walker do). That helps with a scenario like having two option roms right after another at the beginning of the ROM. The current walker would be confused by that. (it always looks for the next file header after the current file's data)
I am missing the point. Are they two cbfs files or ... if they are two cbfs files, then there is no problem. The case that the option ROMs are not part of cbfs? Or there are two option ROMs in one CBFS file?
it's too early in the morning for me :-)
ron