Is there a version of LZO compression library for OpenVMS?

[Maxy2]

Is there a version of LZO compression library for OpenVMS?

LZO home page: http://www.oberhumer.com/opensource/lzo/

The OpenVMS ports of Freeware software (
http://nchrem.tnw.tudelft.nl/openvms/software2.html) lists this about LZO, but the link to the supposed patch (ftp://anonymous:%27%27%27%27@nchrem.tnw.tudelft.nl/openvms/lzo-2_03_vmspatch.tar) is broken:

LZO
Purpose : portable lossless data compression library.
click hereto get the source distribution and information.
patch for version 2.03 : click here for Patch. This patch includes compile support for OpenVMS

Last version tested: 2.03 (23 May 2008)
-using HP C V7.3-009 on OpenVMS Alpha V8.3

[Steven Schweda]

> [...] but the link [...] is broken:

Did you try it without the extra crap?

ftp://nchrem.tnw.tudelft.nl/openvms/lzo-2_03_vmspatch.tar

[Maxy2]

Yes, I tried the link directly, without the junk.

If you try ftp://nchrem.tnw.tudelft.nl/, you'll see that the machine is actually there. Navigating with IE to the directory doesn't work.

I tried command line FTP, and it worked. I was able to get the LZO-2_03_VMSPATCH.TAR file.

Thanks everyone.

[Steven Schweda]

> [...] but the link [...] is broken:

> Navigating with IE to the directory doesn't
> work.

So, MSIE is broken, not the link. MSIE is
notoriously incapable of dealing with a VMS
(TCPIP) FTP server. Not many modern Web
browsers can do it well, but MSIE is worse
than most.


Sometimes it's helpful to reveal what you
actually did, and what actually happened when
you did it, rather than giving a vague
description of what you did and your
interpretation of what it all means.

[Hoff · Accepted solution]

The web site is using old and largely deprecated syntax for the ftp URL, and it appears the client here is running a patched version of Microsoft Windows and Internet Explorer.

http://support.microsoft.com/kb/834489

There are options, if you're not inclined to use command-line FTP:

http://filezilla-project.org/

Please also notify the keeper of the web page at TU Delft.

[Steven Schweda]

You may also find one more change helpful
(unless you have a "malloc.h" lying around
where someone can find it):

ALP $ gdiff -u src/miniacc.h;2 src/miniacc.h
--- src/miniacc.h;2 2008-05-23 08:19:38 -0500
+++ src/miniacc.h 2009-11-11 21:41:32 -0600
@@ -1902,7 +1902,9 @@
#define HAVE_FCNTL_H 1
#define HAVE_FLOAT_H 1
#define HAVE_LIMITS_H 1
+#ifndef __VMS
#define HAVE_MALLOC_H 1
+#endif /* ndef __VMS */
#define HAVE_MEMORY_H 1
#define HAVE_SETJMP_H 1
#define HAVE_SIGNAL_H 1


(Cheap and nasty, but apparently effective.)

[Maxy2]

Here is what I specifically did to download (from Windows command prompt):

C:\temp>ftp nchrem.tnw.tudelft.nl
Connected to hrem157.nano.tudelft.nl.
220 hrem157.nano.tudelft.nl FTP Server (Version 5.6) Ready.
User (hrem157.nano.tudelft.nl:(none)): anonymous
331 Guest login OK, send ident as password.
Password:
230 Guest login OK, access restrictions apply.

ftp> get openvms/lzo-2_03_vmspatch.tar
200 PORT command successful.
150 Opening data connection for SIRBA$DKA0:[ANONYMOUS.OPENVMS]LZO-2_03_VMSPATCH.TAR;1 (148.106.4.6,55170) (250368 bytes)
226 Transfer complete.
ftp: 251346 bytes received in 1.06Seconds 236.45Kbytes/sec.

ftp>

[Hoff]

The Microsoft Windows ftp client is not particularly known for its compatibility with the OpenVMS ftp server. The FileZilla ftp client works better in this regard.

The Windows-integrated version of Hilgreave Hyperterm is in the same general class here; it too mostly works but doesn't have a stellar reputation of compatibility with OpenVMS. The current version of Hyperterm from Hilgreave is better, as is the PuTTY terminal emulator.

Folks using Windows with OpenVMS are often served better with the available and alternative (and often free) tools; the default Windows tools set offer a comparatively poor degree of compatibility here.

[Jansen_8]

My web-site at the tudelft is running on a OpenVMS server indeed. It always gives problems when people try to access it with IE. I have no idea how to solve that.

I included the anonymous.%27%27 stuff, because I noticed that some browsers did not check the anonumous account, but only tried the ftp as username.

Jouk