2726
General Software Discussion / Re: What went wrong with Linux on the Desktop
« Last post by Stoic Joker on September 06, 2012, 02:03 PM »I had BSODs on my nforce4 motherboard when trying to use nvidia's "hardware" firewall (which was a retarted piece of crap, requiring a full install of an apache httpd in order to manage settings locally... :rolleyes: ), and I've had BSODs from third-party firewall, VPN and antivirus products. Some of these seem to show winsock as the problem, but that's only if you look just at the top-level driver in the BSOD, not if you study the actual minidump with WinDbg. Also, I've never had filesystme or registry corruption from any of these "normal" BSODs. Got more information on the issue?Not BSOD due to reg but was because of the theme patching and shell related changes. In case of reg issues, most of them were related to the WINSOCK and other network related issues. I can't specifically point to the issue because I used to patch that using the reg fix for Winsock. Without that fix, It was hard to connect to the net. I am not sure if it was because of driver issue or say some malware? For some reason system was not usable without those reg fixes (most of them were released by MVPs), I hope you remember XP days with regular fixing of broken stuff.-f0dder (September 06, 2012, 12:10 PM)-mahesh2k (September 06, 2012, 01:41 PM)
Only time I ever saw WINSOCK get borked was usually due to an orphaned LSP from either a virus or babysitter security suite (mostly the 2nd one). Either way the fix has always been the same netsh reset winsock ... I don't ever recall using a reg patch for it.

Recent Posts
...I kinda like it myself, and I'm looking to switch to a Win8 phone in the next month or so (whenever they come out).
I'll make popcorn 


