An installation of MS Visual Studio was not bound to the Windows SDK version it shipped with and even newer SDKs were sometime capable to support older plattforms that were not their main target via configuration.
The setup currently uses the SDK that is delivered with the Visual Studio version.
While unlikely to have a direct effect on the games core code, a clean replication would need to be sure to use the Windows SDK the original was build with, since the CRT is compiled into the exe.
Determining this could be very hard and the only method I could come up with would be checking the Windows methods with reccmp.
The fitting SDK with the right configuration should produce the same code.
Additionally, finding older SDKs might be hard and even a bit riskier than searching up MSVC, since as downloadable that could have been a more valuable target for tampering.
The task is therefore optional and should only become important should clear issues related to this arise.
An installation of MS Visual Studio was not bound to the Windows SDK version it shipped with and even newer SDKs were sometime capable to support older plattforms that were not their main target via configuration.
The setup currently uses the SDK that is delivered with the Visual Studio version.
While unlikely to have a direct effect on the games core code, a clean replication would need to be sure to use the Windows SDK the original was build with, since the CRT is compiled into the exe.
Determining this could be very hard and the only method I could come up with would be checking the Windows methods with reccmp.
The fitting SDK with the right configuration should produce the same code.
Additionally, finding older SDKs might be hard and even a bit riskier than searching up MSVC, since as downloadable that could have been a more valuable target for tampering.
The task is therefore optional and should only become important should clear issues related to this arise.