|
|||||||||
|
|||||||||
|
|||||||||
 |
|||||||||
| |
||
|
|
|
|
|||||||||
|
|||||||||
|
|||||||||
|
|||||||||
| |
||
|
|
|
| |||||||||
| View Poll Results: Did you find this guide helpful? | |||
| Yes, this guide was very helpful. |    | 28 | 100.00% |
| No, this guide wasn't very helpful. |    | 0 | 0% |
| I have no opinion. |    | 0 | 0% |
| Voters: 28. You may not vote on this poll | |||
 |
|
| Thread Tools | Search this Thread | Display Modes |
Dev Hardware Forums Sponsor:
|
|
|
March 29th, 2006, 10:43 PM
|
||||
|
||||
|
Dealing With Spyware, Adware, Viruses, and Other Malware
There are literally hundreds of sites on the internet dealing with spware, adware, and viruses. And this is a topic too large for a single post, so I'll just provide some good links for you.
OptimizeXP Virus Removal 101 -- Virus Removal Primer Windows XP Security Checklist Direct Link: http://guide.nilpo.com/spyware
__________________
 Click the image if at any point you don't like my decision.10011100011000101111100011100000011000000100000011 10010011011110110001101101011011110100011000001110 0100111101000100001 Visit Nilpo.com and Ask the Windows Guru! Open me for some very useful links!
 Last edited by Nilpo : October 31st, 2007 at 07:09 AM.
|
|
March 30th, 2006, 04:25 AM
|
||||
|
||||
|
Dealing With Random Problems and Glitches
So, your just having some intermittent problem. There doesn't seem to be any rhyme or reason for it, and it happens whenever it wants regardless of what you are doing. Now what?
This is an excellent time to post in the forums. Intermittent problems that don't seem to have a direct cause are usually related to failing hardware. Maybe you've got RAM going bad or a video card that's about to quit. Update all software and drivers in your system. Try booting into Safe Mode and letting your computer run for a while to see if the problem occurs there as well. If it does, that usually confirms a hardware issue. Benchmark. Test your hardware, preferably with a bootable software that doesn't require Windows to operate. And last, but not least, test your power supply unit (PSU). A failing power supply will generally underpower your PC and can cause some pretty strange things to happen. <edit=Dngrsone>Go to DevHardware!  </edit>Direct Link: http://guide.nilpo.com/glitches Last edited by Nilpo : October 31st, 2007 at 07:15 AM.
|
|
April 3rd, 2006, 04:11 PM
|
||||
|
||||
|
Troubleshooting Windows Errors
While Windows is pretty good about handing out errors when something goes awry, making any sense of the error can sometimes be quite a chore. Hopefully, I can make this a little easier for you.
First, you have to understand that there are many types of errors: General Protection Faults, Page Faults, Illegal Operations, and Fatal Exception errors just to name a few. Knowing the type of error is the first step in deciphering what it means. Windows also has various ways of throwing errors. You also need to determine if it is a program error, a module error, or a system error (kernel32.dll). Windows 2000 and XP simplified this process over earlier versions by reducing the number of error types. So we'll divide this article into two sections Windows 9x Errors (including Windows 95, 98, and ME) and Windows NT Errors (inluding Windows 2000, XP, and higher). Windows NT follows the NT system for the most part, but there is some overlapping. The 64-bit Windows releases should follow the NT model pretty closely. General Error Information: Windows basically uses three types of error codes: text, numeric, and hex codes. Numeric errors, such as Dialup Networking Errors, will simply have a reference number for an error code. Numeric errors will usually also have a text descriptor associated with them. These are generally the simplest errors to troubleshoot because they simply associated a known problem with a known cause. In other words, they return a listed error code under specific circumstances. For instance, if your modem has no dial tone, it simply returns the error code that means just that. Hexadecimal error codes are a little different. While they usually have a text descriptor, these errors are usually a little harder to decipher because they are system generated rather than listed errors. Because they are system generated errors, they often have multiple parts as well. In some cases, this is made a little easier with a text handle. Text errors will either be a text handle appearing as all capital letters with words separated by underscores (i.e. UNMOUNTABLE_BOOT_VOLUME) or as test descriptions (i.e. Unable to connect.) While text errors don't usually occur without either a numeric or a hex code, it just wouldn't be Windows if it didn't happen once in a while. I get asked a lot why it's so hard to research an error code. "Isn't there a list somewhere of all the possible error codes?" The answer quite simply is no. That just isn't possible. Windows is a product comprised of many parts. While many of them are made by Microsoft, still a good many are made by third parties. It would be nearly impossible to generate a list of error codes to cover all of the multitude of possibilities. Windows 9x Errors:
Windows NT Errors: ...writing in progress... Additional Resources: Windows 4 Support Center (Windows 9x) Direct Link: http://guide.nilpo.com/errors Last edited by Nilpo : October 31st, 2007 at 07:15 AM.
|
|
April 4th, 2006, 01:05 AM
|
||||
|
||||
|
Recovery Suggestions and Disaster Planning
Don't wait for disaster to strike. Prepare for the worst now. Here are some simple ways to prepare for a disaster so that you can get back up and running as soon as possible.
System Restore System Restore is a recovery tool that can come in quite handy at times. It creates system snapshots (or restore points) that can be used to roll your computer back to a previous state. If a program installation goes wrong or you catch a virus that leaves your system unusable, you can use System Restore to return computer back to a time before it happened.
Description of the Windows File Protection Feature How to Set up and Use Automated System Recovery in Windows XP Direct Link: http://guide.nilpo.com/recovery Last edited by Nilpo : October 31st, 2007 at 07:16 AM.
|
|
April 4th, 2006, 01:32 AM
|
||||
|
||||
|
Additional Resources: Finding the Answers You Need
Okay, none of the advice here worked and you weren't able to get any help in the forums. Now what?
It's time to get some first hand support from your software or hardware's vendor. Find their tech support number and call or visit their website and look for support desk or trouble ticket link. If, at this point, you're still unable to get operational, it's probably time to start replacing hardware. But don't give up just yet, the links below can be very useful for hard to find information. Help and Support: Microsoft Help and Support Windows Support Center Microsoft Online Crash Analysis Technical Resources: Microsoft Dll Help Database (Good for Identifying Windows Files) Direct Link: http://guide.nilpo.com/answers Last edited by Nilpo : October 31st, 2007 at 07:16 AM.
|
|
April 4th, 2006, 01:52 AM
|
||||
|
||||
|
An Overview of Windows Troubleshooting and Recovery Tools
Last edited by Nilpo : October 31st, 2007 at 07:17 AM.
|
|
April 16th, 2006, 03:34 PM
|
||||
|
||||
|
What To Do When All Else Fails
Last edited by Nilpo : October 31st, 2007 at 07:17 AM.
|
|
Trader Rating: 2
·
# |
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
