NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi Dave, I'm having trouble duplicating the error you are seeing. In particular, I can't seem to make ncdump from netCDF4 produce the message "ncopen failed" on any file, real or imaginary, and it works OK on 64-bit-offset files. Just to be sure, can you please send me output from the following, using the netCDF4 ncdump ls -l e4oper.fc.ml.19970116-19970120.nc ncdump -k e4oper.fc.ml.19970116-19970120.nc ncdump -V The last command will say "-V" is an illegal option, but will then print out the version number, which is what I want to see. Ans just to be sure I understand how the file was created, did you use the netCDF-4.0-beta1 library to create the 7.7Gbyte file, or did you use netCDF-3.6.2 and the 64BIT_OFFSET creation mode? Thanks! --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: WCM-111191 Department: Support Priority: Normal Status: Closed