2. The Heading titled "Weaknesses - 4 GB Limit and No NFO Acceptance" is misleading. The 4GB limit is inherent to FAT-32. If the writer had used Windows 2000 (or indeed Windows NT) with NTFS there wouldn't be this problems as NTFS can handle file sizes ranging into Terabytes.
3. The title "Weaknesses - 4 GB Limit and No NFO Acceptance " should also be IFO not NFO. This was removed to prevent FlaskMPEG coming into trouble with the DMCA. However plugins can be used that add this functionality back to FlaskMPEG (along with much more besides).
4. It might have been an idea to mention that you add additional iDCT algorithms to FlaskMPEG with third party plugins. Many of these are more optimized than the ones included in the official distribution.
just one point DivX ;-) is not now OpenDivX, DivX ;-) is still DivX and openDivX is an entirely new and at this time highly inferior codec and this codec was breifly mentioned in the article.
I think a lot more throught should be going into the Flask articles, it's blatantly obvious that the writer hasn't done his homework on the subject.
April 29, 2001 6:37:28 PM
my mistake. there are so many of these things going around, it's confusing
Can't find your answer ? Ask !
May 1, 2001 7:07:20 AM
Just thought I would expand on this issue a tad bit. The reason that FAT32 can only address up to 4GB is because it uses 32-bit pointers in its implementation. This would seem logical since we only have 32-bit general purpose registers on most of our desktop machines...BUT...there are file systems out there that work around this limitation. One such is NTFS, or if you are interesting in seeing how it is done you could grab the source code for the linux kernel (version 2.2.18 or greater only) and look at the code for the Extended File System 2 and see how they do it...both of those File Systems support 2 or 4 terabytes I believe. Have fun