GPIB no communication after update to Win7

[BobWang]

Hi,

   I have an old application which developed in VB.net 2005, I use cwinstr.ocx for GPIB communication. This works fine in XP for many years! While after I change the PC to Win7 64 bit, it cames error and shows the class not register. But I already get it successfully register both in path C:\windows\system32 and C:\windows\syswow64. And the GPIB driver already update to latest version:2.8.1. The problem still there! Who can help me with how to find a way to fix it!

Regards,

Bob

[BobWang]

Hi,

   I have an old application which developed in VB.net 2005, I use cwinstr.ocx for GPIB communication. This works fine in XP for many years! While after I change the PC to Win7 64 bit, it cames error and shows the class not register. But I already get it successfully register both in path C:\windows\system32 and C:\windows\syswow64. And the GPIB driver already update to latest version:2.8.1. The problem still there! Who can help me with how to find a way to fix it!

Regards,

Bob

[Bonnie]

what's your 488.2 driver version？Can you post your error description?

[BobWang]

Bonnie,

Thanks for taking care of this! My driver has updated to the latest version 2.8.1.

The problem comes out when I initialize my GPIB device, the message shows "the class not register" when the code running to the function under the CWinstr.ocx dll file. The application has running no issue in XP for many years!

Is that due to the dll file CWinstr.ocx not support 64 bit environment? Should I need change to use the NI4882.dll instead?

Regards,

Bob

[Bonnie]

I think the reason may be the .ocx is not reside in a right system32 directory. Maybe you can download the object CWINSTR.ocx from internet and install it.

[smercurio_fc]

Why would you tell someone to go and download an OCX from the internet somewhere, which has the potential of downloading something with a virus, especially since that OCX is already part of NI software?!?

Geez...

As to the question.... You iniitially said this was a VB.NET app. Are you still trying to run this in VB.NEt 2005 on Windows 7, 64-bit? Did you make sure that SP1 for Visual Studio 2005 is installed, as well as the update for Vista (also applies to Windows 7)?

Aside: was there a reason for using the ActiveX controls as opposed to the .NET assemblies? I would think it would have been easier to use the assemblies.