@PeterT Thank you for putting time and effort in this experiment, Peter.
Quote:
Originally Posted by PeterT
** One weirdness I saw... the Keyboard displayed with my patched file displayed an N where the 5 should be.
|
How can one explain this? May first and only idea was that kpg.exe for some reason erroneously tried to execute the replacement of the last byte of the string ("5" to "N") at another address, and by chance in this case there was actually a "5". A comparison of the original file and the patched file however shows, that this is not the case. (But of course, I cannot say whether my patched file would also produce the 5 to N change of the keyboard.) So how can we explain this?
Not that it would really matter, but I was for a short while confused by your identification of FW 3.0.0 with 3.0.1, and started looking at the 3.0.0 file.