TCP/IP Library and Windows 7

[DPat]

Hi together,

I have the following problem: I am trying to build up TCP/IP connections as client. On my notebook (WindowsXP) everything works like a charm. But when I install the application on a Windows 7 PC, no connection is possible.

ConnectToTCPServer fails with "WSAE_UNKNOWN".

Probably this has to do with the socket handling from Win 7. Currently I still have the Measurement Studio Ver. 6.0 on my notebook, because my applications always worked fine on WinXP PCs.

So my question is: Is this a known behavior? If so, is there a workaround or is the only solution a newer CVI Version?

Thanks for any help,

Dirk

[RobertH]

Hello Dirk,

could you describe the problem a little more detailed?

does this error occur on any try using TCP ?

actually it might be, that CVI 6 will not work with Windows 7.

do you have the possibillity to test a newer version of CVI?

kind regards,

robert h

[DPat]

Hello Robert,

thanks for your answer.

To give a some more details:

I can´t say if it is happening with trying to use any TCP from CVI. Because if the application is running on an WinXP PC (my notebook, even installed from the distribution kit) everything is fine. On a Windows 7 PC my application already fails on the ConnectToTCPServer call with the above mentioned error. With PuTTY I can establish TCP connections, a python script (though I am not sure if my python supports Win 7) shows the same problem.

Some more details about the task: I have to establish two TCP connections as client, one to my data acquisition hardware, second one to a TCP Server provided by automationX (some soft-sps solution). If I run my application on my notebook with WinXP everything works fine (even the automationX stuff I connect to is running on a Windows 7 PC). Now I install the application on a Windows 7 PC and both ConnectToTCPServer calls fail with the above mentioned error. So I have no chance to test other TCP calls from the library.

Actually this behavior makes me think that is a problem with the Winsock of Windows 7. Why otherwise it would run on my XP notebook and would fail on the ConnectToTCPServer on the Windows 7 PC?

Unfortunately, being in Asia atm, I only have the CVI 6 version with me. I will travel back to Germany next week. I have the upgrades up to CVI 9 there, but I never installed them. (Never change a running system 😉 ) On the other hand, probably it is time to do so. Never had to work with Win 7 before.

I just wanted to know if anyone else experienced some similar problems and if there is a workaround (maybe even in Win 7 to make the socket behavior / handling like it was on WinXP).

But I guess I have to finally install the upgrades.

Is CVI 9 compatible / tested with Windows 7?

Best regards,

Dirk

[Al_S]

Dirk:

Here's a link from NI showing their supported compatibility with Windows 7.  It shows LabWindows/CVI 2009 as the oldest supported version, so CVI 9.x is not supported under Windows 7.  That doesn't mean your app won't work under Windows 7, but NI doesn't support it.

http://zone.ni.com/devzone/cda/tut/p/id/10383

[Wolfgang]

Just a minor correction of Al's post:

Because CVI 9.1 is equivalent to CVI2009 (see here), CVI 9.1 is supported, and his statement should read:

 It shows LabWindows/CVI 2009 as the oldest supported version, so CVI 9.0 is not supported under Windows 7.

[DPat]

Thanks again for all your answers.

I found out that my software service contract is active, so actually I have CVI 2010 now on my notebook. Unfortunately no longer on job site, will return there beginning of may and post (and flag this thread as solved) if my application, compiled with CVI 2010, will work fine. (after I found out that the datasocket library is now an instrument driver (.fp), guess I will have to read and learn a lot about the changes, coming from CVI 6).

However, a short question (maybe kind of a hijack, but given that I opened the thread): If I build a 32-bit application with CVI 2010, is this still Windows 7 compatible?

Best Regards,

Dirk