Help! "Disk Error: The Drive Is Full"--But It's Not

[George Tyndall]

I'm exporting a PRE7 HD m2t Timeline as MPEG2 and getting the message that the Disk is full, however, the disk to which I am saving has 133GB of free space and the drive does not need defragmenting, according to the analysis of the Windows Disk Defragmenter.

Meanhwile, my Scratch Disk has 210GB of free space and it also does not need defragmemting, while my C Drive has 163GB of free space and it, too, does not require defragmenting.

I'm confused!

[Chuck Engels]

George, Try restarting your computer and going directly to Premiere Elements and export, do nothing else.
Do not pass go, do not collect $200, just export your timeline

[George Tyndall]

George, Try restarting your computer and going directly to Premiere Elements and export, do nothing else.
Do not pass go, do not collect $200, just export your timeline

Ok, I did that and only after it was up and running did I log on to this site.

Is that what you mean--do nothing else until after PRE7 is up and running? Or, do you mean that even after it is up and running I should do nothing else?

The program just finished the export despite my being on this web site and despite chatting on Yahoo with a web cam, so I guess you mean the former. Am I right?

[Steve Grisetti]

You might also want to run a program like Advanced System Care ( http://www.iobit.com/advancedwindowscareper.html ) EasyCleaner or CCleaner to clear off your temp and other old scratch disc files.

You accumulate hundreds of megs of these every month and, though invisible, they can gunk up your system and slow everything down.

[Bobby]

George, I have been lurking with not a lot to comment on yet.

I think you need to determine whether this is in fact a system general problem, or a PRE specific problem. Run CHKDSK (right click on the drive, select Properties, Tools tab, Error checking and let it run. Also try copying or moving files around to that drive to see if all runs OK. If not, then you do have system problems that we can address.

If not, you may be seeing a PRE unique problem. I have sometimes seen those kind of messages myself - they are often Red Herrings and really don't indicate what is going on - PRE is seeing something it doesn't like but isn't giving you a correct or informative message. I have seen this kind of message if the file you are writing already exists, for example - rather than tell you that it gives me some other bum error.

I think this determination would be your next step.