Reason pickafuckinghugeassnumber Why There Aren't Enough Women in Gaming
No Go News
Within Office 2003, the ability to launch a newsreader is turned off by default. Why they changed this from previous versions, I?m not quite sure. All the same, I ran across a fairly ridiculous issue common to the 2003 package. To turn on this feature, you must go to the Tools menu, choose Customize and then select the News feature from the Go options. Cool, right? Initially, yes, but the News option will either disappear or instead of launching the newsreader, will open an Explorer window that shows several DLL files. If the menu option disappears, if you go back to Customize, it no longer shows up there either. Hmmmm?well after a bit of research and tooling around on my own PC (I wound up experiencing the same problems), I came up with a simple, if not odd solution.
According to the research I came across, this issue comes from setting Outlook Express as the default newsreader. OK then?yeah, that makes sense. *ahem* The solution is to go into your Internet Options in the Control Panel and set the default newsreader to Outlook Express on the Programs tab. You then launch Express and select No to the default newsreader question. Once you launch Outlook 2003 again, you will now have full newsreader functionality. If all else fails, create a shortcut that points to the following "C:\Program Files\Outlook Express\msimn.exe" /outnews
Common Language Barrier
Another interesting lil issue I ran across recently was a ?Common Language Runtime not loaded? error within Visual Studio .NET. This was accompanied by the issue of not being able to see the properties of a particular project. The properties were completely blank. VS .NET 2003 was also installed on the machine, but it appears not to have contributed to this problem and was functioning properly. Research online returned very few helpful results, so I was pretty much on my own on this one. I didn?t think a repair would fix the solution, so maybe it was a third party plug-in. I ran .NET using the /safemode switch to see if running the program without any plug-ins would resolve the error. No such luck. I had seen a few mentions of .NET Framework, but this PC already had 1.1 installed. I honestly didn?t have much faith in a repair or reinstall fixing things up due to what I had seen in my error research, but I thought I would give it a shot. When I launched the Add\Remove, the option to reinstall or repair was grayed out. Hmmmm?odd. I ran the setup and decided to try the components update and see if that was holding things up. It indeed, was. The component update was pretty standard; web extensions, setup runtime files and the .NET Framework. I knew there had been revisions to version 1.1 and that?s all it took. Once I ran the update and restarted, all was well. No more errors within .NET and the project properties were showing up perfectly. I have to say, luck was on my side with this one.
I don?t excel at too many things in this life?I?m not particularly book smart which is proven by the lack of High School and College diplomas adorning my wall. I have the distinct knack of saying something completely off the wall at precisely the wrong moment. And to top things off, at times, yes I know this can be hard to believe, I can get a bit uppity and a tab bit bitchy. I have adjusted to these personality pitfalls and quirks throughout my life and have even grown to appreciate them from time to time. But the things I really suck at and can?t accept? Those would be parking and wireless cards. Odd combination? Yes. But true.
The parking? Well, that actually has nothing to do with the fact that I have a beast of a pickup. No matter the car I have owned, I just can?t grasp the parking concept. This, I have never been able to improve upon or understand. Much, might I add, to the disappointment of those neighboring my designated parking spot both at work and home. Don?t even get me started on how awkward I get when it comes to parallel parking?
Fortunately I have no outstanding retardation (mostly) when it comes to supporting WiFi cards at work. This is a good thing considering I must deal with them often and it would be quite damaging professionally speaking. But when it comes to my own purchases, that is a whole different story. I have probably run through a boxful of wireless cards and USB adapters over the past few years. I?m inclined to believe this is not exactly normal. There is no pattern as they have all been different makers and models. Well, there is one pattern?all die within my grasp. Be it from accidental tips of my laptop which lead to crushed cards or various driver and software glitches no other human on Earth has experienced.
I guess if I managed to come to terms with far worse things in my life than this, I will eventually accept the troubles I have with parking and wireless cards. But ya see...that's what ties me up. These are so trivial and should thus, be easily resolved. Not exactly. It's always the details that fuck one up.
After staying home sick with a nasty lil cold, I popped in to check my work email and catch up a bit. It appears to have been a very hectic day for We IT Folk. It was filled with various ridiculous requests and countless unnecessary smartass comments* mixed in with several valid issues and concerns and to top it off, an IT Newsletter gone horribly wrong. Hidden deep within my Inbox I find the following email:
Ineedanewkeyboard.Tespacebarandoterrandomkeysdontworkanymore.
Tanks.
Classic. It still makes me giggle.
*Seriously folks, what is the point of throwing out demeaning comments? It isn?t going to make things happen faster. It only serves to further prove what a thoughtless dick you are. I guess I?ll never understand people.