Has anyone seen a problem with the Aironet 350 not automatically associating? You have to manually set up a second profile and then switch to the dummy profile apply and then switch back to the correct profile and apply again in order to get the 350 to associate. Once associated there are no further problems. Some hardware details:
Problem resolved once I replaced the 350 with a 340 running firmware ver3.98. It appears that there is a problem with the 350 running firmware 4.25.30 on a Win95 box or a 98 box that has been upgraded (Seems to work fine with a native win98 box).