VirtualDub Frame Serving Not Working in XP Pro (NOT the MSVCR70.DLL issue)

[acanthis]

I'm certain that frame serving from VirtualDub did used to work fine on my Windows XP Pro system, but I can no longer get it to function.

This is not the issue that Avery discusses on his home page about not including the VB .Net runtimes (I have MSVCR70.DLL installed, and anyway reverting to the 1.4.9 frame server does not fix the problem).

As soon as I select File -> Start Frame Server, I get an error dialogue: "The procedure entry point ConvertToGlobalHandle could not be located in the dynamic link library KERNEL32.DLL"

On checking my copy of KERNEL32.DLL, I find that, sure enough, there is no such entry point. (And, yes, I only have one copy of the DLL, and it's correctly located in C:\Windows\System32)

This works fine on my video capture machine running Windows 2000, and I'm convinced that I have used frame serving on this box before.

Does anyone have any suggestions?

Thanks for any help you can give.

[Swede]

The only thing I can find about 'ConvertToGlobalHandle' is some issues with 16-bit programs not running in 32-bit Win.. (Knowlegebase at M$)
From this I can only believe that the problem must be something else than the Frame-serving?
What about the source? Can you watch the movie in vDub?
Other than this I'm lost. :(

[acanthis]

Originally posted by Swede
The only thing I can find about 'ConvertToGlobalHandle' is some issues with 16-bit programs not running in 32-bit Win.. (Knowlegebase at M$)
From this I can only believe that the problem must be something else than the Frame-serving?
What about the source? Can you watch the movie in vDub?
Other than this I'm lost. :(

There's no problem watching the files or doing any dubbing/encoding operations etc; everything works fine.

But I have just discovered one thing: The message only appears the very first time I try to start the frame server in a VirtualDub session. And it now seems that the frame serving is actually working, despite this message. I think the files I was serving to TMPGEnc before were rejected for other reasons, and I just assumed that the serving wasn't working properly because of the error message. I've just done a successful frame serve to create a short MPEG and that worked even with the 'ConvertToGlobalHandle' error.

Weird; but at least it seems as though my immediate problem is solved (though I'd still like to know what causes the damn error message)

Thanks for your help.

[ricnews]

I just learned about frameserving and am getting this exact error message, though I haven't found anything on the net specifically about it. The frameserving does seem to work after I ignore the error. But out of curiosity, has anyone else have this problem or figured out what it means?