DescentBB

I'm using windows right now, trying to do some work. I feel like my right hand has been cut off and I'm coming down the the flu.

I love the "hang on. let me freeze up for five seconds" feature.

edit:
It's so ugly. There must be a higher rate of suicide out of those that use this blOw-S.

X2

Bwaaahaaaahaaaaa! Bow to the computer OS master. You will take what I give to you, peon users.

It runs fine on my system.*

*Of course my system is a quad core with 8 GB of RAM and a SSD...

He must be using Windows 97.

Krom wrote:It runs fine on my system.*

*Of course my system is a quad core with 8 GB of RAM and a SSD...

I've got an 8 core with 12 GB of RAM and I can still occasionally either lock it up or sometimes BSOD it with some game playing. But you're right, Win 7 is far more stable than the first incantation of Windows 98 (not SE). The OS that wouldn't turn off!

Oooooooooooooh, news flash from CNBC! Facebook just took over from Microsoft the most despised company title.

Ever since Windows XP came out I haven't seen a BSOD that could really be blamed on Windows itself doing something stupid, most of the few times I've seen Windows XP BSOD I can attribute it to an absurd overclock attempt or some other obviously hardware failing, or plain old malware. My old PC ran for 5 years almost solid through 24/7/365 and it never threw a single BSOD in its entire life, even with a defective video card through some of that. Although I did dodge the bullet once after a memory upgrade by running memtest on it immediately and discovering one of the sticks was defective, if I hadn't tested it first I probably wouldn't have been so lucky.

I've have not seen Windows 7 BSOD yet, but so far the vast majority of systems I've seen Windows 7 running on I have built myself, so no surprise there.

*Pant pant* ...back on my Linux box. All is well again.

To be fair, I was using a lab computer running XP. Omg that crap was slow and I was in a bad mood; a perfect storm.

xp.. on old hardware... and it was slow.

hmm, big suprise there!


as for that freeze for five seconds thing... bet ya it was something running in the background causing that.

Ferno wrote:as for that freeze for five seconds thing... bet ya it was something running in the background causing that.

My guess it's McAfee.

Krom wrote:Ever since Windows XP came out I haven't seen a BSOD that could really be blamed on Windows itself doing something stupid, most of the few times I've seen Windows XP BSOD I can attribute it to an absurd overclock attempt or some other obviously hardware failing, or plain old malware. My old PC ran for 5 years almost solid through 24/7/365 and it never threw a single BSOD in its entire life, even with a defective video card through some of that. Although I did dodge the bullet once after a memory upgrade by running memtest on it immediately and discovering one of the sticks was defective, if I hadn't tested it first I probably wouldn't have been so lucky.

I've have not seen Windows 7 BSOD yet, but so far the vast majority of systems I've seen Windows 7 running on I have built myself, so no surprise there.

Actually, I think you're right. I've BSODed Win 7 only 3 times and I think I accidentally found out what the cause was. By coincidence, I removed a cheap media card reader/usb hub that was installed in my system and I haven't had a BSOD since, nor have I had to do a fresh reboot to play a game either. The OS gods are happy with my rig again. I still have Deus Ex freeze in the menus, but I can't blame the OS for that since the three-fingered salute works to get it out of trouble.

What ticks me off is MSE. If, for some reason if you have a lockup and have to force a reboot, it screws up one little file that keeps throwing an error log entry for eternity, unless you delete that file and reboot so that it can "recreate" itself. Stupid Microsoft.

My other gripe is the very rare and random "temporary account" problem, that I haven't solved yet. Some program, somewhere, is NOT unhooking itself from the registry during shutdown. I'm seriously looking at getting process monitor to catch the little booger in the act, but I'm tired of doing admin duties.

Heh. I'm just getting ready to deal with a few admin issues on my Linux box.

Something's changed in the last couple upgrades that broke vsftp and maybe apache. Yay for having to dig through those config files again.

I've been lucky that I've never had a BSOD in XP or my Win 7 box.

tunnelcat wrote:Actually, I think you're right. I've BSODed Win 7 only 3 times and I think I accidentally found out what the cause was. By coincidence, I removed a cheap media card reader/usb hub that was installed in my system and I haven't had a BSOD since, nor have I had to do a fresh reboot to play a game either. The OS gods are happy with my rig again. I still have Deus Ex freeze in the menus, but I can't blame the OS for that since the three-fingered salute works to get it out of trouble.

What ticks me off is MSE. If, for some reason if you have a lockup and have to force a reboot, it screws up one little file that keeps throwing an error log entry for eternity, unless you delete that file and reboot so that it can "recreate" itself. Stupid Microsoft.

My other gripe is the very rare and random "temporary account" problem, that I haven't solved yet. Some program, somewhere, is NOT unhooking itself from the registry during shutdown. I'm seriously looking at getting process monitor to catch the little booger in the act, but I'm tired of doing admin duties.

Sounds like you have too many applications installed / running and they have mucked up the OS, a problem that is likely more of a challenge for the average Linux user to reproduce. Disabling unneeded automatic startups could probably improve the situation considerably, although if it is a computer that gets used by a whole family the damage is often so extensive that only a format/reinstall can fix it.

The only time I've seen the linux kernel panic (aside from fatal errors during boot) was when I was writing some webcam code that was at the time still buggy. Even though my code was buggy, bad calls are supposed to return an error code, not crash the OS! Incidentally, later, when I was writing the Windows backend, I got the Logitech webcam driver to BSOD under similar circumstances.