Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!killer!mjbtn!root From: root@mjbtn.UUCP (Mark J. Bailey) Newsgroups: comp.sys.tandy Subject: Re: Time on Tandy 3.2 Message-ID: <241@mjbtn.UUCP> Date: 13 Apr 88 12:08:29 GMT References: <1618@scicom.alphacdc.com> Organization: JobSoft Design & Development, Murfreesboro, TN USA Lines: 36 Summary: it is compiled into the problem code In article <1618@scicom.alphacdc.com>, cyrill Sun Apr 10 06:49:16 1988 writes: > > 1. uucp still executes its scheduled calls according to crontab > entries, using Daylight time. However, when it logs these, and all > incoming calls, it logs them in STANDARD time (without an xST suffix). > > 2. When BASIC reads the time, such as in "PRINT TIME$", the time > returned is, again, STANDARD time, not daylight. I do not remember > this problem occurring in previous years, under different versions > of XENIX. When Tandy released 3.2, they had compiled the new Daylight Savings Time change period into the "basic system" code. This is why your system clock changed appropriately. However, other programs like MBASIC and uucp are not part of the "core release" and have not been modified. You will have to ask Tandy about MBASIC as it is a separate package. When the 3.2 release of their development system (which usually follows two to three months after a release of a "core" upgrade), they will have supposedly fixed the CDT/CST problems with uucp, at, and any other programs that ordinarily come with the Xenix Development System. Hope this helps. Mark. -- Mark J. Bailey _____________________________________________________ _________________\ _____| > @ Nashville Knoxville _/ / + ____'' > Jackson + <*> MURFREESBORO _/ / "From the Heart of Middle Tennessee!" ___> > + Memphis Chattanooga _< <______________________________________________+_______/ JobSoft UUCP: ...!{ihnp4,cbosgd,mit-eddie}!killer!mjbtn!root Design & Development Co FIDO: Mark Bailey at Net/Node 1:116/12 Murfreesboro, TN USA