NanoBreaker

Re: «<< 12Oz Computer Tech Support >>> hangovers suck ass

totally agree i seen this shit i was like wtf were they thinking if you would fall or get hit it would pop right through yer skin and shit and just having that in yer body the feeling would just be so damn nasty

Re: «<< 12Oz Computer Tech Support >>> is this for a MAC or PC

Re: «<< 12Oz Computer Tech Support >>>

does anyone have these? or would you ever get one?:o

How to get mexicans in and out of a car How do you get a bunch of mexicans in a car? Throw a dollar in it. How do you get them out? Throw in a job application!!!

Re: «<< 12Oz Computer Tech Support >>> no dont wear clothes kids be like me and have help walking with your 3rd leg its great when trying to take pictures you can stand perfectly still

the movie sucked video game is better

Re: «<< 12Oz Computer Tech Support >>> YES!!! microsoft down 11% in stocks keep going lower and buy some stock in them assholes make me some moneys

Re: «<< 12Oz Computer Tech Support >>> hey look its a bumparoo

damn sorry about the size fucking huge

Re: «<< 12Oz Computer Tech Support >>> bump

dope pics

this ass is better

real or fake cat tounge really like that?

Re: «<< 12Oz Computer Tech Support >>> There are lots of ways to get to Event Viewer, but I typically hit Start, Run, and type eventvwr. There are typically three logs available: *Application: applications running under Windows are supposed to log their events here. *Security: when enabled, Windows can log a host of security-related events, which are logged here. *System: the operating system logs its events here. If you click on the System node on the left hand side, you'll get something much like this: Each line on the right corresponds to one event logged by the system. The event type can be a "Success Audit", Informational, a Warning, or an Error. Information here includes the date and time of the event, the source (the Windows component in this case) of the event, the "category", an event number, the user account in use when the event was logged, and the computer name. This is where things start to get a little disorganized: *There are no hard and fast rules for what constitutes an error, warning or informational event. In fact, a properly operating system might show Error entries in the event logs. *As you can see in this listing, "category" is rarely used. *Each event is assigned a number. We'll see in a minute how to translate them, but for the moment, this display is rather meaningless to the casual observer. If you double click on one of the event lines in the right hand pane, you'll get something like this: This is actually a fairly useful warning. The error number corresponds to the message displayed in the Description box. Here, my system is telling me that my clock might be off because it wasn't able to reach a time server for an extended period of time. Clearly, just a warning. From my application log, however, comes another all-too-common type of entry: This "Success Audit" of my run of Office Update is trying to tell me something. Unfortunately "The Description for Event ID (0) ... cannot be found" is a very common Event Log entry. Often there will be additional data included that might give a clue as to what was being logged. In this case it appears to be a successful install of "VSDEBUG_6707_ENG". I think. And that leads to how things get even more obfuscated in the event log: applications, often included the operating system itself, fail to log things correctly, or at all. In their defense, the event log has a very convoluted interface to program to, but nonetheless, while difficult, it can and should be used correctly. So, should you care? Absolutely. The Event Log is far from perfect, but it can contain valuable data. At worst, it will tell you nothing. At best, it may hold important clues to problems you may be having with your computer, or the applications you're using. Go ahead and browse around in the event viewer. Don't panic when you see lots of warnings or errors; as I said, even a functioning computer will have those. In fact, if you look while your system is functioning normally, you'll get a sense of what "normal" looks like in your event log. Then later, when you see items that seem suspicious, out of place, or seem to be related to the problems you're seeing, that's information worth paying attention to.

Re: ANIMATED GIF HALL OF FAME SUPERTHREAD

3.98

Re: «<< 12Oz Computer Tech Support >>> defrag

railroad dicks have more power then local cops if they catch you in the yard they can shoot yer ass if they feel like it