[EMAIL PROTECTED] wrote:
>> the BSOD in Windows XP looks very nice! It now displays more >> human-comprehensible text and sounds "friendly" too - but it > >Is the color configurable? I wonder what a Neon Green Screen of Death >would look like... I think it's a no. But if you should get one, it reads somehow like "This is the first time you get to this screen..." I laughed a good one when my classmate who attended the .Net seminar months ago made XP RC1 crash just three days after the seminar and related the contents of the new BSOD (And he was proud of it too initially, since it took him three days...) And it is still blue (since it is the Blue Screen of Death)! Some people say the BSOD text exudes the big-daddy effect that M$ wants to project. However, it still doesn't offer enough clues to deduce where did it go wrong for some cases (there exists...) for debugging to proceed. I've yet to crash WinXP myself at home (since I don't have one, and I'm not inclined to install it to my lone win98 box which is only a Pentium 200MHz with 64MB of RAM at max already, so running XP might be an impossible event for me) so I'm not sure if XP RC1 and XP final's BSOD didn't change at all... Talking about the BSOD kinda reminds me of the UNIX version - the controlled crash that uses the ostrich algorithm of deadlock resolution: kernel panic; which is quite a rarity, save when your hardware flops. Haven't seen one for quite a long time already (last time I had one was back then when I was still using 2.4 athlon-optimized kernels compiled with gcc-3.0. It would crash after a resource-intensive task has been done in the system, such as compiling gcc. since reverting back to gcc-2.95, haven't encountered another kernel panic again). Paolo Falcone __________________________________ www.edsamail.com _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
