In LabVIEW 8.0, the ZLib.dll calls don't compile.

[StephN]

In LabVIEW 8.0, the ZLib.dll calls to Inflate/Deflate (downloaded from www.ni.com/support) can't be compiled because there is no *.lsb file for each code interface node. Does anyone have *.lsb files for these, or know how to convert them to library call nodes?

[StephN]

I found out that following instructions pays off. I also contacted NI by email, and was told to copy the ZLib.dll file into my windows\system32 directory. That worked !  It now compiles and runs in LabView 8.0 without problems. 

Thanks, NI engineering staff.

[Mister_Rose]

I can't open the Zlib functions in Labview 2010. It complains that the VIs are too old and exits.

Has anyone got an updated build of the Zlib functions?

Thanks,

[Dennis_Knutson]

What are you refering to? Use the OpenG zip functions or the ones that come with LabVIEW.

[Mister_Rose]

Unfortunately I cannot download the OpenG files because it seems that the remote server is not responding.

This could be a proxy issue with the VI Package Manager. I really wish people wouldn't hide free and open source things behind proprietary gatekeepers.

[Jim_Kring]

---

@mister Rose wrote:

Unfortunately I cannot download the OpenG files because it seems that the remote server is not responding.

This could be a proxy issue with the VI Package Manager. I really wish people wouldn't hide free and open source things behind proprietary gatekeepers.

---

Hey Brian,

Here's a link to where you can download all the OpenG packages directly: http://sourceforge.net/projects/opengtoolkit/files/

Personally (although, I'm very biased), I like to think of VIPM as a facilitator, not a gatekeeper.  The only thing that is hidden is complexity and manual work. What sort of improvements to the experience did you have in mind?

Cheers,

-Jim

[Mister_Rose]

Jim, Thanks for the reply.

I was a little frustrated at the steps needed to download one little module. After poking around for a bit I now understand the role that the package manager plays. It is a nice little tool.

However, I think you need to beef up the network connections area. I have two proxy networking setups that do not work with your tool. I wasn't able to do anything with it until I went home and plugged it into my home network, which has no proxy.

Situation 1 is my work proxy, which blocks a bunch of websites that the admins deem "subversive" or for "hacking". What they call hacking I call software engineering, which is my job. This is not really your problem.

In order to accomplish my job, I have another proxy (Setup 2) that runs locally on my computer and forms an SSH tunnel with a computer outside our firewall. This allows me to get to the blocked sites. I use PuTTY to do this, and you can read about how they set up a PuTTY SSH tunnel here if you like.

A simpler way to support this might be to take the proxy settings from Internet Explorer and use those by default. I can get my IE to work with both proxies, so if you used those settings, your software would have much more success for unusual environments such as mine.

As it stands now, I cannot do updates at work, I have to go home and do them.

The OpenG page says that to get the OpenG VIs you need to go to your installation FAQ, and neither page mentions the fact that the OpenG VIs can be downloaded from Sourceforge. I think OpenG should make mention of that and indicate your tool as a way to manage everything. But you may not control the OpenG page, so you might want to mention this on your page. As it stands now, the OpenG website makes it sound like the only way to get the VIs is to download your software (which brought up the gatekeeper comment).

I also tried to setup an account on your website so I could post to your forums, but I never got the confirmation email (brian at brianrose dot net). Can you check on this?

Thank you,

[Jim_Kring]

Hey Brian,

Ya, I can see how the network stuff is frustrating (when it's not working).  FWIW, it's pretty hard to find/build a rugged cross-platform solution that deals with proxy servers (in various types and configurations).  That said, we've been pushing NI to improve its native support for HTTP and that will hopefully pay off.

Regarding direct download location, we do put a links on the package pages, such as this one: http://wiki.openg.org/Oglib_lvzip-2.5.1 (see the "direct download" link)

However, it's worth noting that the direct download approach is actually very confusing to new users and gets them derailed.  That's why we've worked really hard to streamline the process within VIPM.

Moving forward, we're working closely with NI to further streamline things, so expect things to continue to improve over time.

> I also tried to setup an account on your website so I could post to your forums, but I never got the confirmation email (brian at brianrose dot net). Can you check on this?

I emailed you back about this.  Can you check your spam box?  I suspect you'll find my reply as well as the confirmation email from when you signed up in our forums 🙂

Thanks,

-Jim