but I can create a file >4GB with a normal GCC-program:
(on a=20
NTFS-harddisk)
The file is opened and data is written to it.
You can follow this=20
process with multitasking from another
DOS-commandline. You can peek into=
the=20
file, while data is
appended to it by a GCC-compiled program.
You can=20=
open=20
it with other C-programs
until less than 4GB are written. Then suddenly=20
you
can't open the file with GCC-compiled programs,
while DOS-commands=
=20
"dir","type","copy" still work.
This continues while the file still grows=
and=20
after it's finished.
Now, does the whole structure of the file change dramatically,
when=20=
byte=20
2^32 is written ? Hard to believe.
The data is still at the same place,=20
where it was when byte
2^32-1 was written. Seems to me that GCC just=20
checks
for the filesize and when it's too big then GCC
exits with an e=
rror=20
- although it could proceed
as normal, at least for the first 2^32=20
bytes
and probably with some small modifications for
the rest as=20
well.
I guess that it can be done by changing less than 100 bytes
in t=
he=20
gcc.exe.
--Guenter.