Problem saving the current calculation
 

Hello guys, I'm running prime95 for a couple of years now. Some weeks ago I firstly recognized that my prime95 ver. 28.4 after booting my machine is always starting worker #1 at 1.02% and worker #2 at 8.08%. I have never had a similar prob before, and I cannot remember I'd done any changes at my machine's configuration. Any idea, what causes this problem? Thank you for helping! Best wishes, PG

You did not put your Prime95 under "Program Files", did you?

If so, Windows is shadowing the data safe files, as data files must not be under "Program Files." Prime95, by default, puts data files in the same folder with the executable.

Another reason could be that your IT department configured your PC with something like "Deep Freeze," so it goes back to frozen image on every boot.

Hello again and thank you very much@TObject for your reply!

No, my prime95 directory is stored under C:\Program Files (x86).

I tried to change the file attributes and the user's rights, and what shall I say - the problem is solved:
Any user account is allowed now to read and write the config- and what-to-do-files. Hope this will be working permanently. :-))
(However, I told that I did not change configuration since years; so I still do not know the reason for that.)

Best wishes,
PG

[QUOTE=pericologiallo;395100]Hello again and thank you very much@TObject for your reply!

No, my prime95 directory is stored under C:\Program Files (x86).

I tried to change the file attributes and the user's rights, and what shall I say - the problem is solved:
Any user account is allowed now to read and write the config- and what-to-do-files. Hope this will be working permanently. :-))
(However, I told that I did not change configuration since years; so I still do not know the reason for that.)

Best wishes,
PG[/QUOTE]

For the 64-bit versions of Windows, "Program Files (x86)" is treated the same as "Program Files": by default, programs are not allowed to write to the "Program Files*" tree unles explicitly given permission by an administrator (you, in this case). Just make sure you only give write access to the Prime95 folder, not the entire ffolder tree, since global access to the "Program Files*" tree is used as a transmission route for various virii!

[QUOTE=schickel;395103] Just make sure you only give write access to the Prime95 folder, not the entire ffolder tree, since global access to the "Program Files*" tree is used as a transmission route for various virii![/QUOTE]

Thank you too.

Of course I just edited the prime95 folder/files. But in fact I think now that this solution has something of a work around, hasn't it? Would it be better to install the program in an alternative folder?

And again: I have absolutely no idea how this could have happened without any changes made at the PC configuration. Maybe it's the ghost in the machine? ;-)

[QUOTE=pericologiallo;395107]But in fact I think now that this solution has something of a work around, hasn't it? Would it be better to [B]install the program in an alternative folder[/B]?[/QUOTE]

Yes, that's the usual way to work around this issue. I'd still recommend it, to avoid problems if the permissions change in the future, for example.

*** Solved ***
 

So I will move the program folder and hope to avoid problems in the future. Thank you all!

Best wishes,
PG