home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!europa.asd.contel.com!howland.reston.ans.net!usc!zaphod.mps.ohio-state.edu!uwm.edu!ogicse!psgrain!m2xenix!jiml
- From: jiml@psg.com (Jim Long)
- Newsgroups: comp.dcom.modems
- Subject: Re: Interesting phenomena with ZyXel U-1496E+
- Message-ID: <1992Dec17.163839.19486@psg.com>
- Date: 17 Dec 92 16:38:39 GMT
- Article-I.D.: psg.1992Dec17.163839.19486
- References: <TOM.92Dec17075724@amber.ssd.csd.harris.com>
- Organization: Pacific Systems Group, Portland Oregon US
- Lines: 17
-
- In article <TOM.92Dec17075724@amber.ssd.csd.harris.com> tom@ssd.csd.harris.com (Tom Horsley) writes:
- >I have a program which dials up the NIST computer time number and sets my
- >computer's time. The way the NIST system works, you echo the characters it
- >sends you, and NIST computes round trip delay times, flagging the time once
- >it gets a consistent set of round trip delays (by changing a '*' to a '#' in
- >the line it prints).
- >
- >When attempting to run this program with my new ZyXel U-1496E+, NIST never
- >gets consistent round trip delay times (this is all at 1200 bps).
- >
-
- I see the same behaviour here (with my E+). I contacted Life Sciences
- Software (are you running TIMESET 6.0?) and found that if I _do not_ use
- the line delay adjustment (B instead of Alt-B), it works. So I have
- sacrificed a little bit of accuracy, but at least now it does work.
- --
- uunet!m2xenix!jiml or jiml@m2xenix.psg.com
-