[RESOLVED] Issues with version 2047

[jpsdr]

I've update to 2047 from 2046 and have troubles...
I've noticed 2 issues for now :
- I've 2 OS installed on my PC : WIndows XP SP3 and Windows XP64 SP2. According what i need,
i switch from one to another. (Even if i intend to update to Win7 (and Win7x64) as soon as i find the time i don't have for now).
The ID code is now different on my both OS. So, is it still possible to have several licenses
number on the license file ? Otherwise, i may have to handle switching between 2 license files.
- When i try to start the x64 version on Windows XP 64, i've an error saying it's not a Win32 valid application.

[admin]

I will restore the ability to add multiple licenses and notify here when I have slip-streamed it.

Things work fine for me with 64-bit version on 64-bit Win8. I will double check the upload and go from there.

[admin]

I have slip-streamed the multiple licenses fix.

Please re-download and try the 64-bit version. It works fine for me on 64-bit Win8 as I said.

[jpsdr]

Same issue with x64 version. But the x86 version work fine under bot XP and XP64. I don't have (yet) Win7...
What compiler version do you use ?
It's seems specific to the .exe, not the DLL, because an avisynth script (using dgi file) opened with VDubx64 works fine.
Unless... dll hasn't changed, and not recompiled...
Apparently, with VS2012 or VS2013 by default you don't create XP valid application.
Now, if you intend to drop XP support, like more and more people, because you don't want to waste time, i'll not be mad, no hard feeling.

[admin]

Ah it's only on XP!

I use Visual Studio Express 2012 on Win8 64 for the 64-bit stuff and Visual Studio 2005 on WinXP 32 for the 32-bit stuff. I'll have to look into this further. I don't want to drop WinXP but I don't have a WinXP 64 system either. And I can't use VS 2005 on Win8.
I also noted that Win32 builds done on my Win8 64-bit also give the error running on WinXP. That's why I still do the Win32 builds on my 32-bit WinXP system with VS2005.

The 64-bit DGDecodeNV DLL was recompiled on Win8 64.

I suppose you can use the 32-bit DGIndexNV with the 64-bit DGDecodeNV as a workaround if there is no solution to be found.

[admin]

See here. It should be possible. Investigating further...

http://stackoverflow.com/questions/1313 ... tudio-2012

http://blogs.msdn.com/b/vcblog/archive/ ... lable.aspx

[admin]

Re-download 2047 and update 64-bit DGIndexNV.exe. Please report the result.

It sure will be great to be able to build both the 32-bit and 64-bit binaries on my 64-bit Win8. I can test the 32-bit part if you verify the 64-bit build on XP.

[Aleron Ives]

You should also still be able to target XP if you decide to use VS 2013, as long as you use .NET 4.0 or earlier. XP isn't supported on .NET 4.5 or higher.

[admin]

Not possible because the CUDA toolkit is not compatible with VS2013. Nvidia has been dragging their feet on it. The latest status is that a candidate toolkit supporting VS2013 "may be released this summer".

[admin]

Any test results on WinXP 64, jpsdr? Thank you.

[jpsdr]

Just give me time to back home...
I've seen this at work this morning, now back and tested Ok, thanks.
And while i'm still having XP, i can test 64 builds on XP.

[admin]

Thanks a lot! You know me, I'm sometimes impatient, and some argue, a bit grumpy. And since I retired, I forget that some people actually have to work. I'm just getting set for my afternoon nap.

But where would my stuff be without guys like you? So thanks for bringing the issues to light and being willing to test stuff. We move onward and upward together!

[BarryW]

Just to confirm that the license has changed for me as well with 2047.
Error message just says "Invalid License!".

Only tested on WinXP (32bit) so far. I'll test Vista (32bit) and Win7 (64bit) tonight.
I've gone back to using the last version for now 2046.

[admin]

Barry, the license is supposed to change! You need to make a new license using the online generator. It is intentional, as I have changed the licensing algorithm to be more user friendly.

Or did I misunderstand you?

[BarryW]

Ok