Rob Inglis said,
> No, you're not 'duplicating' effort here. Really the only thing you should
> do is set the address for your Time Server to the same address as your
> Gateway. That will hopefully prove to be quicker in setting your clock
> time (due to a shorter network distance between you and the time server),
> rather than the University/College server you are currently using. Compare
> the two to see which is more accurate if you can, but I'd guess that for
Clock accuracy is more important than network closeness. It's no use
using a nearby machine if it has an inaccurate clock. Machines
dedicated as time servers should be correctly synchronised. I could
set my A4000's clock from my A2000, it's less than 2ms away, but it's
not accurate.
> most people it wouldn't matter if the clock was a minute or two out.
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 :)
Neil
--
Neil Bothwick - http://www.wirenet.co.uk icq://16361788
Connected via Wirenet,The UK's first Amiga-only internet access provider
--
.. Veni, Vidi, Visa - I came, I saw, I charged it.
