To answer my own question, Pharlap uses FAT32, and is thus limited to 4G for file sizes.
The approach I'm using, then, is to monitor the file size (using the regular File I/O "Get File Size" function, and if the size hits 2G, I close the file and open a new one, then continue logging. Is there a better approach?