AIW MMC 7.6 large file capture error

[fortension]

I seem to be having an unusual error. I'm using a AIW Radeon and W2k (NTFS). I just upgraded (after uninstall) to the latest video driver, video capture driver, and MMC 7.6. When capturing large files, and by large I mean over 4gb significantly enough, I get an error when I save the file. It says: "(RManager) An Unknown error occured while accessing an unnamed file." The file is saved, but it is unscannable and tends to crash all viewers. I didn't have this problem before with earlier versions and I don't have the problem with capturing large AVI files in VDub.

Any ideas?

[Stan DeHaven]

Well,

I had a 'sort of similar' problem with a NTFS drive where the data would not accept a file name, but the file was there. I reformatted the drive (which Win2k did not like btw) because it was new and nearly empty. However, I believe that running error correction (chkdsk) and defragmenting the drive should be all that's needed. Be prepared for the defragement to take a while. Also, I was running Norton Utilities, which keeps a record of files (especially big ones which are noticeable).


Good Luck!

Stan

[Stan DeHaven]

Well,

I had a 'sort of similar' problem with a NTFS drive where the data would not accept a file name, but the file was there. I reformatted the drive (which Win2k did not like btw) because it was new and nearly empty. However, I believe that running error correction (chkdsk) and defragmenting the drive should be all that's needed. Be prepared for the defragement to take a while. Also, I was running Norton Utilities, which keeps a record of files (especially big ones which are noticeable).


Good Luck!

Stan

[Nelson37]

Under XP pro, I get this error every time but the files are always usable. Some progs have problems with over 4GB files, are you sure your viewers will handle them?

[fortension]

OK, I tried out another file, and it does seem to be player dependent. I couldn't find an actual player that crashed this time, but it seemed to before. My drive is defragged often, so I doubt that was a problem. I still have problems with flask/xmpeg opening the file, but that does seem to be a 4gb problem.

Thanks for the help.