DLink GWL-G630 Entry Point Problem - wlanapi.dll

Since upgrading my Acer laptop (Travelmate 2300) to XP SP3, I cannot use the
Dlink utility. I receive the following error:

'The procedure entry point apsGetInterfaceCount could not be located in the
dynamic link library wlanapi.dll'
I have removed and re-installed the drivers/software, but no improvement.
Web search suggests compatibility problem with Dlink driver/dll.
Whilst I still have wireless connectivity, the Dlink utilities do not work.
It seems this is an SP3 issue - other users report the issue is resolved if
they revert back to SP2.
There must be a better resolution!

either use Windows native WZC features to manage the wireless
(uninstall the utility and keep the wireless) or contact D-Link
support/search their downloads for a fixed version.

On Tue, 6 May 2008 02:21:01 -0700, Duckysan1
<(E-Mail Removed)> wrote:

>Since upgrading my Acer laptop (Travelmate 2300) to XP SP3, I cannot use the
>Dlink utility. I receive the following error:
>
>'The procedure entry point apsGetInterfaceCount could not be located in the
>dynamic link library wlanapi.dll'
> I have removed and re-installed the drivers/software, but no improvement.
>Web search suggests compatibility problem with Dlink driver/dll.
>Whilst I still have wireless connectivity, the Dlink utilities do not work.
>It seems this is an SP3 issue - other users report the issue is resolved if
>they revert back to SP2.
>There must be a better resolution!
--

Barb Bowman
MS-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

Thanks for the comments.
It seems XPSP3 adds a new version of wlanapi.dll that conflicts and replaces
the Dlink DLL. I have written to Dlink, but am not holding my breath. The
following appears on the 'Tech ARP' site:

"Windows XP SP3 introduces a new .dll file that is named Wlanapi.dll.
Certain device driver installations for some third-party wireless network
adapters also install a Wlanapi.dll which will be replaced by SP3 resulting
in errors.

This error message will appear during every restart after you install
Windows XP Service Pack 3 : "The procedure entry point apsSearchInterface
could not be located in the dynamic link library wlanapi.dll"

Impact : Low – Obtaining updated drivers for the WLAN device resolves this
issue
KB Content : KB 950720"

I'll check it out.

"Barb Bowman" wrote:

> either use Windows native WZC features to manage the wireless
> (uninstall the utility and keep the wireless) or contact D-Link
> support/search their downloads for a fixed version.
>
>

Wlanapi.dll is part of the new wireless API introduced quite long
ago in KB918997, and now integrated into SP3.

The Dlink package could include some other version of this dll,
because the Microsoft's wlanapi.dll does not have export
function named "apsSearchInterface".
IMHO Dlink should work with MS to resolve this issue.

Regards,
--PA


"Duckysan1" <(E-Mail Removed)> wrote in message
news:EC4E9B6F-7CDB-4631-9E79-(E-Mail Removed)...
> Thanks for the comments.
> It seems XPSP3 adds a new version of wlanapi.dll that conflicts and
> replaces
> the Dlink DLL. I have written to Dlink, but am not holding my breath.
> The
> following appears on the 'Tech ARP' site:
>
> "Windows XP SP3 introduces a new .dll file that is named Wlanapi.dll.
> Certain device driver installations for some third-party wireless network
> adapters also install a Wlanapi.dll which will be replaced by SP3
> resulting
> in errors.
>
> This error message will appear during every restart after you install
> Windows XP Service Pack 3 : "The procedure entry point apsSearchInterface
> could not be located in the dynamic link library wlanapi.dll"
>
> Impact : Low â?" Obtaining updated drivers for the WLAN device resolves
> this
> issue
> KB Content : KB 950720"
>
> I'll check it out.
>
> "Barb Bowman" wrote:
>
>> either use Windows native WZC features to manage the wireless
>> (uninstall the utility and keep the wireless) or contact D-Link
>> support/search their downloads for a fixed version.
>>
>>

It isn't just D-Link, that utility is supplied by the wireless
chipset manufacturer and customized by multiple folks using that
chipset. When they get bits from the source...

On Wed, 7 May 2008 00:50:48 +0300, "Pavel A."
<(E-Mail Removed)> wrote:

