I have a question. Why would a router firewall not do the trick?
Hi cjessee
Well as Doby mentioned, a hardware router monitors data packets in and out of your computer. A firewall, working closely with a router program, examines each network packet to determine whether to forward it toward its destination. The best and most efficient way is to have a router w/firewall and a software firewall. Viruses, BHO's, spyware, adware, malware; keyloggers, trojans etc cannot be scanned for, detected, monitored, scanned, filtered, removed and managed by a firewall, and especially not a router firewall. Real-time browser protection, real-time registry protection, enhanced site blocking (many more utilities) are also needed, such as provided by IE-SPYAD, MVPS HOSTS file, Spyware Guard, SpybotS&D Tea Timer etc. Port (& ad, cookie) management is mostly what the firewall does, but a router firewall will not be able to allow you the option to control net access by applications on your system such as what a software firewall does.
Anyone know anything about "Advanced WindowsCare Pro 2?"
Its very good for all else but not a firewall though.
how would I be able to tell if there's a firewall in the router?
Check your manual or your specs online, or enter the router config and check there if there's an option for Firewall enabling. There should also be a router firewall program.
Also one time I was surfing the web and Norton said "an intrusion attempt on your computer has been blocked". Is that the standard virus block notification?
Norton 2005 Internet Security is the last I had so I can't be sure there. Although yes, the blocking would prompt a window message of similar sorts I guess.
Kalim, what do you mean by the user had Style XP installed in reference to Ntoskrnl.exe errors?
Well it seems you didn't have Style XP installed. Its used to install themes, wallpapers, icons on WinXP systems.
Ntoskrnl.exe is one of the files you have to swap inplace of the original in
system32. If you swap the wrong file, such as one for SP2 on a SP1 system, your system will fail to load-up.
Since this is no more a problem for you, I don't see a point for dwelling on it further now.
The reason I ask is that I have Windows XP and a day before the computer crashed my son tried to install "Oregon Trail" on the computer but it wouldn't work because it was made for Windows 95/98. Could that install have caused the Ntoskrnl.exe error? Thanks!
Nope, it should have nothing to do with the system32 folder. Its a matter of troubleshooting such errors, as various reasons for it arising coexist. Here's a good start:
http://www.computerhope.com/issues/ch000646.htm