Farming with prime95.exe ...

greeners · 2002-09-02, 22:42

Lost an almost completed 33m yesterday ... such is life in the corporate environment ... bit painful at times. And no, no backup.

So, I have a set of scripts that copies the client and work from a source machine to various targets and then executes prime95.exe locally. Does not require a user to be logged in, just requires the machine to be on and me and admin on the box. Works pretty well, but requires a bit of upkeep.

With this latest loss, I was thinking that I might be better off trying to run the client centrally ... all located on the same system and run it over the network. I would like to have this work, even if no one is logged in on the target system. I have been trying variations of the following line in a .BAT file that I push out to the target system and run:

\\gimpserver\prime\workstation1\prime95.exe

Which will run, but never seems to update the data files, even though I have set a 10 minute update.

Has anyone tried anything along these lines? I think that I need a bump to get going ... or maybe just some electric shock treatment.

ET_ · 2002-09-03, 07:59

You obviously tested the following:

[code:1]COMMAND LINE ARGUMENTS
----------------------
-An This is used to run two or more copies of prime95
from the same directory. Using this command line
argument causes prime95 to use a different set of
filenames for the INI files, the results file, the log
file, and the spool file.
Just use a different value of n for each copy of
prime95.exe you start.

-Wdirectory This tells prime95 to find all its files in a different
directory than the executable.
[/code:1]

This way you teach Prime to look for the update files on the correct directly of your central distribution server.

Luigi

greeners · 2002-09-04, 02:18

Thanks Luigi. Managed to get it working ... turned out to be domain vs. workstation permissions.

Currently I am running each client in their own sub directory. I may try to run them all in one directory as a trial, but that makes me a bit nervous for some reason. We shall see how it goes ... ;)

2002-09-02, 22:42	#1
greeners Sep 2002 3 Posts	Farming with prime95.exe ... Lost an almost completed 33m yesterday ... such is life in the corporate environment ... bit painful at times. And no, no backup. So, I have a set of scripts that copies the client and work from a source machine to various targets and then executes prime95.exe locally. Does not require a user to be logged in, just requires the machine to be on and me and admin on the box. Works pretty well, but requires a bit of upkeep. With this latest loss, I was thinking that I might be better off trying to run the client centrally ... all located on the same system and run it over the network. I would like to have this work, even if no one is logged in on the target system. I have been trying variations of the following line in a .BAT file that I push out to the target system and run: \\gimpserver\prime\workstation1\prime95.exe Which will run, but never seems to update the data files, even though I have set a 10 minute update. Has anyone tried anything along these lines? I think that I need a bump to get going ... or maybe just some electric shock treatment.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Flaming Raspberries	a1call	Hardware	20	2018-04-29 11:25

2002-09-03, 07:59	#2
ET_ Banned "Luigi" Aug 2002 Team Italia 5×7×139 Posts	You obviously tested the following: [code:1]COMMAND LINE ARGUMENTS ---------------------- -An This is used to run two or more copies of prime95 from the same directory. Using this command line argument causes prime95 to use a different set of filenames for the INI files, the results file, the log file, and the spool file. Just use a different value of n for each copy of prime95.exe you start. -Wdirectory This tells prime95 to find all its files in a different directory than the executable. [/code:1] This way you teach Prime to look for the update files on the correct directly of your central distribution server. Luigi

2002-09-04, 02:18	#3
greeners Sep 2002 3 Posts	Thanks Luigi. Managed to get it working ... turned out to be domain vs. workstation permissions. Currently I am running each client in their own sub directory. I may try to run them all in one directory as a trial, but that makes me a bit nervous for some reason. We shall see how it goes ... ;)