Is there any simple way to locate these dialogs in the hex without resorting to the debugger. I suspect this is from some variation in the fix level or some such making the call to the windows api come out to a different binary value. I did some scoping out of stuff, trying to match strings and such, but never found the right hex strings. Is there a list of what else is broken in Protel 99SE under Windows 7 Thanks again, Tony.įound this threat, breathed a sigh of relief, and got out the hex editor. So I followed your same approach and found where to patch for the schematic library dialog as well (I dont understand why the code is duplicated, as the dialogs are pretty much identical, but anyway.) Patch offset 0x25f78 to 0x25f81 inclusive with 0x90 (original bytes were: 50 8b 45 ec 50 e8 7e c1 fd ff ) in Client99SE.exe With both these patches applied, you can add libraries to both the pcb and schematic under windows 7. I will do some more testing and - if necessary - tinkering if there are still more problems. So: get yourself a hex editor (I use HxD, its free) and edit the Client99SE.exe file.Ĭhange all bytes from offset 2690E to 26917 ( a total of 10 bytes that need to be changed) to 90. Protel 99Se Libraries Code Is Duplicated.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |