Originally posted by: Amused
Originally posted by: Soopaced
that is actually my exact problem of why my bootup is so slow..i disabled the wzc ...once i enabled it..my boot up is now decent...but too bad i have a flakey connection again..going to dl the new update to access connections that just came out and see if that helps...it would be a pain in the ass if i had to disable wzc every time..anyone come up a solution to the intel wireless problem..thanks
UPDATE:
i just installed the newest access connections released 4-7-04...enabled wzc...i did not remove the intel proset wireless 7.2.0 i previously installed ..and now i have a faster boot up and a stable connection without disabling wzc...the only problem i saw was that it seemed like i had two intel prosets running in my startup box..the 7.2.0 i had and i guess the one that comes with access connection..but i just exited the 7.2.0 one and it doesnt show up in my startup even though its running..im too afraid to remove it...in case that is the reason why my connection is stable...thanks for all the help...if anyone just dled the newest access connections and have a stable connection who didnt before without the intel proset 7.2.0 pls let me know..thanks
I have that version. Although it does not drop the connection with the wireless AP, WZC STILL causes huge pings every minute or so for five seconds and sometimes a few lost packets. Disabling WZC after boot stops this.
This is both IBM's and Window's fault. WZC is crappy, and IBM's drivers rely on WZC to boot. The pings are caused by WZC regularly checking for new APs and there is no way to tell it not to, other than shutting it down after boot.
So I made a shortcut on my desktop that goes directly to the admin services. It makes shutting down WZC fairly painless after booting.
With any other driver set, one would simply download the W2K drivers for the wireless client and turn off WZC completely. However, IBM's drivers are universal for XP and W2K, so we're screwed. :|