F
Francesco Bucciantini
Guest
Hi,
I have a Windows Embedded Standard 2009 machine that has been showing ads on a screen for years.
Ads are just videos encoded by various companies.
Everything is automatised and it works flawlessly.
Some companies are now requiring subtitles to be displayed and they are providing soft-subs videos (not hardsubbed), so I was going to integrate a render to the player that actually shows the ads on the screen. The render I trying to integrate is able to render subs in different color spaces and bit-depths. It's written in C++ and I compiled the project with v141_xp, it compiles fine and it works perfectly on Windows 10, but when I try to run it on Windows Embedded Standard 2009 I get "Invalid Access Memory Location (998)". It seems that even though I compiled it using v141_xp, it still tries to use two kernel calls that are missing in Windows Embedded Standard 2009: InitializeProcThreadAttributeList and DeleteProcThreadAttributeList.
Is this an expected behaviour? Isn't v141_xp supposed to take care of these kind of calls and compile a Windows Embedded Standard 2009 compatible binary?
This is the solution explorer: Github Download
Thank you in advance.
Continue reading...
I have a Windows Embedded Standard 2009 machine that has been showing ads on a screen for years.
Ads are just videos encoded by various companies.
Everything is automatised and it works flawlessly.
Some companies are now requiring subtitles to be displayed and they are providing soft-subs videos (not hardsubbed), so I was going to integrate a render to the player that actually shows the ads on the screen. The render I trying to integrate is able to render subs in different color spaces and bit-depths. It's written in C++ and I compiled the project with v141_xp, it compiles fine and it works perfectly on Windows 10, but when I try to run it on Windows Embedded Standard 2009 I get "Invalid Access Memory Location (998)". It seems that even though I compiled it using v141_xp, it still tries to use two kernel calls that are missing in Windows Embedded Standard 2009: InitializeProcThreadAttributeList and DeleteProcThreadAttributeList.
Is this an expected behaviour? Isn't v141_xp supposed to take care of these kind of calls and compile a Windows Embedded Standard 2009 compatible binary?
This is the solution explorer: Github Download
Thank you in advance.
Continue reading...