SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 15 | November | 2004 ]

<< Previous Message << >> Next Message >>


Date: Mon, 15 Nov 2004 17:21:06 PST8
From: Tom Brown <thombrown@san.rr.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: OT: FAA times out . . . (was W2K pagefile.sys )

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Jeffrey Race wrote:
> On Mon, 15 Nov 2004 16:18:16 PST8, Mark D. Overholser wrote:
>
>
>>Remember, this is Windows (TM), the OS that requires reboots for things
>>that "other" OS's just do by running a little "script".
>
>
> Now that I have you all on the line, I am curious about an article
> appearing in the latest IEEE Spectrum, just here, about a Harris Corp.
> system installed for the FAA which crashed causing LA control towers
> to be unable to reach any planes . . . then the backup system also
> failed. Fortunately there were no crashes because of some automated
> system built into new planes ("Pull up . . . ! Pull up . . . !).
> Anyway the postmortem discovered that the SOP to reboot the system
> every 30 days had not been followed, since it was designed to
> crash every 49 days due to some timer sequence termination.
> Could this be some W(%&*& behavior? If so why would anyone design
> a system in this way? And does OS/2 suffer a similar vulnerability?
> What to do? Gory details please.
>
> Jeffrey Race
>

My memory is somewhat foggy, but the 49 day figure seems to ring a bell.
ISTR that is the time it takes for the real-time clock to overflow, at
least in OS/2. Probably so in Windoze, too. If the clock driver doesn't
handle it correctly, it could screw up the timekeeping for the system
and thus many other things as well. Think of the time functions required
to keep aircraft a "safe" distance apart, estimate ETAs, etc.

Someone else may come up with a better explanation.

--
Tom Brown
thombrown at san dot rr dot com
Member SCOUG, V.O.I.C.E. & SDAA
running eComStation GA + FP 3
eCS system uptime is 0 days 00:42 hours

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 15 | November | 2004 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.