Proper way to move file into system32 folder?

Installation of XP SP3 overwrote a wireless adapter driver called wlanapi.dll.
I found the old file and drag and dropped it into the system32 folder from C:\ANI\ANIWZCSZ. Now, when the computer starts up there are no notices about missing files but the empty C:\ANI\ANIWZCSZ directory window appears on the screen. How do I correct this problem?

 

Did you see this notice from Microsoft?
http://support.microsoft.com/kb/950720

and did you follow resolution directions by going to your wireless card manufacturer and downloading latest sp3 compatible drivers and software for your wireless adapter?

also see this:
http://www.techsupportforum.com/sec...cs-launcher-windows-absolutely-necessary.html

 

Thank you for the reminders re: Microsoft use of wlanapi.dll name in XP SP3 resulting in overwriting of D-Link wireless device driver of same name. I got the most up-to-date driver I could find online and used a batch file to pull wlanapi.dll out of a servicepackuninstall folder to C:\Program Files\ANI\ANIWZCSZ. Then I dropped the file in the system32 folder. I tried using xcopy to copy the file back to the ANIWZCSZ folder but I got invalid parameters notices and a new folder was made called Program%Files with the wlanapi.dll file inside C:\Program%Files\ANI\ANIWZCSZ.
How do I get the C:\Program Files\ANI\ANIWZCSZ directory window that wlanapi.dll used to be in to close and not open on startup?

 

Hello laserbue,

Why are you just trying to copy and paste over this problem rather than uninstalling the old and reinstalling the new? "Registry" may be a factor and settings needed will not be changed or used on a copy/paste.

I guess I just don't have a full or firm grip on the finite details of the "root" problem and the reasoning behind your choice of the fix. I find it puzzling.

 

reinstall

I think the C:\Program Files\ANI\ANIWZCSZ directory window is opening at startup because I didn't use xcopy to move the D-Link wlanapi.dll file to the system32 folder. That's my best guess. I just want to reverse whatever I did.
W2CSLDR2 is a startup file that seems to be responsible for opening the directory window of the folder wlanapi.dll was in before I dropped it into the system32 folder, but it may also be the wireless device startup file so I don't want to disable it. When I disabled W2CSLDR2 at startup the ANIWZCSZ window stopped opening.

 

Hi again,

So... "the problem" is fixed?

Your main problem is still clear as mud to me, must have something to do with this post sp3 problem and your choice of a fix or work around:
http://kb.cadzow.com.au:15384/Cadzow/details.aspx?ID=1898

In any case, I'll ask again, is this fixed? If not, you may wish to start explanation/description, fresh, from the beginning and supply ALL the details of the problem, from start to current situation, including quoted errors and what you did in an attempt to fix it/them.

Sorry, I am trying my best to fill in the holes. The biggest one, at the moment may be between my own ears.

 

Thank you for continuing to try to understand my problem. The problem with a window showing C:\Program Files\ANI\ANIWZCSZ\ at startup has not been fixed yet.
Originally, the problem was regarding 2 error messages that were appearing and a search on the internet revealed that the problem was (as you have correctly surmised) that a D-Link wireless device used a file that had the same name as a file in the later Windows XP SP3 that overwrote the wireless device file when XP SP3 was installed. I saw the WINDOWS notices you have referred to and several postings regarding the problem. One solution on the internet was to get the old wireless device file from the uninstalled SP2 folders using xcopy, put it into the system32 folder and rename it as wlanapi.dll. I used a batchfile rather than xcopy to get the old file. The batch file created two nested folders in C:\Program Files called ANI and ANIWZCSZ with the old wireless wlanapi.dll file in the ANIWZCSZ folder at C:\Program Files\ANI\ANIWZCSZ\wlanapi.dll. I dragged and dropped wlanapi.dll from C:\Program Files\ANI\ANIWZCSZ into the system32 folder and when I did a restart, the error messages did not appear but the C:\Program Files\ANI\ANIWZCSZ window would be open on the desktop at startup.

A revised driver was also downloaded from D-Link as well and the device was uninstalled and installed again. The device is working fine but that C:\Program Files\ANI\ANIWZCS\ folder window keeps opening up at startup. How do I stop the window from opening at startup?

 

Hi laserblue,

Odd that you copied/extracted the file to *\system32 folder when the directions said to extract this dll to the C:\Program Files\ANI\ANIWZCS2 but if this is botched all together, your wireless will have issues and it should be easy enough to straighten out.

Where is the batch file you ran and what commands were in it?

If you are sure these folders are not needed by your wireless device you can either check for and stop the startup by any of the methods below:

First make sure there is no reference to it in the startupfolder which you can get to via the start button>all programs "startup "

No joy......any of the methods may work:

Do you have "hijackthis" application or a favorite program that you like to run to control your startups?

Barring any batch file complications, it is a run key in the registry that you'll be looking for to either delete or correct. Any of the below methods are safe and easily reversible.

See if Msconfig>startup tab shows anything related to C:\Program Files\ANI\ANIWZCS2 as a startup that you can disable (uncheck)? See:
http://ihacking.wordpress.com/2008/02/12/control-startup-programs-in-windows-xp/

startup control panel:
http://download.cnet.com/Startup-Control-Panel/3000-2094_4-10039330.html

autoruns:
See what programs are configured to startup automatically when your system boots and you login. Autoruns also shows you the full list of Registry and file locations where applications can configure auto-start settings.
http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx

The method below is riskier and will require "caution and precaution ".

prefer the manaual way: (backup registry or export any key before you edit.)
http://windowsxp.mvps.org/Startup.htm