I'm not saying the blue screen is a good thing ;-> personally I'd like a "This piece of software broke in this way" message and what was making the call to rundll32 or whatever it was ( its been that long since I've had BSOD's I cant remember what they normally happened in) In the past year I think I've had 2 blue screens and both of those were about a week apart, and surprisingly just after I put some new ram in, now its out everything has been fine once again. god damn K7S5A motherboard. (those 2 bluescreens count 3 computers one of which runs 24/7 (its a k6-2 500 with 128mb ram and a 120W psu running 3 hard drives, Now thats abuse)) ----- Original Message ----- From: "John Ferrell" To: Sent: Monday, June 30, 2003 10:32 AM Subject: Re: [OT]: Why MS$ Is Loved > True, but the OS is in the best position to be able to effect a recovery or > at least point in the general direction of the problem. > The Blue screen says "Broke" and nothing more. > > John Ferrell > 6241 Phillippi Rd > Julian NC 27283 > Phone: (336)685-9606 > johnferrell@earthlink.net > Dixie Competition Products > NSRCA 479 AMA 4190 W8CCW > "My Competition is Not My Enemy" > > ----- Original Message ----- > From: "Jake Anderson" > To: > Sent: Sunday, June 29, 2003 8:09 PM > Subject: Re: [OT]: Why MS$ Is Loved > > > > sorry but saying that an OS can make up for faulty hardware is plain and > > simple crap. > > > > baring fantastic measures (eg those used for satellites where they expect > > solar proton events) no OS will make up for the CPU spitting out the wrong > > answers. > > ----- Original Message ----- > > From: "Peter L. Peres" > > To: > > Sent: Monday, June 30, 2003 4:19 AM > > Subject: Re: [OT]: Why MS$ Is Loved > > > As to clocking down, scores of people run dual boot machines and the > *nix > > > variants almost never need clocking down to make them work. It is > entirely > > > possible to write software (esp. io and interrupt related) that pushes > the > > > hardware or latency tolerance so far that it needs clocking down to make > > > it work. On *nix those code parts are usually extremely well written and > > > debugged. > > > > -- > > http://www.piclist.com#nomail Going offline? Don't AutoReply us! > > email listserv@mitvma.mit.edu with SET PICList DIGEST in the body > > -- > http://www.piclist.com#nomail Going offline? Don't AutoReply us! > email listserv@mitvma.mit.edu with SET PICList DIGEST in the body -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! email listserv@mitvma.mit.edu with SET PICList DIGEST in the body