Error Writing Intermediate File
 

Suggestions please?

Thanks

Has there been a change in users on this machine? If so, check file permissions.

[quote=jinydu;229089]Suggestions please?[/quote]Disk is full?

User's disk quota is all in use?

Some technical background (assuming old naming conventions):

There should be two save files for your exponent, [B]p[/B]O983639 and [B]q[/B]O983639. A third file, [B]r[/B]O983639 will be created when progress needs to be saved. Then either the p- or q-file will be deleted and the r-file renamed accordingly.

Now the error says the r-file could not be written. This may mean what cheesehead and Uncwilly said, or filesystem corruption, or bad disk blocks, or simply that a file of that name already exists, and is write protected. Make sure that this is not the case. Also make sure the p- and q-files are not write protected, either (if they exist). I'm not sure whether there's a separate error message if the renaming fails.

If you don't mind about your 0.09% progress, you could even simply remove whichever of the 3 files exist, and restart the exponent from scratch.

[quote=ckdo;229137]Some technical background (assuming old naming conventions):

There should be two save files for your exponent, [B]p[/B]O983639 and [B]q[/B]O983639. A third file, [B]r[/B]O983639 will be created when progress needs to be saved. Then either the p- or q-file will be deleted and the r-file renamed accordingly.[/quote]IIRC (* Checks own prime95 directory -- yeah *), the p-file is always the newer of the two (p,q). So first the r-file is written, then the q-file is deleted, then the p-file is renamed the q-file, then the r-file is renamed the p-file.

Same problem, I just reboot
 

My older XP machine running Prime95 eventually throws this type of error after a few weeks of continuous running. I think it's related to a memory leak somewhere (not necessarily Prime95), but gave up troubleshooting it.

A reboot fixes everything for the next couple of weeks.

Deleting all save files (and a few other files to clear up disk space) and starting again fixed the problem, at least for now. Thanks

P.S. I lost far more than 0.09%. The test had been a little over 50% done; but this was lost due to a computer restart.