yikes.  

I can't easily reproduce this, BUT I did notice a related bug which I filed as bug 3748

Richard, is it possible a code you were using for testing made it into the firmware image and gets set sometimes?

For any users that stumble across this bug listing and are looking for a workaround, you can erase the code by doing a factory reset (holding the "+" button on your remote as you reconnect the power).  As I mention in the other bug, this workaround will lock your Squeezebox.  However, if you unplug and replug your power again, it seems that the reset has occurred correctly, and the code will be cleared.

Jim, did you do anything unusual with your SB2 beforehand that might help me try to reproduce this bug?

> Richard, is it possible a code you were using for testing made it into the
> firmware image and gets set sometimes?

And if that's the case, please divulge the code so that I don't have to do a factory reset and reenter that bugger of a 64 character random WPA-PSK password. :-)

> did you do anything unusual with your SB2 beforehand that might help me
> try to reproduce this bug?

I don't think so.  After an SVN update of the server I'd been having difficulty connecting my two Squeezeboxe 2s to the server, so I believe before the fw upgrade it was probably sitting unconnected with "Connecting to SlimServer..." on the screen.  I rebooted the server (Windows machine) and then the firmware was upgraded.  Upon the SB2 rebooting, it went back to "Connecting to SlimServer..." and that's when it wouldn't let me into the setup due to the lock code having beeng set.  A couple more reboots of the server and it's now connected again to SlimServer.

I did not include any lock codes in the firmware image when I was testing, this must be due to random values in the nvram that is now used for the lock code.

Jim so the squeezebox with the lock code is now connected to the server? If you don't need to change the settings, wait until the next firmware update. I will probably disable all locks for the first upgrade to fw59 (or which ever firmware is next released).

I had the same problem - after the fw58 upgrade the setup code was set to an unknown value. 

A factory reset got past this issue but following the upgrade I can't connect to SlimServer over wireless (wired is fine).

It gets stuck at the "Connecting to SlimServer..." point and never comes back. My WAP is a LinkSys WRT54G v4 with v1.0.08 firmware.

I've gone back to the older firmware for now.

Bug 3752 covers the issue where the Squeezebox could not connect to the Slimserver.

This bug is fixed in firmware 59. It is currently undergoing internal testing. You will be notified again when it is made part of a nightly release. 

Please note a side effect of fixing this bug is a full factory reset if you downgrade from firmware 59 to an earlier firmware (but not when you upgrade to this firmware).

This fix is now available in the 6.5 nightlies ONLY.  FW59 will not work with Slimserver versions 6.3.x and below.

Please give it a try and let us know how it goes.

I can confirm that the upgrade to fw59 cleared the random code that was set.  Thanks.  Testing whether or not the code gets set in the first place is going to have to be left to someone else.