Shouldn't the v141_xp output a valid xp binary and get rid of those things, especially 'cause they are not included inside VSFilter itself but are probably a dependency? I took a look at Wine and it seems that they implemented the call, so I tried to take their implementation and use it as a wrapper to basically direct the call to it instead of to the kernel, but unfortunately it didn't work.

It simply has lpAttributeList which is the attribute list created by the InitializeProcThreadAttributeList function. LPPROC_THREAD_ATTRIBUTE_LIST lpAttributeList,ĭeleteProcThreadAttributeList is a void and thus it does not return a value.

It has lpAttributeList (which is the attribute list and it can be NULL to determine the buffer size required to support the specified number of attributes), dwAttributeCount (which is the count of attributes to be added to the list), dwFlags (which is a reserved parameter and it must be zero) and lpSize. It returns a zero value if it fails or a non-zero value if it succeeds. InitializeProcThreadAttributeList is a bool. Unfortunately, these two functions have been introduced in Windows Vista. I noticed that two kernel calls are missing in Windows XP: InitializeProcThreadAttributeList and DeleteProcThreadAttributeList. I apologize if it sounded like plagiarism, but trust me, no harm was intended at all.īy the way, Vangelis, since you are the same person of 'VistaLover', I wanna ask you something now that I have the chance ^^ĭuring the last few days I've been trying to compile the latest VSFilter for XP and it does compile with v141_xp toolset (and specifying /Zc:threadSafeInit-), but it doesn't work and ends up with an Invalid Access Memory Location (998) on run-time. If I remember correctly, you disabled some assembly optimisations and I didn't like that, however I tried to compile it with Intel Parallel Studio but it didn't work, so I ended up using Visual Studio (disabling the same things you pointed out because I read your post and you saved me a lot of time, really), but enabling assembly optimisations available to my CPU at the time. ffmpeg updated here: generally help people on Doom9 and I remember when they were talking about ffms2000 and I found your mailing post, but, just like Avisynth plugins, I generally re-compile them myself with the assembly optimisations available for my CPU using Visual Studio.

Ffmpeg download for windows xp