Discussion Locked

NW 5.0 server losing time

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Single server is losing about 1.5 min/day. We tried TIMESYNC to an external NTP source but TCP/IP apparently collides with an old version of Btrieve 6.10f which is necessary for the main DOS app. Upgrading Btrieve is not an option. We already unloaded the IDE drivers. Is there a way to sync with a local CL32 station instead of an outside source? Are there any other hardware or software solutions?

9 replies

by grbeckmeyer

This is a known problem with the TIMESYNC.NLM version 5.12 (and possibly some higher versions) Check your version of this NLM, and try reverting back to version 5.09 (from SP2)and dated 2/11/99. You will need to copy this version over your current, then reboot the server for the changed file to take affect.

by w1ngate

If you are useig an IDE cd rom unload the driver. This took care of the time issue on our server

I am told by Novell that the latest service patch will take care of this.

by pam_greenup

A software solution that worked for us was to upgrade your IDEATA driver. Our server was losing 20 minutes a day. The IDEATA5.exe patch can be found at the Novell support page. This is very easy to do and only takes a couple of minutes. You will need to reboot your server.

by estebandelatorre

Removing IDE controller from PC's setup should be enough, but sctrictly responding your question...
Not to a client, but...take a look arround, sure you will find enough hardware to install a 2 unlicence NW 5.0. Make this your SiNGLE type Sync, andmake the production server a SECONDARY. Do not add to the tree, unless you are now planing to add some replicas here, It will save your time when a new SP arrives that fix this issue, simple turn off the SINGLE and start tracking time... Perhaps the HW clock is damaged!)
edt@bancobgn.com

This discussion is closed to new replies.