Prime95 on Windows 7?

[ixfd64]

As we know, running Prime95 on Vista can be somewhat tricky:

1. Prime95 cannot be placed in the "Program Files" directory because Vista does not allow users to write to that folder.
2. Enabling the "Start at Bootup" option will cause Prime95 to act up; instead, a shortcut to Prime95 must be placed in the "Startup" folder.

Does anyone know if there are any similar issues associated with running Prime95 on Windows 7? I've never touched Windows 7 before, but chances are that I'll inevitably be using it in the future.

[TimSorbet]

I don't have experience with Windows Vista or 7, but I think that both of those problems are the same between Vista and 7.

[pegaso56]

Hi, short answer, mostly yes. Make a folder in my documents, or public documents. And why don't you try Linux?
Best regards, Carlos

[joblack]

Originally Posted by ixfd64

As we know, running Prime95 on Vista can be somewhat tricky:

1. Prime95 cannot be placed in the "Program Files" directory because VIsta does not allow users to write to that folder.
2. Enabling the "Start at Bootup" option will cause Prime95 to act up; instead, a shortcut to Prime95 must be placed in the "Startup" folder.

Does anyone know if there are any similar issues associated with running Prime95 on Windows 7? I've never touched Windows 7 before, but chances are that I'll inevitably be using it in the future.

You can put prime95 in the Program Files folder but you have to give yourself (your user not the administrator) writing rights in the folder. Additionally I've found out that you have a performance lost if you use Prime95 in that folders (there seem to be additional win 7 tests which needs more time in writing).

I just moved the complete Prime95 folder in c:\Prime95 and I never got any problems (autostart works like a charm) with Win7 anymore ...

[cheesehead]

Originally Posted by ixfd64

1. Prime95 cannot be placed in the "Program Files" directory because VIsta does not allow users to write to that folder.

Originally Posted by joblack

You can put prime95 in the Program Files folder but you have to give yourself (your user not the administrator) writing rights in the folder. Additionally I've found out that you have a performance lost if you use Prime95 in that folders (there seem to be additional win 7 tests which needs more time in writing).

Has either of you tried what's described in undoc.txt, to use a different directory for the writeable files?

In prime.txt you can force the program to use different filenames for 6 files.
You can also change the working directory (identical to the -W command line
argument).
    prime.ini=your_filename
    local.ini=your_filename
    worktodo.ini=your_filename
    prime.log=your_filename
    prime.spl=your_filename
    results.txt=your_filename
    WorkingDir=your_directory_name

[joblack]

Originally Posted by cheesehead

Has either of you tried what's described in undoc.txt, to use a different directory for the writeable files?

In prime.txt you can force the program to use different filenames for 6 files.
You can also change the working directory (identical to the -W command line
argument).
    prime.ini=your_filename
    local.ini=your_filename
    worktodo.ini=your_filename
    prime.log=your_filename
    prime.spl=your_filename
    results.txt=your_filename
    WorkingDir=your_directory_name

It might be easier to move it out of the program files directory.

[cheesehead]

Originally Posted by joblack

It might be easier to move it out of the program files directory.

Does that mean you have not tried the undoc.txt method?

[joblack]

Originally Posted by cheesehead

Does that mean you have not tried the undoc.txt method?

No I moved the complete folder out of the win7 protection area ...

[cheesehead]

Okay.

- - -

I remain interested in reports from folks who have tried the undoc.txt method. Please let me know whether you found that a satisfactory alternative.

[joblack]

Originally Posted by cheesehead

Okay.

- - -

I remain interested in reports from folks who have tried the undoc.txt method. Please let me know whether you found that a satisfactory alternative.

But let me say that under the windows programming specification it's a bad decision to write in the program files folder. It might be a good idea to give the user the chance to save the data in the profile (for instance in the installation process).

That would have the advantage that several user in a multiuser system could use the same executable (and the information could be saved on the server profile) ...

[cheesehead]

Originally Posted by joblack

But let me say that under the windows programming specification

which I'm not familiar-with except by inference from comments

it's a bad decision to write in the program files folder.

What is the approved method of communicating to an executable either (a) a set of changeable parameters in some file within the program files folder, or (b) a pointer to a file containing such parameters in another folder?