DLink GWL-G630 Entry Point Problem - wlanapi.dll

[Duckysan1]

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]

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.

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/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

 

[Duckysan1]

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.

 

[Pavel A.]

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

 

[Barb Bowman]

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...

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

--

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

 

[leyland]

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!

 

[leyland]

On booting up I am shown the WZCSLDR2/WLANAPI.DlL/apsGetReady. I've tride to
remove this no joy. I then discover that there are spyware companies claiming
to be able to remove this, of course for a fee. Do these work ?.
Just what is Windows doing to resolve this problem. Are they working on this
as we speak. Come on Windows you must be aware of this problem, give us an
answer.

 

[R. McCarty]

Not a Windows/Microsoft issue at all. You have a support applet for
a Wireless card that is attempting to start at boot. Either the .Dll is not
found or the registration for it is missing/incorrect.
Several options - either use Windows Native Wireless to control the
device or check your card's vendor website for an updated driver &
support applet.

 

[Richard in AZ]

Actually it is a Microsoft/Windows issue. They rewrote a dll file, that Dlink was using, with the
issue of SP3.
The new dll file is not compatible with the DLink drivers.
However DLink should now have a patch, or new driver, for their card. But seems they don't care
about some older cards.
Going to "msconfig" and turning off the DLink monitoring software stops the nag window and does not
stop the card operation.

| Not a Windows/Microsoft issue at all. You have a support applet for
| a Wireless card that is attempting to start at boot. Either the .Dll is not
| found or the registration for it is missing/incorrect.
| Several options - either use Windows Native Wireless to control the
| device or check your card's vendor website for an updated driver &
| support applet.
|
| | >
| > On booting up I am shown the WZCSLDR2/WLANAPI.DlL/apsGetReady. I've tride
| > to
| > remove this no joy. I then discover that there are spyware companies
| > claiming
| > to be able to remove this, of course for a fee. Do these work ?.
| > Just what is Windows doing to resolve this problem. Are they working on
| > this
| > as we speak. Come on Windows you must be aware of this problem, give us an
| > answer.
| >
|
|

 

[R. McCarty]

Thanks for the additional info, wasn't aware of the circumstances of the
..Dll.

 

[Kelly]

SP3

Beta tester are you? <eg>

--

All the Best and Happy Turkey Day,
Kelly (MS-MVP/DTS&XP)

Taskbar Repair Tool Plus!
http://www.kellys-korner-xp.com/taskbarplus!.htm

 

[leyland]

 

[leyland]

Yes we are all aware of the problem with apsGetReady.
Everybody has their own solution, blogging does not solve it.
Simple question, what is MICROSOFT doing to resolve this. Could MICROSOFT
make an official statement. If WZCSLDR2i s not within their remit then we can
seek the answer elsewhere.