The lockup isn't likely taking place, but you think it is.
What's likely occurring is that you are trying to access
the update server using a dial-up connection. If so,
then the program will "lockup." This is due to the fact
that the data the app needs to access is very large, not
to mention the fact that possibly thousands of other
users might also trying to access the same data.
When I used dial-up in the past to download the updates
it took about 4-5 minutes just to check if any updates
were available. It then took about 10 more minutes to
download the updates. Now since I use broadband, it
usually hangs up for about 10-20 seconds and takes about
another 30 seconds to download the updates.
The two files that make up the upsate are fairly large,
the smallest of the two files when uncompressed is about
1.23 MBs and the other is about 2.6 MBs. Because of
this, downloading such files will take a long time.
Another thing to keep in mind is that if you look at the
amount of memory (Crtl-Alt-delete >Processes > Mem Usage)
that the app is using you will see that when the updater
is run, the memory usage skyrockets, taking up most of
the allocated memory for the app. This causes the
refreshing of the app to slowdown to such an extent that
the app seems to lockup. But it doesn't really lockup,
it only seems as though it does. On my system for
example (using broadband), when I launch MSAS it usually
uses about 12 KBs of RAM, but when I use the updater it
spikes to about 30 KBs of RAM. This means that there's
about a 150% increase in memory usage. If you are using
dial-up this percent increase might even be higher than
what I'm experiencing.
Alan
