Hi Elena,
thanks for the reply. Here is the error I am getting:
HDF5-DIAG: Error detected in HDF5 (1.8.5-patch1) thread 0:
#000: ..\..\..\src\H5Dio.c line 174 in H5Dread(): can't read data
major: Dataset
minor: Read failed
#001: ..\..\..\src\H5Dio.c line 404 in H5D_read(): can't read data
major: Dataset
minor: Read failed
#002: ..\..\..\src\H5Dcontig.c line 520 in H5D_contig_read(): contiguous
read
failed
major: Dataset
minor: Read failed
#003: ..\..\..\src\H5Dscatgath.c line 516 in H5D_scatgath_read(): file
gather
failed
major: Low-level I/O
minor: Read failed
#004: ..\..\..\src\H5Dscatgath.c line 252 in H5D_gather_file(): read error
major: Dataspace
minor: Read failed
#005: ..\..\..\src\H5Defl.c line 451 in H5D_efl_readvv(): block write
failed
major: Low-level I/O
minor: Write failed
#006: ..\..\..\src\H5Defl.c line 280 in H5D_efl_read(): external file
address
overflowed
major: External file list
minor: Address overflowed
A bit more information - I am trying to read part of a 1D dataset which
consists of a compound data type. The raw data is held in an external binary
file. I can use the HDF5 library (C++ bindings) to read the data from the
external file okay, except if I try to access data after about the 2GB
point.
The error message above "external file address overflowed" looks
suspiciously like a large file access problem?
I have also had a quick look at the HDF5 source code. It seems to make use
of 'fseeko' if it is available otherwise it uses 'fseek' to position the
file pointer. I suspect this could be why it doesn't work on 32-bit windows.
I believe Windows uses _fseeki64 rather than fseeko.
Regards
Paul
--
View this message in context:
http://hdf-forum.184993.n3.nabble.com/Large-File-Support-on-Windows-tp1589826p1595574.html
Sent from the hdf-forum mailing list archive at Nabble.com.
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
