labview-zmq doesn't support windows xp.

LabVIEW bindings for the ZeroMQ project

Brought to you by: mjasperse

labview-zmq doesn't support windows xp.

Forum: General Discussion

Creator: crocket

Created: 2013-02-05

Updated: 2013-02-22

crocket - 2013-02-05

InitializeCriticalSectionEx is not found in kernel32.dll on windows xp.
InitializeCriticalSection exists on windows XP.
InitializeCriticalSectionEx exists in kernel32.dll since Windows Vista.

DLLs in labview-zmq refer to InitializeCriticalSectionEx, so I can't use
them on windows xp 32bit.

Can you fix the builds?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Martijn Jasperse - 2013-02-05

Thanks for your query.
Unfortunately this appears to be a well-documented problem with the official release build of zeromq itself (see e.g. https://github.com/bvarga/delphizmq/issues/3 and https://zeromq.jira.com/browse/LIBZMQ-480) making the underlying libzmq incompatible with WinXP despite what the website says.
This is a shame. I don't have access to any XP machines for testing which hinders debugging. If I can get a virtual-machine running I'll give it a try. If you have MSVC you could try and recompile libzmq yourself, or add your voice to the zmq bug tracker on jira to get the official build fixed.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Martijn Jasperse - 2013-02-05

Rebuilding ZMQ on XP wasn't as hard as I expected. I can't test it with LV myself right now, but try overwriting the DLL in C:\Program Files\National Instruments\LabVIEW 20XX\vi.lib\addons\zeromq with the attached file and tell me if you still get the same error.

libzmq-v100-mt-3_2_2.dll

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

crocket - 2013-02-06

It turned out that if I create an indicator from data output of zmq_recv.vi, it creates a string indicator with hexadecimal display style.

After setting the display style to the default one, I started seeing proper output.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

crocket - 2013-02-06

It works with libzmq-v100-mt-3_2_2.dll that you gave me.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Martijn Jasperse - 2013-02-06

I've rebuilt the package with custom-built DLLs. Can you check that the latest release of labview-zmq (v1.3.1.58) works on XP?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

crocket - 2013-02-19

Sorry for a late reply.

I tried installing 1.3.1.58 and 1.3.1.60, but VIPM refused to install because PostInstall.vi couldn't find "C:\Documents and Settings\Administrator\Local Settings\Temp\rename_lib.vi".

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

crocket - 2013-02-19

I also tried installing 1.3.1.60 on my coworker's computer which has windows xp 32bit.
1.3.1.60 was successfully installed on his computer.

I don't know why it fails to be installed on my computer.

On my computer, 1.2 is installed well, and 1.3 can't be installed due to the error I described above.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Martijn Jasperse - 2013-02-19

How odd. What version of VIPM are you using? Are you and your coworker using the same version of VIPM+LabVIEW? I have implemented several workarounds for problems with the packaging system and it's possible you've found an incompatibility.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

crocket - 2013-02-20

The VIPM version is "2012.0.1 build 1818" on my and his computers.

The LabVIEW version is 12.0 32bit on both computers.

The only difference is that I installed 1.12 and overwrote a DLL file manually before and he didn't.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Martijn Jasperse - 2013-02-20

The install process is annoyingly bug-ridden and VIPM has some odd behaviour. I just uploaded v1.3.1.62 of the package, which should resolve this particular error.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

crocket - 2013-02-21

1.3.1.62 could be installed well on my PC.

Thanks.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Martijn Jasperse - 2013-02-22

In that case I shall mark this topic as resolved. Cheers.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.