RayeR CZ, 01.12.2020, 00:11 |
VXD/LE file modification - unknown bytes in header (Developers) |
I'm trying to port some patch from one VXD to another VXD (a different driver version). I started with comparing patched and original file. At the beginning there are 3 different bytes at offset 144-146h - what is its meaning? --- |
|
tkchia 01.12.2020, 15:12 @ RayeR |
VXD/LE file modification - unknown bytes in header |
Hello RayeR, --- |
|
RayeR CZ, 01.12.2020, 18:24 @ tkchia |
VXD/LE file modification - unknown bytes in header |
> No idea, but perhaps the bytes starting at offset 0x144 are part of some --- |
|
Laaca Czech republic, 02.12.2020, 13:08 @ RayeR |
VXD/LE file modification - unknown bytes in header |
Some info is here: --- |
|
RayeR CZ, 27.12.2020, 21:54 (edited by RayeR, 28.12.2020, 01:11) @ Laaca |
VXD/LE file modification - unknown DWord in header-codesize? |
I didn't much oriented in that document but I got an idea, that the DWord at offset 144-147h must be some image size or code segment size because the patched file contains 56 new bytes of code in a cavity at the end of file and the difference of this magic DWord between original and patched version is aslo 56 so without this change Win98 crashed probably because accessing code beyond the limit. So I fixed the magic DWord by adding 56 and let's see :) --- |
|
RayeR CZ, 30.12.2020, 05:14 @ RayeR |
VXD/LE file modification - unknown DWord in header-codesize? |
I got a message that patched driver now works at least with 256MB card so it's on a good way, the DWord in header really matters... --- |