On 22 Apr 1999, Neil Bothwick wrote:
> Anyone that uses the cost logger needs an accurate time server.
> Otherwise the clock will be changed during the logging period, making
> all calculations invalid. Try setting your clock forward a day while
> online and see what Genesis tells you the call is going to cost :)
Ahhhh. So THAT'S my problem with the old cost logger. Or is it? If the
time server changes the internal clock time to, say, two minutes earlier
than it was set to before the time server query, would this mess the cost
logging up badly? i.e. could this be why most of the calls logged show as
0.05 (the minimum call cost), regardless of duration? Not that I actually
need the cost logger, but I'm a bit of a perfectionist..
Rob. ---- Granite City Roadsters, Aberdeen, Scotland.
Robert Inglis
=============
[EMAIL PROTECTED]
[EMAIL PROTECTED]
WWW Page : http://www.geocities.com/MotorCity/Track/8980/
The Heartbeat of America : Today's Chevrolet
_______
____/ /____
/ /
/ /
/____ ____/
/______/
Pontiac : Driving *EXCITEMENT*
