On 27 Oct 99, at 21:13, Albert Garrido wrote:
> I'm currently trying to configure the Time command, as listed in the
> docs, to
> get the prime95 client to function as follows.
>
> User ID=XYZABC
> Time=1-5/18:00-0:00,1-5/0:00-08:00,6-7/0:00-24:00
> (reset of Prime.ini)
>
> Anyhow, it doesn't seem to work, and I tried a few other syntax forms,
> but
> what would usually happen is that either the app runs at 6:00PM and then
> goes
> to sleep at 6:01. I inserted the line Priority=1 after the Time line,
> and it
> doesn't do much. I couldn't find an explanation of the time variables
> on the
> FAQ, I'm hoping someone's been down this road before.
This is slightly tricky & not very well documented - though there is
explanatory text in the "undoc.txt" file which comes with the
official v19 distribution (and also with late betas of v19).
The trick is:
(a) the "Time=" line(s) should appear at the end of the file;
(b) any "Priority=" or "DiskWriteTime=" directives must appear
_after_ the "Time=" line to which they apply.
This allows you to use different priority & disk write time at
different times of day, even if the program is running 24 x 7.
The downside is that you _cannot_ have "Priority=" or
"DiskWriteTime=" before the first "Time=" line; if you do, then the
time directives will not work as expected.
Also, the end point in your first time interval should be 24:00 not
0:00. The end time must always be greater than the start time.
I would suggest you resequence your Prime.INI file as follows:
[ all other lines]
Time=1-5/00:00-08:00
Time=1-5/18:00-24:00
Time=6-7/00:00-24:00
If you have any Priority= or DiskWriteTime= directives, delete them
from the "top section" & make copies after each of the Time=
directives.
This should run the program at all times except 08:00-18:00
(according to your system clock) Monday to Friday.
I'm doing something a bit similar, and it does work; the end of my
Prime.INI file looks like this:
Time=1-7/00:00-08:05
Priority=1
DiskWriteTime=30
Time=1-7/20:00-24:00
Priority=1
DiskWriteTime=30
[Runs the program from 20:00 to 08:05 7 days a week]
I know that Priority=1 & DiskWriteTime=30 are defaults & could
therefore be omitted. I was messing about!
> Anyhow, it's an Athlon that's running at 900Mhz, besides the novelty
> value of
> that. How fast would something like this get through an average LL
> test?
{Green with envy}
I don't know whether Kryotech does anything with the bus/memory
speed, if it's "just" a CPU speedup (i.e. a larger multiplier) then
the effect will be significantly less than 1.5 times as fast as a
"room temperature" Athlon @ 600 MHz. But then the Athlon should be
significantly faster than a PIII at the same bus & CPU speed - even
without re-tuning to take advantage of the Athlon architecture.
My guess is, if the Krytotech module is driving the Athlon at 9x100
MHz, the performance is probably going to be almost exactly twice
that of a PIII-450 - which is about 10% better than the "standard"
benchmark PII-400 - so multiply the benchmark figures by 0.45. Should
do better than that if the bus speed is higher than 100 MHz.
Quite apart from anything else, it would be interesting to see how
well Prime95 _does_ run on an Athlon. Perhaps you would care to run a
QA test suite (takes about 12 hours on a PIII-450). You might also be
interested in parallel running some tests with the QA team; the extra
interest here is that this is probably as good a way as any of making
a name for yourself by finding a flaw in the Athlon FPU !!!
Regards
Brian Beesley
_________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
