Hello Everyone, Mat is in the process of forming UL Lafayette's first Open Source student organization. He has had a wonderful response from undergraduates and many Grad students. ULOSLUG will be submitting a request for charter soon. I think it would be nice if you visit their website and show your support.
http://uloslug.ath.cx Great job Mat! Don't forget to take Nicole out for all her support through thick and thin. Thanks, Sonja -------------- next part -------------- An HTML attachment was scrubbed... URL: http://oxygen.nocdirect.com/pipermail/general_brlug.net/attachments/20030913/202ce485/attachment.htm From [EMAIL PROTECTED] Sat Sep 13 21:37:43 2003 From: [EMAIL PROTECTED] (will hill) Date: Sat Sep 13 20:03:50 2003 Subject: [brlug-general] M$ did cause the blackout. In-Reply-To: <[EMAIL PROTECTED]>; from [EMAIL PROTECTED] on Sat, Sep 13, 2003 at 09:38:40 -0500 References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On 2003.09.13 09:38 John Hebert wrote: > Will, > > I skimmed through the article but saw no mention of Microsoft failures. > > How did you arrive at your conclusion? > > John Hebert This does: "That day, Midwest I.S.O. faced a computer malfunction at a big utility it monitors, FirstEnergy of Akron, Ohio, making it harder to track grid conditions, and computer problems at its own headquarters that were, at the least, an added distraction." I think that these malfunctions were Microsoft. I can't put my finger on it, but I remember reading that the monitoring software was on their platform and that something dumb like blaster ate it. Also, it looks as if they were depending on it because they were stretched too thin to properly monitor the other equipment which may have indicated other problems that got by them. I also suspect the "state estimator" was running on windoze. We had such estimating equipment for core monitoring at River Bend. The plant could be run without it, but it was helpful. The program's writers actually put in a splash screen saying that it was for "Windoze". I can imagine that the "state estimator" was a similar work running on a little box in the control room. I'll bet anyone a nickel that the only thing the monitor system and state estimator have in common was Microsoft under it.
