Since my last post on page 19 of his thread on 29 December at 23:31, I have tried on my 13" White MacBook not only everything I had tried before, but in addition DiskWarrior. No change.
Then I took the bull by the horns and restored Snow Leopard from the System Disk.
Tried the Wifi BEFORE doing any system updates - IT DID NOT WORK. Whereas when I did the original installation it had worked up to 10.6.4 inclusive.
Then I updated using the 10.6.6 combo - IT STILL DID NOT WORK.
BUT my wifi still works perfectly on every other machine - even when I play around with the channels (anyway there is no problem of interference here) AND when I use BOOTCAMP and then log out of it and onto the Mac OS X side of the machine - the Airport still continues to work and I can use the wifi until I put the machine to sleep or something else occurs to cut me off. Then I cannot re-connect.
I suppose that the original 10.6.5 did a firmware update as I now have
Software Versions:
Menu Extra: 6.2.1 (621.1)
configd plug-in: 6.2.3 (623.2)
System Profiler: 6.0 (600.9)
Network Preference: 6.2.1 (621.1)
AirPort Utility: 5.5.2 (552.11)
IO80211 Family: 3.1.2 (312)
Interfaces:
en1:
Card Type: AirPort Extreme (0x168C, 0x86)
Firmware Version: Atheros 5424: 2.1.14.5
Locale: ETSI
Country Code: GB
Supported PHY Modes: 802.11 a/b/g
Supported Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140
Status: Not Associated
and I suppose that the re-installation of Snow Leopard would NOT have set the firmware version back to a previous version, which may explain why even going back this far did not correct the problem.
So it looks as if there is a problem of incompatibility between Snow Leopard as such, all versions, and this latest firmware update, as the firmware update has apparently NOT affected the ability of Windows XP Pro SP2 on the Bootcamp side of the machine to connect and maintain connection.
OR in all my other attempts to get this machine on line again I have changed something else unsuspected that is preventing connection.
Any ideas?