>Wlanapi.dll is part of the new wireless API introduced quite long
>ago in KB918997, and now integrated into SP3.
>
>The Dlink package could include some other version of this dll,
>because the Microsoft's wlanapi.dll does not have export
>function named "apsSearchInterface".
>IMHO Dlink should work with MS to resolve this issue.
>
>Regards,
>--PA
>
>
>"Duckysan1" <(E-Mail Removed)> wrote in message
>news:EC4E9B6F-7CDB-4631-9E79-(E-Mail Removed)...
>> Thanks for the comments.
>> It seems XPSP3 adds a new version of wlanapi.dll that conflicts and
>> replaces
>> the Dlink DLL. I have written to Dlink, but am not holding my breath.
>> The
>> following appears on the 'Tech ARP' site:
>>
>> "Windows XP SP3 introduces a new .dll file that is named Wlanapi.dll.
>> Certain device driver installations for some third-party wireless network
>> adapters also install a Wlanapi.dll which will be replaced by SP3
>> resulting
>> in errors.
>>
>> This error message will appear during every restart after you install
>> Windows XP Service Pack 3 : "The procedure entry point apsSearchInterface
>> could not be located in the dynamic link library wlanapi.dll"
>>
>> Impact : Low â?" Obtaining updated drivers for the WLAN device resolves
>> this
>> issue
>> KB Content : KB 950720"
>>
>> I'll check it out.
>>
>> "Barb Bowman" wrote:
>>
>>> either use Windows native WZC features to manage the wireless
>>> (uninstall the utility and keep the wireless) or contact D-Link
>>> support/search their downloads for a fixed version.
>>>
>>>
--

Barb Bowman
MS-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

The solution is much more simpler and is reported here
http://kb.cadzow.com.au:15384/Cadzow...s.aspx?ID=1898

The solution is here
http://kb.cadzow.com.au:15384/Cadzow...s.aspx?ID=1898

The D-Link AirPlus Utility does not work with Windows XP Service Pack 3. Upon loading, it displays: “AirGCFG.exe - Entry Point Not Found. The procedure enry point apsGetInterfaceCount could not be located in the dynamic link library wlanapi.dll.”.
A workaround is to use the pre-SP3 version of wlanapi.dll and place it in the appropriate directories. Upon loading, this version of the file will be used instead of the version in the System32 directory.

xcopy %Windir%\$NtServicePackUninstall$\wlanapi.dll "%ProgramFiles%\D-Link\AirPlus G"
xcopy %Windir%\$NtServicePackUninstall$\wlanapi.dll "%ProgramFiles%\ANI\ANIWZCS2"

"ciccio" wrote in message
news:(E-Mail Removed) m...
> The solution is here
> http://kb.cadzow.com.au:15384/Cadzow...s.aspx?ID=1898
>
> The D-Link AirPlus Utility does not work with Windows XP Service Pack 3.
> Upon loading, it displays: "AirGCFG.exe - Entry Point Not Found. The
> procedure enry point apsGetInterfaceCount could not be located in the
> dynamic link library wlanapi.dll.".
> A workaround is to use the pre-SP3 version of wlanapi.dll and place it in
> the appropriate directories. Upon loading, this version of the file will
> be used instead of the version in the System32 directory.
>
> xcopy %Windir%\$NtServicePackUninstall$\wlanapi.dll
> "%ProgramFiles%\D-Link\AirPlus G"
> xcopy %Windir%\$NtServicePackUninstall$\wlanapi.dll
> "%ProgramFiles%\ANI\ANIWZCS2"
>

Again, the "pre-SP3 version" makes no sense. This DLL conflict can occur
even on SP2 with KB KB918997, so whoever maintains AirGCFG.exe is
going to rename their DLL, or, at least, install it into their app dir
instead of system32.

Regards,
--PA

can you please post the exact steps to fix this? I need help, thanks!

"ciccio" wrote:

> The solution is here
> http://kb.cadzow.com.au:15384/Cadzow...s.aspx?ID=1898
>
> The D-Link AirPlus Utility does not work with Windows XP Service Pack 3. Upon loading, it displays: “AirGCFG.exe - Entry Point Not Found. The procedure enry point apsGetInterfaceCount could not be located in the dynamic link library wlanapi.dll.�.
> A workaround is to use the pre-SP3 version of wlanapi.dll and place it in the appropriate directories. Upon loading, this version of the file will be used instead of the version in the System32 directory.
>
> xcopy %Windir%\$NtServicePackUninstall$\wlanapi.dll "%ProgramFiles%\D-Link\AirPlus G"
> xcopy %Windir%\$NtServicePackUninstall$\wlanapi.dll "%ProgramFiles%\ANI\ANIWZCS2"
>
>
>
>

Unfortunately for my DI-624 did not work.

"ciccio" wrote:

> The solution is here
> http://kb.cadzow.com.au:15384/Cadzow...s.aspx?ID=1898
>
> The D-Link AirPlus Utility does not work with Windows XP Service Pack 3. Upon loading, it displays: “AirGCFG.exe - Entry Point Not Found. The procedure enry point apsGetInterfaceCount could not be located in the dynamic link library wlanapi.dll.�.
> A workaround is to use the pre-SP3 version of wlanapi.dll and place it in the appropriate directories. Upon loading, this version of the file will be used instead of the version in the System32 directory.
>
> xcopy %Windir%\$NtServicePackUninstall$\wlanapi.dll "%ProgramFiles%\D-Link\AirPlus G"
> xcopy %Windir%\$NtServicePackUninstall$\wlanapi.dll "%ProgramFiles%\ANI\ANIWZCS2"
>
>
>
>