System clock too fast..??

[BD]

Hey, all.

I have a Soltek SL-75FRN2. Had it about 2 years. Unsure of fw rev; I
know I haven't updated it in quite some time.

My system clock is running stupidly fast, to the tune of about 10
minutes per day.

Is this likely caused by a low CMOS battery? Or could there be a
hardware fault somewhere??

I'm also looking for recommendations for an (ideally free) clock sync
utility. Something that will sync to an NTP server somewhere
automatically. I've tried a few tools thus far, most promising of which
seems to be AnalogX, but oddly, the automatic syncing doesn't seem to
be working. I can sync it manually...

I wonder if this utility has to be configured to run under a special
account or something...

Anyway.

Thanks for any and all...

BD

 

[Rod Speed]

I have a Soltek SL-75FRN2. Had it about 2 years. Unsure
of fw rev; I know I haven't updated it in quite some time.

My system clock is running stupidly fast,
to the tune of about 10 minutes per day.

Is this likely caused by a low CMOS battery?
Nope.

Or could there be a hardware fault somewhere??

Yep, that oscillator could well be running that fast.

I'm also looking for recommendations for an (ideally free) clock sync utility.

XP will do that without addons. You do need to set the update
frequency behind its back if you want to update it say every few hours.
http://www.dougknox.com/xp/scripts_desc/xp_time_sync.htm

 

[BD]

Or could there be a hardware fault somewhere??

Yep, that oscillator could well be running that fast.

Only thing is it's only been the past few weeks it's been acting up.
That's all I find weird.

XP will do that without addons.

I managed to get this AnalogX thing to run right, and it's acceptably
lean; I'll stick with that for now, but I will grap that script in case
this 3rd party app doesn't cut it.

Thanks!

 

[Paul]

Hey, all.

I have a Soltek SL-75FRN2. Had it about 2 years. Unsure of fw rev; I
know I haven't updated it in quite some time.

My system clock is running stupidly fast, to the tune of about 10
minutes per day.

Is this likely caused by a low CMOS battery? Or could there be a
hardware fault somewhere??

I'm also looking for recommendations for an (ideally free) clock sync
utility. Something that will sync to an NTP server somewhere
automatically. I've tried a few tools thus far, most promising of which
seems to be AnalogX, but oddly, the automatic syncing doesn't seem to
be working. I can sync it manually...

I wonder if this utility has to be configured to run under a special
account or something...

Anyway.

Thanks for any and all...

BD

On some Nforce2 chipset boards, the problem is so severe, that NTP
is not the right answer. There is a suggestion here, that disabling
APIC (advanced programmable interrupt controller) can solve
the problem. (When APIC is turned off, the hardware runs as PIC.
Instead of 24 or so IRQs, the system will use 0..15.) As far as I
know, Windows should be able to deal with the reduced number of
IRQ numbers available, but you may want to research the topic,
of what happens to Windows when APIC is turned off. I don't see
a reason why it would crash and burn, but try to do the research
anyway. I've always run my Nforce2 board at 200MHz, and did
all my overclocking with the multiplier, and I've never had
a problem with timekeeping (I use an AthlonXP-M).

http://nforcershq.com/forum/20-vt19...torder=asc&highlight=nforce2+clock&&start=190

This problem has nothing to do with any time keeping functions
as such. It is not related to your CMOS battery. It is a bug
in the Nvidia chipset.

Paul

 

[BD]

Windows when APIC is turned off. I don't see a reason why it would crash and burn,

Mm.

At this point, there are enough devices in my machine that I would
rather not do _anything_ with IRQs. And, if this little appie does the
trick, I'll just suck it up. ;-)

 

[WebWalker]

Two things you can try :-

1) Change the CMOS battery.

2) Flash the BIOS to the latest.