Sorry to contribute to the whine facto but...
I need to export QT same as source from my timeline to disk. Yesterday I did this with no problem exporting an 11 gig QT and then a 13 gig QT f rom my Powerbook. Today I get an error saying the file cannot be created because it would exceed the two gigabyte file size limit. Further I'm told to "export a shorter duration or change my export settings".
I thought the 2 gig file size limit was a thing of the past. Why was this no problem yesterday (or in the recent past for that matter) but today it is. I'm trying to export a QT movie - I've tried several times, rebooted and tried again. Any insights??

There is a file size limit with certain disk format structures, like FAT-32, I believe, and possibly a few others.  More knowledgeable people need to step in here and correct me if I'm wrong.

...another teachable moment. I discovered that I hadn't emptied the trash and as a result, my drive had less room on it than I assumed it had. The 2 gig file limit was Avid's response to the fact that I had insufficient space left on my drive to complete the QT export.. I suppose a guy who forgets to empty the trash can't complain that the software doesn't express itself more clearly.

Sounds like you've fixed it but I can confirm that you can exceed 2GB.

I am having this same problem.  Trying to export a quicktime movie in length of about 2 hours long.  I've done it many times before, except for today, 2 hours into the export process I got the same 2 Gig error with direction to change "export settings or export a shorter file.  I did just empty the trash 2 days ago. The hardware states that there are 455 GB available.  So any other suggestions to why it's not working? Are there any other settings I should be changing?

Did this get resolved. I have had a file size limit error while exporting a Quick Ref. 1 1/2 hr of dv quality doesn't seem like it should be so large.

Help!

I'm having the same issue. Trying to export uncompressed QTs from the timeline, done it a 'million' times before without issue. Now, suddenly I'm getting the same error. The drive is brand new with 750Gb available, NTFS. Just upgraded to MC v3, so assumed this was the problem but other are having the same issue with earlier builds.

Anybody ever figure this one out?

TIA,
Chris

Anybody have any thoughts on this yet? Sorry to be a nudge, just hoping to find a solution.

Chris