If you play Warcraft 3, you probably know a new 1.22 patch recently came out. Exicted as the bnet community was, two common problems quickly arose:
problems either occurced concerning the no-CD fix from 1.21, or people had problems downloading the patch from bnet. After looking around to fix this problem, a certain forum-poster had mentioned something to the effect of
At that time, I thought to myselt, "wow, the only other instance I had with updates corrupting their own programs was with Microsoft updates (i.e. the Software Distribution Service issue from a year back)".
Then when I was trying to deal with the second issue, fellow interent-users pointed me to the solution: I had to download a Microsoft C++ update. Hey, look, Microsoft came in the picture again! Though while this time, they weren't directly at fault, it did strike me ironic that something like this happened, since Blizzard usually has a reputation of taking great pains to ensure their products are the best they can be...
problems either occurced concerning the no-CD fix from 1.21, or people had problems downloading the patch from bnet. After looking around to fix this problem, a certain forum-poster had mentioned something to the effect of
| Quote: |
I noticed that the new patch had corrputed my War3.exe...gee thanks a lot, Blizzard  |
At that time, I thought to myselt, "wow, the only other instance I had with updates corrupting their own programs was with Microsoft updates (i.e. the Software Distribution Service issue from a year back)".
Then when I was trying to deal with the second issue, fellow interent-users pointed me to the solution: I had to download a Microsoft C++ update. Hey, look, Microsoft came in the picture again! Though while this time, they weren't directly at fault, it did strike me ironic that something like this happened, since Blizzard usually has a reputation of taking great pains to ensure their products are the best they can be...
