View Full Version : NeoHD - HDLink throws 'problem/needs to close' window at startup.


Robert Gadsdon
March 20th, 2010, 08:06 AM
I have just upgraded from NeoScene to NeoHD, and after the upgrade HDLink worked fine.
Now, after a system restart, HDLink throws a 'Cineform HDV Capture Application has encountered a problem and needs to close...' window each time it is executed.
The info given in the error report is:

AppName: hdlink.exe AppVer: 4.3.0.240 ModName: kernel32.dll
ModVer: 5.1.2600.2180 Offset: 0000a250

A few seconds after the "...encountered a problem..." window is displayed, HDLink starts up, and appears to work, as long as that window is not closed.

I have already tried completely deinstalling NeoHD, and clearing out related registry entries etc. and then rebooting/reinstalling, but the problem persists.

System is a CoreDuo with 4GB memory, running WinXP SP2.

Robert Gadsdon.
March 20, 2010

David Newman
March 20th, 2010, 10:04 AM
What is odd, I haven't heard of that one. Do try support for help. When Neo HD's HDLink startup is does look for capture devices, HDV, Blackmagic or AJA cards, so do you have anything that might be seen as a capture device, but not.

Robert Gadsdon
March 20th, 2010, 03:35 PM
Thanks. I have sent an email to support...

I have a Blackmagic card in the system, and this is shown correctly as a "Decklink Video Capture" in the HDLink 'Capture Source' field.
I have also attached my Canon HV30 camera via FireWire, and this also shows up correctly in the 'Capture Source' field.

I had been using the NeoScene version of HDLink on this same system without problems, for about 6 months..

David Newman
March 20th, 2010, 10:53 PM
Then I would look at your Blackmagic card's drivers, try getting an update. That is the only difference between NeoScene and NeoHD startup, NeoHD is initializing your Blackmagic card.

Robert Gadsdon
March 22nd, 2010, 01:15 PM
I finally found that a _cold_ boot - after shutting down and powering off the system for a couple of minutes - fixed the problem, so it probably was a hardware-related aberration.

Thanks,

Robert Gadsdon