SP3 and Dlink Wireless NIC problem (partially solved)

I installed SP3 on a XP Pro computer using a Dlink DWL-G510B wireless NIC.
After the installation I got the following error message with every boot.

"AirGCFG.exe - Entry Point Not Found
the procedure entry point apsSearchInterface could not be located in the dynamic link library
wlanapi.dll"

It seems SP3 installs a new version wlanapi.dll that is not compatible with AirGCFG.exe.
The NIC works and wireless connects, just have the boot error message.
I tried to get an older version of wlanapi.dll, but could not find one in either the driver files
from Dlink or on the web.

I emailed Dlink, but no response yet.

Did find that AirGCFG.exe is the Dlink NIC monitoring program that loads as a TSR (but does not show
in MSCONFIG).
Windows Defender (Software Explorer) showed it and allowed me to disable it as a TSR.
Now I do not get the boot error message and the NIC still works.

Will post back if I get a reply from Dlink.

RoseMarie
Thu Jul 03 23:56:01 PDT 2008

I also have got the same error and wouls appreciate hearing what to do as my
reseach pulled up more problems than remedies!
--
Rose@NZ


"Richard in AZ" wrote:

> I installed SP3 on a XP Pro computer using a Dlink DWL-G510B wireless NIC.
> After the installation I got the following error message with every boot.
>
> "AirGCFG.exe - Entry Point Not Found
> the procedure entry point apsSearchInterface could not be located in the dynamic link library
> wlanapi.dll"
>
> It seems SP3 installs a new version wlanapi.dll that is not compatible with AirGCFG.exe.
> The NIC works and wireless connects, just have the boot error message.
> I tried to get an older version of wlanapi.dll, but could not find one in either the driver files
> from Dlink or on the web.
>
> I emailed Dlink, but no response yet.
>
> Did find that AirGCFG.exe is the Dlink NIC monitoring program that loads as a TSR (but does not show
> in MSCONFIG).
> Windows Defender (Software Explorer) showed it and allowed me to disable it as a TSR.
> Now I do not get the boot error message and the NIC still works.
>
> Will post back if I get a reply from Dlink.
>
>
>

Richard
Fri Jul 04 06:36:27 PDT 2008

DLink has no intention of fixing this problem. However, disabling
AirGCFG.exe as a TSR eliminated the error message and the NIC works just
fine.
Use a program like Windows Defender to disable AirGCFG from starting up on
boot and you should be able to continue using your wireless Network
Interface Card.

"Rose-Marie" <RoseMarie@discussions.microsoft.com> wrote in message
news:F0A8A1FB-36F9-4A1C-86CB-18B69E2243CC@microsoft.com...
>I also have got the same error and wouls appreciate hearing what to do as
>my
> reseach pulled up more problems than remedies!
> --
> Rose@NZ
>
>
> "Richard in AZ" wrote:
>
>> I installed SP3 on a XP Pro computer using a Dlink DWL-G510B wireless
>> NIC.
>> After the installation I got the following error message with every boot.
>>
>> "AirGCFG.exe - Entry Point Not Found
>> the procedure entry point apsSearchInterface could not be located in the
>> dynamic link library
>> wlanapi.dll"
>>
>> It seems SP3 installs a new version wlanapi.dll that is not compatible
>> with AirGCFG.exe.
>> The NIC works and wireless connects, just have the boot error message.
>> I tried to get an older version of wlanapi.dll, but could not find one in
>> either the driver files
>> from Dlink or on the web.
>>
>> I emailed Dlink, but no response yet.
>>
>> Did find that AirGCFG.exe is the Dlink NIC monitoring program that loads
>> as a TSR (but does not show
>> in MSCONFIG).
>> Windows Defender (Software Explorer) showed it and allowed me to disable
>> it as a TSR.
>> Now I do not get the boot error message and the NIC still works.
>>
>> Will post back if I get a reply from Dlink.
>>
>>
>>