Dlink has a problem with SP3 changing the contents of wlanapi.dll by Microsoft SP3.
I have been corresponding and talking with Dlink Tech Support.
They don't have a fix yet.
The problem is with a monitoring file that loads in the background at startup.
In my case it was AirGCFE.exe,
In your case it is WZCSLDR2.exe.
You can disable these files from starting at boot and the NIC will still work.
You may not fine your monitoring file in MSCONF, but in Windows Defender, Tools, Software Explorer
you will find the startup files listed with an explanation of what it does. Just disable from
starting there and hope that Dlink come up with a solution soon. Their tech support was unaware of
the SP3 conflict with wireless NICs.
|
| --
| nski
|
|
| "Big Al" wrote:
|
| > normski wrote:
| > > -- Hi can you advise me on this please? Just downloaded & installed service
| > > pack
| > > 3 for windows xp each time i start up a box appears which says
| > > WZCSLDR2exe ENTRY Point not found
| > > The procedure entry point aps Get Ready could not be located in the dynamic
| > > link library Wlanapi dll.
| > >
| > > Thank you
| > > normski
| > >
| > > nski
| > Seems to have something to do with your Dlink wireless. You might
| > have to re-install the drivers, check to make sure you got the latest.
| > I googled both the exe and dll filenames.
| > Is your wireless not working? and are you using Dlink?
| > Hi not using Dlink now i used to but now use Netgear so do you think there may be some old
Dlink files causing the problem?
