War o(of)n Ter(Windows)ror
Saturday, February 28th, 2009So over this weekend, I decided to push my luck (yet again…) at running Windows Vista and Leopard on my MacBook (If you remember from a long time ago, I use to have Windows XP, Ubuntu, and Leopard running all together, but I ran into a few bumps and lost that set up leaving only Ubuntu and Leopard [Windows lost a well fought battle against the Ubuntu upgrade, after Ubuntu took a low blow at XP by adding a hidden partition for swap space behind my back (I still have no idea how, it just appeared like magic!)]. After about two weeks without Windows (actually, the finding of a homework assignment that required Windows), I found I was very screwed without a version of Windows on my computer. So this weekend, I decided that since it is spring break (a really really long weekend) that I would attempt to wipe my hard drive (completely), install Leopard, and then dual boot Leopard and Windows (the easy and non void of warrantee way) using boot camp. Wipe, went fine, perfect, crystal smooth (I don’t even know if that’s a phrase but I’m using it). Then boot camp, made a windows partition just fine. Then I installed the drivers for windows to use all the MacBook features… That’s when it all went down hill. I could not install any Microsoft product after installing those drivers (I believed Windows was trying to fight dirty this time in a form of mass suicide). This struck me hard in the head and got me really heated up! I decided that this time, I would play rough, and shatter this window and mix it into apple sauce and feed it to the homeless kittens by the school (ok… not really, but it has crossed my mind). I decided to use multiple versions of Windows to test this bug (yes… it was a bug, if it doesn’t work, it’s buggy). XP, same thing happened, Vista, happened again, Windows 7 Ultimate (ULTIMATE!!!!) it broke too. Looking at the results, I became very flustered… “Why could I run Windows on here before?” “Why can’t I now?” I decided to look deeper into the message that Windows was trying to send me… “Error 1923: Something something Administrator cannot perform Administrator tasks cause Windows hates (HATES) you!!!” I then decided to resort to the last (my last resort?), I googled this error code (but google is not a verb!). The first answer I received was from Microsoft (“We still hate you!!!”), “This error means you didn’t fully uninstall Office Beta” I started getting mad, “I NEVER INSTALLED OFFICE BETA!!!” It gave me no solutions, so I posted feed back “No, this was not helpful… At all, please make products that work. (I was on fire, almost literally)” I then went back to the google page and looked at other people who had the same issue, none of them had it solved, I was nearly hopeless, then I saw live search (Microsofts version of google that looks way harder to follow) and searched it in there. Amazingly, the results were different than googles (the pages were more Microsoft has seen your error before)! But non of the errors were similar to mine, because I never installed office beta. I then decided to look at a post from seven years ago that seemed more relevant that the more recent problems (Windows, as we all know, is old windows + some new stuff = old bugs with new looks [like a fly that glows… fire fly!]). This post was just like the old one saying that I had to reinstall Office beta, and then uninstall and reinstall (I still wondered where my beta was o.o;; ). I scrolled down the page further, and found another listing of reasons for the bug (but with no known solution) HORA! I found it (eureka?), there were two running processes that relied on some Microsoft stuff that needed to be changed for any Microsoft product to be installed I looked at my process list and there they were! So I ended them painfully, problem didn’t fix… I uninstalled the app and tried again… Problem still there… I finally reinstalled Windows and installed my apps and then tried installing the problem app (problem child ^.^ ), it broke my keyboard and mouse… I was overwhelmed wondering how to fix it, I thought to myself and started debating with my evil dark side who wanted to smash the computer in half and just buy a new one (which I mildly agreed with but didn’t do) and we decided on reinstalling Windows again. This time we decided instead of going with install all the boot camp stuff (which boot camp did on it’s own) we would only install the drivers for the devices we wanted to work (which was pretty much everything). To do this we decided to run all the separate executables on the Leopard DVD in the Drivers Vista looking section with a select few being avoided. After installing these and force loading a few drivers, everything worked! Windows didn’t die, stuff functioned right, and my evil side decided to subside admitting defeat to me (again)! So what was causing the bug you fellow Windows on Mac users ask? The intel mobile graphics accelerator was causing the problem, so installing everything I could but that (and some annoying install “Apple apps please”) it all came together nicely. The War on Win(Terror)dows still continues, and we await your next challenge (which should have been “Code name Windows 007”)!
Please excuse this post for being extra nerdy and bias against Windows and it’s followers, just going through all this trouble to be able to use Windows Live Messenger (and Office) to its fullest I think is bias against Apple users and Linux users, and this fight shall never end till we all merge in to Leonudows (sounds like a food dish to me)!
———– PS ————————–
Windows Live Writer is so smexy for blogging!!!! THANK YOU MICROSOFT!!!