Quote:
Originally Posted by jackie_w
I'm not sure CSS Id (e.g /* found: 116 (zlib) pos: 45e7e8 */) is any help because the id number (116 in my example) changes with every firmware, even if the CSS content itself hasn't changed.
|
I can have a FindZlibBaseAddress instruction which can take either: a checksum of the CSS, the CSS Id, or a unique string anywhere in the CSS.
Also, should I make an option to dump the CSS?
Quote:
Originally Posted by jackie_w
Can you also consider creating a physical output log .txt file. When users have problems, it might be helpful if it's easy for them to attach their error log when they ask for help. Or are you planning to make the new system so easy no-one ever makes silly mistakes  |
I'm going to do the in the new patcher. Remember, the drop-in replacement is only for testing without having to rewrite all the patches and for me to try implementing a parser for the old format. And yes, I'll try to make this as impossible as possible to make it possible to make mistakes.