Re: Airport Extreme card and MoreSCF
Re: Airport Extreme card and MoreSCF
- Subject: Re: Airport Extreme card and MoreSCF
- From: Smith Kennedy <email@hidden>
- Date: Wed, 28 Jan 2004 13:06:41 -0700
Greetings,
I was also seeing that problem, and this seems to have fixed that
particular issue, but I am also having problems with turning on the
wireless card programmatically. Is this also a known issue on 10.3?
It would be nice if the schema/whatever of the keys for wireless stuff
didn't change every time Mac OS X rolls from 10.1 to 10.2 to 10.3.
This makes it hard for us to write code and have it just work. The
changing options between Cheetah, Jaguar, and Panther have been the
cause of continually having to revisit code that once worked. When
will this settle down a bit?
Smith
On Jan 27, 2004, at 11:14 AM, Dave Camp wrote:
On Jan 27, 2004, at 2:32 AM, Quinn wrote:
At 17:55 -0800 26/1/04, Dave Camp wrote:
Any thoughts on why the Airport Extreme names not "correct" in SCF
for locations I create?
This is a bug in MoreSCF. Actually, it's a bug in MoreSCF code that
only exists because of limitations in the OS. To wit, the OS
provides no simple way for third party developers to get the user
visible name for a network port <rdar://problem/2851696>. Thus,
every time we introduce a new port type (for example, AirPort Extreme
vs AirPort), we revise the code in the Network preferences panel to
produce the correct name and every developer has to do the same. This
is very annoying and we're hoping to rectify it (by adding a "what's
the user visble name for this port" API) in the next major release of
Mac OS X.
At some point I'll revise MoreSCF to cover the AirPort Extreme case
<rdar://problem/3540864>. Until that time, you must fix the problem
in your copy of the code. I believe that the correct fix is to
replace line 502 of "MoreSCFPortScanner.c"...
&& CFEqualString(tmpStr, CFSTR("AirPortDriver"))) {
... with...
&& CFStringHasPrefix(tmpStr, CFSTR("AirPort"))) {
I can't test this today because I don't have easy access to an
AirPort Extreme card. Let me know how it goes.
That does appear to fix the problem, at least on a single run on a
machine with the old card and a machine with the new card.
I've also logged bug <rdar://problem/3541060> asking for some
additional properties indicating if the interface is wired or
wireless.
Thanks,
Dave
---
It is dark; you are likely to be eaten by a grue. -Zork
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.