We created a 12Gig AVI file... it works fine - it's not corrupted. However, we are trying to convert it to mpg2 using Videowave so it could fit on a dvd. Do you know of a limitation on file size with xp. Error: Page fault in non page area. We increased the win page file from 2 GB to 20GB (it can be done) - this time it states another problem. We even moved the page file to a seperate physical drive. Watchdog.sys error. Thanks.

To me it doesn't sound like a filesize limit of the OS (because then you wouldn't have a file that large in the first place) but rather like a filesize limit of the program you are trying to use to open it. A 12GB file does not fit in 32bit address space, if that program is trying to open it as a memory mapped file it is doomed to fail on any 32bit system.

yeah... it's time for Athlon64.

Pardon my intrusion, but check a regular DVD & you'll notice that it has not one but many MPG segments... Most MPG encoders Free & Commercial will not go over the 32 bit limit... I know this, cause it took me 2 days of trying to make such a big file conversion myself, to finaly go look at how the Pros do it. And they split the file into segments, most converters will add a little info into each segment's header where each file joins. And that's the extent of my knowledge on this topic! Good luck! Marco

I noticed that too but didn't think anything of it. And it's only one hour. If we are not mistaken, it 2GB @ 32bit?

Sounds right. Like i said, most encoders have the capability to split your file. i can't remember offhand the name of the utility i used(2 years ago). It's a 3 part process(if i remember). First, the encoder will split your file into manageable segments(Video part), it splits the Audio into a seperate file. Then when it encodes to MPG, it will use the segments & sync the Audio to each segment. Now, maybe 2 years after my own perilous journey into MPG conversion, the process has been simplified. Or at the very least, they've made the steps tranparent to the user. An analogy to this would be converting .WAV files to .MP3. When it started, the process whas 2 parts. Now, it's one(Although, technically, it's still 2!) :-) Marco

Try it on Linux?

We don't have Linux... but I'd really hate to do it over again (stop and go, stop and go). Personally, I'd fire intel CEO for not going 64bits sooner and AMD CEO for being very stingy on MHz.

This has nothing to do with your CPU not having 64bits, this is just a software thing. Complain at the vendors of video software that don't handle such large files, if you need someone to blame. Your operating system, file system and CPU seem to be up to handling 64bit file pointers, otherwise that 12GB file wouldn't exist. Since it's an AVI file, look on the web for file splitters, there are a couple of them. Maybe one of them is able to cut it into smaller chunks. What program created that 12GB file in the first place anyway?

try this: http://www.doeasier.org/splitter/

I'm not complaining... just pointing out what areas they are lacking in. In most cases the shareholders own the company and can decide who stays and who goes. That's all. We had to do it at 3min each file (about 150MB)... slow but it works. The first movie created was 2GB+ AVI (20min). It was reduced to 1.4GB mpg. The next movie was 12GB- the one giving problems.

Maybe this is not relevant but I understand that if you are using Fat32 instead of NTFS then your file size is limited to 4Ghz for video processsing. Are you using NTFS?

OOPs I mean 4 GBytes.

If you check out video software, you'll find some that advertise that they can render "beyond the 2 Gig limit," or words to that effect. So I would agree that it's probably your software.

NTFS - which we believe is still a 32bit system. Yes, VideoWave5 is able to capture >12GB video files and it's able to convert it to mpeg. It does so in batches (seperate files)... we discovered unfinished 1.2GB file. However, the problem lies in the conversion process where it may falter somewhere along the line. Sometimes it may run for 30min or 2mins before it crashes. This was done with minimal processes running... no firewall, AV, etc. We tried several AVI file splitters but none could read the 12GB file. So we redid the scene to 7GB (33Mins). It crashed in the conversion process at 92% complete! Perhaps it was just too much for the software to handle. But windows didn't state it was a software problem... it said it might be a hardware or driver problem (blue screen of death).

LOTR uses Linux, 3000 servers of it... OK, you told me you do not have Linux (need I mention it is free?) and if you wish to finish this project in a short time I do inderstand that using it seems daunting ( and not such a great advice). However, consider that all 3D feature films since Titanic were rendered using Linux render farms, so this platform did prove itself for this kind of tasks. On the long run you should give it more attention...

Thanks - we just finished the project. By the way, Roxio just informed us today that their software can handle video files >12GB therefore the problem lies elsewhere.

We kept the 12GB file and tested on a 512MB system and everything worked fine. It converted to 2.6GB mpeg. I don't think the memory was bad because Poser used up as much as 1022MB of RAM (out of 1024) for firefly. However, with p4 render, 512MB is suffice and it's about 500% faster. We now feel the problem was some programs can't handle 1GB memory... as Poser did in the days of old.

I have XP and 1 Gig ram I just converted a 19 gig avi file to a mpeg-2 dvd using Sonics 'My DVD' it worked fine . So I can testify that that program works okay.

Yes, some programs will work.... Ulead media studio pro, Premiere to name a few. It's a shame the AVI has to be sooo large and converting takes time. But file/size ratio... mpeg2 is best.