I found one oddity of the SetFilePointer API function:

The function uses two DWORDs for describing the offset to move to. The docu
states, that the high-DWORD pointer can be set to NULL if unused. This is only
true, if using offsets < 2 GByte. If using larger values, f.e. 3.5 GByte, the function
fails, even under Win2K. Here you need to set the high pointer to a valid DWORD,
and set this DWORD to zero. Now Windows assumes the lower DWORD as unsigned
and the function works.

(seems to be a little compatibility to _llseek in Win3.11 :) )

* did you know the famous animal odd-celot? *
Posted on 2002-09-02 03:47:24 by beaster