Ryland wrote:
can we lay this one to rest please it's beggining to make my brain melt in exasperation.
Right back at you, but at the same time I can't let your accusations go unanswered.
If it's true that apple introduced a new revision of the draft 'n' standard then they are the only people in the world who know about it, including the people who write the airport extreme base station software/firmware.
Not at all. It all depends on whether any changes in implementation between drafts requires corresponding changes in router firmware as say Apple has implemented the 802.11n draft spec in their hardware.
That's the problem with implementing a
draft spec; it's always going to be a moving target.
Note also that any speculation about
which draft of the draft spec is implemented has no bearing on 802.11b/g mode, only 802.11
n.
If you and others you know haven't seen any problems then good for you make the most of it, it doesn't mean that there isn't a significant problem. You've used your laptop in many places that just means there's no problem with
your laptop. If you used mine in all those places then you'd have given up by now.
I never said there wasn't an issue here, I've said it's not necessarily Apple's and there's no data that it is, definitively,
their fault.
I've also said if it works for you to go back to 10.5.1 or even, worst case scenario, 10.4 Tiger, you should do so.
If it's a recent hardware purchase and you can return your purchase without taking a financial loss, you should also do that, the same as with any other product one would purchase that doesn't work as one expects when they get it home.
But if it
does turn out to be Apple's fault, they will get the bug resolved as soon as they can.
At least we both agree that we don't know what the problem is/ but it is specific to certain laptops and leopard revisions. So regardless of whether due to a one in a million chance it's not there fault it's still going to appear to be. So if they did something they should have been able to undo it by now.
That's just it; if it were trivial to reproduce and/or if the bug were trivial to fix and/or test, they would have.
They have
not.
If going back to Tiger fixes it, then back to leopard brakes it again then the blame
is going to land on them. especially with all apple equipment. and especially when you take into account all the bugs in Time machine, Apple TV,iTtunes, the Leopard Firewall,Internet connection sharing (leopard). The leopard installation etc etc etc
Human nature is of course that people will blame Leopard, and there's nothing anyone - you, I or Apple - can do about that. The better question is whether the blame is deserved.
since November their slogan 'It just works (for the most part)' has changed to 'It just doesn't work (at all)' for me. This is
exactly why i f*cked it off with Micro$oft and spent a year of my time re learning and migrating all my stuff, only to be confronted with this laughably poor OS
Alas, I realize that's the case for the people here, but it simply is
not for most Leopard users at large.
From past experience I've seen what occurs when Apple inadvertently breaks functionality of something for even 10% of users and it gets a
lot more press from the trades than this issue has received.
Little comfort, I realize.
I feel a bit lost now and will stay with Tiger having finished the task of rebuilding all my machines with Tiger. I will now have to stay with it for 2008 and probably longer until my machines don't meet the requirements of the software i use and they are too slow to use. Then I'll seriously have to consider Linux or heaven forbid Vista, to replace all my macs. If there is still no viable mac alternative.
That is also why we have a computing marketplace.
Once again, I understand how frustrating the issue is, and I'm sure Apple engineering shares your frustration. All engineers hate bugs, especially those that are near impossible to reproduce under controlled conditions, as this issue shows every sign of being.
I'm not going to speculate, but from past experience I know Apple has probably "captured" more than one notebook and base station exhibiting the issue in order to try to reproduce the issue in-house, though I've no idea if they've been able to do so once the units were received.
But as I said, it's ridiculous to keep banging your head against the wall on an issue, and as such if you have a workaround available it's best to apply it until you see mention of a future software update that may fix your particular issue.
I've got one particular issue that Apple
did break with Leopard, and I'm awaiting a fix, but it affects so few people it's much lower on the bug fix food chain than
this issue is. I know Apple will fix it
eventually, but until then if I want that functionality I have to either find an alternative solution or drop back to Tiger.
Since Leopard's features are of greater import to me, I, unfortunately, have to do without. 😟
