OK, the latest is that I appear to have got it working.

I installed 6.5.0 on my laptop (there was no way I was messing with my
beautifully tweaked and setup 6.5.2 on my main PC) and directed my SB3
towards that.

It connected fine, downgraded to FW64 and rebooted.

However - it lost all its wireless settings on reboot (a shock to me)
so I had to input everything again - which would have been easy if I
could remember my wireless password).

So, I inserted a new password into my Access Point (plus all my other
wireless equipment) and the SB3 duly connected to SS v6.5.0 on the
laptop.

When I then stopped slimserver, the 'waking slimserver' message was
back (and not just on a reboot like before).

I then pointed my SB3 back towards my main PC with 6.5.2 on it and
after updating to FW80 (which I've been running for a few days now) it
connected easily.

Guess what... 'Waking Slimserver' seems to have been restored! :)

So, what could have caused this?  Could it have been my upgrade from
6.5.1 to a very particular version of 6.5.2 (with the added bonus of
FW76) which only a few of us seem to have done?

I can't get my head around how taking a particular upgrade path can
influence this seeing as others on FW76/80 have not had the problem and
that SS is not run on the squeezebox but on a remote computer.

Anyway, I appear to have it working.  I'd recommend the technique to
others and thanks to those who suggested it!

Daz

PS The only thing that nearly caught me out in all of this was the fact
that 'l' and 'I' look identical on the squeezebox when inputting
wireless passwords just as they do in the arial font in which I'd
printed it out as a reminder!!!


-- 
dazbarber
------------------------------------------------------------------------
dazbarber's Profile: http://forums.slimdevices.com/member.php?userid=8088
View this thread: http://forums.slimdevices.com/showthread.php?t=33867

_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss

Reply via email to