NLM FOR NETWARE 3.12 (Networking Products)
At 29 JAN 1998 08:50:37AM CITY OF PROVIDENCE wrote:
WE JUST INSTALLED A NEW SERVER PENTIUM 2 300MEGAHRTZ 128K AND THE CMOS CLOCK AND THE NETWORK TIME ARE NOT THE SAME. THE SERVER TIME IS LOSING ANYWHER FROM 1 TO 6 MINUTES PER DAY. WHEN THE SERVER IS DOWNED AND REBOOTED THE TIME IS CORRECT. HAS THIS PROBLEM SURFACED ANYWHERE ELSE.
At 29 JAN 1998 08:59AM John Duquette wrote:
I don't see where our NLM has any bearing on this problem, but I used to have a PC that lost a significant amount of time (several seconds/day). I solved it by installing TARDIS tardis is a 95/NT utility that checks and if necessary corrects your clock from the time servers.
Alternatively you can:
1) check/replace the CMOS battery
2) contact your hardware manufacturer (i.e. motherboard manufacturer)
John Revelation
At 30 JAN 1998 05:27AM Steve Smith wrote:
Interesting. At 300 mHz the server would have to have a process steal a significant time-slice from the BIOS int 8h (clock tick) which ticks 18.2 times per second.
Some NLM is robbing significant cycles from your machine's clock interrupt, and potentially int 70h as well, which ticks a lot faster.
The fact that a reboot solves things means that your PC clock chip is accurate, but that something is piggybacking onto Netware so much that it shows when a 300 mHz machine gives it enough action, and the BIOS ticks are retarded by active processes.
You might identify the NLM culprit by elimination. Failing that, I could write you a utility which reset the server clock each hour from a more reliable workstation clock. Email me if this is what you want.
Steve
At 02 FEB 1998 10:46AM city of providence wrote:
Revelation response for nt/server. Is this the same for netware??