Hi Helen,

> True only if the database partition is FAT32 or NTFS4. (If OS was
> upgraded originally from NT 4, existing partitions are not "upgraded" to
> NTFS 5)

That is a quite interesting statement Helen, here is what FB 1.0 release
note says:

[FROM FB 1.0 RELEASE NOTES]

Large Database File Support
(Sean Leyne, David Trudgett)
The logical database can comprise a primary file and numerous secondary
files (the standing record for a single FB/IB database is 980GB!). However,
this enhancement concerns the size of a single physical database file. The
maximum file size limit involves three separate factors:
* the implementation (coding) of the FB/IB engine I/O functions <=== HERE
* operating system support for 64-bit file operations
* filesystem limits on file size

Engine support for 64-bit file I/O

All Firebird/IB versions prior to FB v1.0 (including IB v6.0) used both
32-bit API/OS calls and 32-bit (integer) file pointer structures. The
engine's capability was thus designed to handle files with a maximum file
size of 4Gb. In the Unix code the file pointer structures were defined as
signed
integers, thus limiting Unix and Linux implementations to file sizes of 2Gb.

[END]


FB 1.0 introduced 64bit I/O. To me your statement is not consistent with
what is written to the FB 1.0 Relase Notes. More on how this FB
implementation was done for Windows/Linux can be find at this release notes.

Also, I've had problems on the past using IB6 and db files over 2Gb on a
Linux (with Ext3, thus supporting files larger than 2GB) and moving to FB
1.0 with 64bit I/O fixed!


Regards,
Anderson Farias