iTimeSync: 49 days, 16 hours?

[Unregistered]

I'm sure there's something obvious that just isn't sinking into my mind, but I'm looking at the iTimeSync screen shown below, and I can't figure out why it's displaying "49 Dys 16 Hrs". I have AutoSync set to every 15 minutes. My date/time is not off by anywhere near 49 days (as you can see). For the moment, I'm at a loss, but I have a feeling that once I find out, I'm going to feel stupid!

[Siegfried]

No need to feel stupid; I'm equally confused. The only routine in iTimeSync that displays a contdow like that is the AutoSync/Check. Thus I've looked around there but there should be no what that it could display the time by itself without a "until auto..." so I'm confused. Please try pressing the "reset" button for the AutoSync and see what happens. I've had iTimeSync syncing all afternoon trying to replicate that without any luck. If it happens again (or if it won't go away) could you send me your data file? It'll help me track down what's going on here...

[Unregistered]

The strange thing is that it wasn't counting down, and it didn't say "until AutoSync". It just kept displaying "49 Dys 16 Hrs".

In any case, it doesn't seem to want to happen again. I remember at the time I was scanning servers and editing ServFile.txt with the GUI running. Maybe iTimeSync got confused because the list file changed, without a "refresh" being done...? (I can't see how that would affect what iTimeSync displays for the AutoSync countdown, though.)

This also makes me wonder if the service needs to be restarted whenever ServFile.txt is manually edited.

[Siegfried]

It just kept displaying "49 Dys 16 Hrs".

No change at all? Odd...

In any case, it doesn't seem to want to happen again. I remember at the time I was scanning servers and editing ServFile.txt with the GUI running. Maybe iTimeSync got confused because the list file changed, without a "refresh" being done...?

Scanning servers perhaps, but editing no. You have given me more to work with though!

This also makes me wonder if the service needs to be restarted whenever ServFile.txt is manually edited.

If you want the servers to be updated, yes.

[Siegfried]

We've released a new version that could prevent this. We are still unable to replicate the issue though.

[g3sna]

[Unregistered]

I've just updated as shown to 1.502. My registration runs back to 2003 and I have a dReg.dat file. This no longer works with the latest version. Any advice please?

Thanks,

Stuart

Yeah--start a new thread that actually refers to your own bloody problem, rather than reviving one that is years old and making me get a "new reply" notification email for nothing at all.

[g3sna]

Thank you for that great advice.