Gan Shun

yes it should be safe. If it becomes a pain, we can work that into some kind of warning that doesn't terminate the parsing

I'll look into making it a per call setting next week!

can I clarify, is this outside of all FVs? I think we do preserve this, so it must be a bug if it's being deleted. If it's between FV's this...

I think so and we should warn in that case

to be specific, UTK will not show duplicates in the case of intel roms, since there is an IFD and we only parse the regions specified by the first IFD...

I don't want to tell people to go learn forth just to use the command line interface of our program..

Ok I'm convinced. It would make certain things easier, like diffing two bioses.

I did the copying in the past because once you start modifying the files underneath a firmwarewarevolume, during the reconstruction I was seeing some corruption because the firmwarevolume buffer is...

I would +1 on not trying to calculate offsets by subtracting pointers. Lets discuss what you're trying to achieve and maybe we can find another way to do it

> Also an important argument is: the behavior of pkg/-stuff should be predictable. But it appears that if you change a byte in a "File" then in the total firmware...