Path: utzoo!mnetor!uunet!nbires!isis!scicom!cyrill
From: cyrill Sun Apr 10 06:49:16 1988
Newsgroups: comp.sys.tandy
Subject: Time on Tandy 3.2
Message-ID: <1618@scicom.alphacdc.com>
Date: 10 Apr 88 13:50:15 GMT
Sender: cyrill@scicom.alphacdc.com
Lines: 33


Reply direct to 'reo!root by mail as he doesn't get news.

	From reo!root Sat Apr  9 15:23:23 1988
	Received: by scicom.alphacdc.com (smail2.5)
		id AA08815; 9 Apr 88 15:23:12 MST (Sat)
	To: cyrill
	Subject: Time on Tandy 3.2
	Date: Sat Apr  9 15:05:48 1988
	
The advent of Daylight Savings Time this past week has brought out
an appearent bug in either XENIX 3.2 or MBASIC for the Tandy 16/6000.
Both products are from Microsoft.  The "bug" is as follows:

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.

Has anyone else encountered this, and is there a fix available?
The one in uucp is minor, but BASIC programs that test the time
before executing a function can be adversely affected by the
second.

Richard E. Oakes
USPS:  602 Dawson Street                             CompuServe:  70475,333
       Aurora, Colorado  80011-6907
UUCP:  {boulder, ncar, nbires, isis}!scicom!reo!rick