We are currently experiencing read large binary files that individual file size exceeds 4.0GB. From the manual/electronic documentation, integer definitions involved in functions such as FILE_SIZE@ and FPOS@ are defined as KIND=3(see definition of SIZE, POSITION, NEW_POSITION etc). This causes incorrect values returned.

As Integer (KIND=4) have been introduced, does this integer data type apply to the above mentioned functions and how does it work? I have tried to use Integer*8 SIZE in calling FILE_SIZE@ and it worked in one of my test case. However, I need to get confirmation from Silverfrost on the definitions of integer types regarding to such kind of issues.

In addition, I am interested to get information on technical support and charges.