[Windows XP] Error dialog: ... GetNumaNodeProcessorMaskEx ... KERNEL32.dll.

[mm0359]

Hello,
With (brand new) Avidemux v2.6.13 (2016.08.18) on Windows Vista,
I get a double (non-blocking) error on (every) Avidemux startup.

Install file: avidemux_2.6.13_win32.exe
Error dialog: ... GetNumaNodeProcessorMaskEx ... KERNEL32.dll.
Microsoft says this function (indeed) needs Windows 7.

(Avidemux v2.6.12 did not have this issue.)

Can this be "improved/fixed" to properly support Windows Vista?
Thanks.

[mean]

If you remove libx265.dll* doest it work better ?

[mean]

(or libx264*)

[mm0359]

Testing/Confirming with "v2.6.13 + usp10.dll" on WinXP.

If you remove libx265.dll* doest it work better ?

Renaming "libx265.dll" replaces the 2 "GetNumaNodeProcessorMaskEx" dialogs with 2 "... libx265.dll was not found ..." dialogs.
Not really "better", but it shows/confirms "libx265.dll" is the "culprit"

(or libx264*)

Renaming "libx264-146.dll" simply adds 2 "... libx264-146.dll was not found ..." dialogs.
"Worse", not the "culprit"

Ftr, is it expected that (at least) these two dlls are "loaded"(!?) twice?

[mean]

Ok, so it is indeed x265
I'll see what i can do
(lmight be  loaded once for "all UI" and once for "Qt UI")

[mm0359]

("v2.6.13 + usp10.dll" on WinXP.)

Much alike, "avidemux_cli.exe" triggers 1 "GetNumaNodeProcessorMaskEx" dialog then reports:
{
[videoEncoder6]Symbol loading failed for ...\plugins\\videoEncoders\libADM_ve_x265_other.dll
...\plugins\\videoEncoders\libADM_ve_x265_other.dll:CannotLoad
}

[mean]

Try with that one, might work
http://fixounet.free.fr/avidemux/libx265_xp.zip

[mm0359]

Try with that one, might work
http://fixounet.free.fr/avidemux/libx265_xp.zip

("v2.6.13 + usp10.dll" on WinXP.)
Yes! It fixes "avidemux.exe"
and "avidemux_cli.exe" too:
{
[videoEncoder6]Name :x265 ApiVersion :6 Description :x265 based HEVC Encoder (c) 2014 Mean/Gruntster
[VideoEncoder6] Registered filter ...\plugins\\videoEncoders\libADM_ve_x265_other.dll as  x265 based HEVC Encoder (c) 2014 Mean/Gruntster
}

And it fixes the error on Windows Vista too

[mm0359]

And it fixes the error on Windows Vista too

(When) Will this "fix" be included by default?
Thanks.

[mean]

Never
XP is not supported

[mm0359]

XP is not supported

I know, and thanks again to have made this XP lib available!

Yet, Windows Vista is still supported, isn't it?

[Jan Gruuthuse]

XP  Mainstream   Support End Date: 4/14/2009
Vista Mainstream Support End Date: 4/10/2012
Why do you expect a free independent developer to support his program beyond Mainstream Support (on aged operating systems)?

[mm0359]

Why do you expect a free independent developer to support his program beyond Mainstream Support (on aged operating systems)?

Windows :
XP, Extended Support End Date: 4/8/2014
Vista, Extended Support End Date: 4/11/2017

Avidemux :
2015-05-16: 2.6.9 :
* Win32 and Win64 builds are now using winbuilds.org, Xp no longer supported.
and
win32 2.6.13 Final Install (32 bits), FossHub,
NOT XP COMPATIBLE

I am not requiring support.

XP is officially unsupported :
I'm simply asking whether there could be some simple workarounds,
like the Microsoft "usp10.dll" and Multicoreware "libx265.dll" ones.
If there are not, then too bad.

Vista is not officially unsupported :
hence my question!
If it is unsupported now (as XP is), then please state it explicitly (as XP is)...
Thanks.

[mean]

It basically boils down to the effort involved.
Supporting win64 for 7 and up is not difficult.
Win32 is a different matter, between the exception management (sjlj vs the other one), XP class vs Vista class, etc..
the # of combinaison is huge and the audience is smaller & smaller

So if i can make it work with a small amount of work, fine
Else i wont pursue it, it's not worth it

[mm0359]

So if i can make it work with a small amount of work, fine
Else i wont pursue it, it's not worth it

I agree. And thanks for trying that at least!
Then, you should probably document a "Vista (+/-) unsupported" (as XP is), fwiw.

I'm thinking about ReactOS too, which currently targets (XP and) Server 2003 compatibility. But that's "future"...