FS#5013 - Fwpatcher fix spurious patching attempts
Opened by Jonas Häggqvist (rasher) - Monday, 03 April 2006, 16:13 GMT
Last edited by Jonas Häggqvist (rasher) - Thursday, 18 May 2006, 22:28 GMT
This patch fixes the problem with fwpatcher that meant it'd attempt to patch all the time. The problem was that the commandline driven interface used WM_USER as signal to start patching. This signal is reserved and will be generated for a lot of different commands. The solution is to use something in the range 0xC000-0xFFFF which is available for applications as signal instead as per http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wceshellui5/html/wce50lrfwmuser.asp
Patch severity set to High because without it, keyboard navigation is completely impossible Priority immediate because I don't think 3.0 should be allowed to ship with an fwpatcher that is not accessible (that is of course if fwpatcher is to be used for 3.0).
Tuesday, 20 June 2006, 11:01 GMT
Reason for closing: Accepted
Additional comments about closing: Alright, all\'s fine then. I was just a little curious why the fwpatcher had not been updated to include the fix and thought you might have forgot.