marwoodevents wrote:
William,
Assuming that you are an Apple engineer, this is really not the way, from a PR point of view, to deal with an issue like this.
If you re-read the AD Terms of Use, you'll see that Apple Employees identify themselves as such.
I'm just a user like you who spends his own time trying to help fellow Mac users with their issues.
However I also have been in the industry for almost three decades now, so I know a lot more about debugging, diagnosis and difficult technical issues than you might think.
I realize how frustrating it is when you're having an issue - I've been there myself - but I also know that since I have no issues with the machines I use nor do hundreds of my co-workers who've also upgraded to Lion and use Wi-Fi daily at work, home and in coffee shops and hotels, there's something unique about your systems that is exacerbating the issue, which is why I've said all along I hope AppleCare is collecting data to be able to track this down and root cause it and direct the appropriate party to fix the issue. That may be Apple - if it's a Mac OS X bug - or a third party if it turns out it's a firmware bug on the part of a router or chipset vendor.
A product isn't "clearly defective" unless the issue is root caused to something you did; stating that Snow Leopard or any other device works isn't sufficient to point the finger at Lion, but at present we simply don't know.