Rob Inglis said,
> 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?
No, it would mess it up by two minutes :)
> i.e. could this be why most of the calls logged show as
> 0.05 (the minimum call cost), regardless of duration?
If you clock is slow, so it gets put forward during each call, a lot
of calls could fall within the minimum period.
> Not that I actually
> need the cost logger, but I'm a bit of a perfectionist..
You can check your bill on BT's site (if you're with BT), if you
really want to know...
Neil - who just got a bill for -�70 :)
--
Neil Bothwick - http://www.wirenet.co.uk icq://16361788
Connected via Wirenet,The UK's first Amiga-only internet access provider
--
As of next week, passwords will be entered in Morse code.
