This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
>From: "Alan Scheinine" <address@hidden> >Organization: ? >Keywords: 200307291310.h6TDAtDX023577 netCDF download Alan, >Institution: CRS4 >Package Version: V3.5.1-beta11 >Operating System: Linux >Hardware Information: Intel Pentium >Inquiry: After logging-in, I tried to download > netCDF Source Code, V3.5.1-beta11 (netcdf-3.5.1-beta11.tar.Z) >The web browser shows that it is working >but nothing arrives. >I tried both netscape and Mozilla, >the same problem. My first inclination is to advise you to use FTP directly. >The problem may be our firewall but that >would be a very difficult problem to resolve. >The netscape browser shows that the download >link becomes an ftp server, This is correct. >but I am unable >to access the ftp server with ncftp (because, >I assume) I must get the software while >logged-in. I don't understand this comment unless you mean that you think you must be logged onto the web site to do the download. >At the present time our cluster of Linux >machines use a recent gcc and a recent PGI, >both of which result in an error when compiling >netcdf version 3.5.0 , so I need to be able to >obtain 3.5.1. How? From a Linux xterm window, try the FTP/ncftp: ftp ftp.unidata.ucar.edu <user> anonymous <pass> "Alan Scheinine" <address@hidden> cd pub/netcdf binary get netcdf-3.5.1-beta11.tar.Z quit The FTP/ncftp should work as long as your machine has both forward and reverse name lookup; we block others to cut down on DOS attacks. If DNS does not support forward and reverse name lookup for your machine, try doing the FTP/ncftp from a different machine. If the problem turns out to be your firewall, you should get your system administrator(s) involved. Tom Yoksas