Re: Constant New Port message's for MoreSCF
Re: Constant New Port message's for MoreSCF
- Subject: Re: Constant New Port message's for MoreSCF
- From: Juan Ignacio Leon <email@hidden>
- Date: Thu, 20 Oct 2005 22:24:35 -0500
On 10/20/05, Peter Sichel <email@hidden> wrote:
> On 10/20/05, Mark Thomas wrote:
>
> >Hi,
> > I thought I'd update everybody on my dealing with Airport Extreme and
> >MoreSCF is that I have found a fix, but updating the code in the Port
> >scanner code, not to just look for for "AirPortDriver", but to look for an
> >IOClass which has the first 7 characters of "Airport", as I have seen a few
> >variations of this name AirportXXXXX but that seems to do the trick quite
> >nicely.
> >
> > I would be curious if anybody has any issues with the above technique or
> >did it another way, but that how I've got the code working.
> >
> >Thanks
> >Mark.
>
> Specifically, in MoreSCFPortScanner.c, change this:
>
> && CFEqualString(tmpStr, CFSTR("AirPortDriver"))) {
>
> to this:
>
> && CFStringHasPrefix(tmpStr, CFSTR("AirPort"))) {
>
> It looks reasonable to me.
>
> - Peter
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Macnetworkprog mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
Fantastic! Thanks for figuring out and posting such a simple patch.
I'll incorporate this into my code.
Along the same lines, does anyone know if the new USB modem on new
G5's and the DevKit Macs' modems get recognized by MoreSCF or will it
require some similar patching?
I want to keep my release functional as long as possible.
JI
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden