WoW, is right...
Mar. 4th, 2007 09:11 pmWhile Natalie was here last night, I started to download World of Warcraft, hoping to be able to install it and have Natalie show me the ropes, as I had indicated a curiosity about the subject (though I am not really inclined to add another time sink to my already overburdened schedule). After a few minutes of downloading at less than impressive speeds, the downloading utility informed me that the reason for the slow performance was, likely, my firewall and my router.
I did knock my Outpost firewall out, intending to see what would happen performance-wise, and as expected, it had no effect. Once I granted the downloader permission to do its thing, Outlook went about its other business, so disabling the firewall was probably not that great an idea.
Actually, it was not turning the firewall back on that was not that great an idea, but I digress.
I resumed the download of WoW's 3.15 GB installation file this morning, and finally completed the process. Upon trying to install the game, my VAIO threw an bad memory NMI error, halting the machine. Shutting the machine down and starting it back up revealed a desktop configuration vastly different than the one I had started out with previously.
After about 30 minutes of juggling, I rebooted and managed to restore the desktop to what it was, except for my quick-launch items, which had been alphabetized for me by some capability in XP and which I was too lazy to try to rearrange back to my liking.
Writing off the memory error as possibly some kind of one-of-a-kind random error, I attempted the installation again, and got the same error.
This time, it took me a full hour or so to restore some semblance of order to my desktop, and that time didn't include the time spent running the Microsoft memory checking utility for a good long while. By then, it was time to start translating.
Between this, that, and the other thing, I've gone for a walk with Galina (it's cold outside, but it gave me something to do while the VAIO's memory was being checked), taken a nap, encountered problems with my other system (delayed write errors on a Windows 2K system, which had never happened before), and now, pretty much finished the translations due tomorrow.
I have to finish them, however, before I go to sleep, as I am due to substitute for someone tomorrow at JSC, an all-day assignment, according to the on-call person who called a few hours ago.
What prompted this post was having some kind of window pop up on top of me typing in Word, only to immediately disappear and have the computer start buzzing loudly (which somehow made me look at the firewall icon in the system tray, which showed the thing to be off). For all I know, whatever popped up was asking me if I agreed to sell my first-born to the Vogons, and I only happened to be typing a "y" when it happened.
In any event, I've shut down all applications except for Word and Semagic, and checked my process list for unusual items (and found none). I should probably reboot the machine, to be on the safe(r) side.
Ye gods, it's already after 9 pm.
Cheers...
I did knock my Outpost firewall out, intending to see what would happen performance-wise, and as expected, it had no effect. Once I granted the downloader permission to do its thing, Outlook went about its other business, so disabling the firewall was probably not that great an idea.
Actually, it was not turning the firewall back on that was not that great an idea, but I digress.
I resumed the download of WoW's 3.15 GB installation file this morning, and finally completed the process. Upon trying to install the game, my VAIO threw an bad memory NMI error, halting the machine. Shutting the machine down and starting it back up revealed a desktop configuration vastly different than the one I had started out with previously.
After about 30 minutes of juggling, I rebooted and managed to restore the desktop to what it was, except for my quick-launch items, which had been alphabetized for me by some capability in XP and which I was too lazy to try to rearrange back to my liking.
Writing off the memory error as possibly some kind of one-of-a-kind random error, I attempted the installation again, and got the same error.
This time, it took me a full hour or so to restore some semblance of order to my desktop, and that time didn't include the time spent running the Microsoft memory checking utility for a good long while. By then, it was time to start translating.
Between this, that, and the other thing, I've gone for a walk with Galina (it's cold outside, but it gave me something to do while the VAIO's memory was being checked), taken a nap, encountered problems with my other system (delayed write errors on a Windows 2K system, which had never happened before), and now, pretty much finished the translations due tomorrow.
I have to finish them, however, before I go to sleep, as I am due to substitute for someone tomorrow at JSC, an all-day assignment, according to the on-call person who called a few hours ago.
What prompted this post was having some kind of window pop up on top of me typing in Word, only to immediately disappear and have the computer start buzzing loudly (which somehow made me look at the firewall icon in the system tray, which showed the thing to be off). For all I know, whatever popped up was asking me if I agreed to sell my first-born to the Vogons, and I only happened to be typing a "y" when it happened.
In any event, I've shut down all applications except for Word and Semagic, and checked my process list for unusual items (and found none). I should probably reboot the machine, to be on the safe(r) side.
Ye gods, it's already after 9 pm.
Cheers...