Re: US/Pacific-New didn't change to PST last Sunday

Article View: comp.sys.next.misc

Article #104

Back to comp.sys.next.misc Previous Next

#104

From: Brian Willoughby
Date: Fri, 30 Oct 1992 03:50

15 lines
1387 bytes

Art Isbell writes
| Did anyone else experience the failure of US/Pacific-New to change to PST
| correctly?   I set Preferences to US/Pacific and that seems to work, but will
| it work next spring?  Which is the proper Preferences setting for those of us
| in the US/Pacific time zone?

Everyone else is posting complaints that their machine isn't working in some  
way.  I just wanted to make a note that I did a clean install of 3.0 (not an  
upgrade) and my Preferences was set to US/Pacific.  The time change occurred  
correctly.  Someone else has already posted an explanation of why  
US/Pacific-New didn't change yet - its by design.
-- 
Brian Willoughby	Software Design Engineer, BSEE NCSU
BrianW@SoundS.WA.com	Sound Consulting and Signal Processing Software
NeXTmail welcome	- NO EMAIL SOLICITATION without prior permission

Technical Details

Message-ID: <Bwx1CM.1FE@sounds.wa.com>

Path: arc1-ca.pugleaf.net!sparky!uunet!ogicse!news.u.washington.edu!uw-beaver!uw-coco!nwnexus!sounds!brianw

References: <1ck55uINNg7@darkstar.UCSC.EDU>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!sparky!uunet!ogicse!news.u.washington.edu!uw-beaver!uw-coco!nwnexus!sounds!brianw
From: BrianW@SoundS.WA.com (Brian Willoughby)
Newsgroups: comp.sys.next.misc
Subject: Re: US/Pacific-New didn't change to PST last Sunday
Message-ID: <Bwx1CM.1FE@sounds.wa.com>
Date: 30 Oct 92 03:50:45 GMT
Article-I.D.: sounds.Bwx1CM.1FE
References: <1ck55uINNg7@darkstar.UCSC.EDU>
Sender: brianw@sounds.wa.com (Brian Willoughby)
Reply-To: BrianW@SoundS.WA.com
Distribution: usa
Organization: SoundSoftware, Bellevue, WA, USA
Lines: 15

Reply to Parent Message