So let’s turn our attention to the imports. If we try run the application now, we’ll get an error message due to a missing API in kernel32. Most of you probably already know that you need to adjust these fields as follows:įortunately, it’s enough to adjust the fields in the executable we want to start (python.exe), there’s no need to adjust the DLLs as well. This happens because of some fields in the Optional Header of the Portable Executable. If we try to start any new application on XP, we’ll get an error message informing us that it is not a valid Win32 application. Our target application will be the embedded version of Python 3.7 for x86. There’s no real purpose behind this article, beyond the fact that I wanted to know what could prevent a new application to run on XP. I didn’t find any prior research on the topic, but I also didn’t search much. Namely, running applications compiled with new versions of Visual Studio on Windows XP. To restart my career as a technical writer, I chose a light topic.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |