Prev: Clicking sound in IE
Next: Can't play WAV Files
From: Alb�do on 22 Jul 2010 08:18
I have tried to reinstall an983.sys manually through the device driver (?)
interface, but though the file appears in three different locations:
- C:\WINDOWS\ServicePackFiles
- C:\WINDOWS\system32\dllcache
- C:\WINDOWS\system32\drivers
the first two failed (the driver was not found); as for the third, the "OK"
button remained greyed.
--
a.


From: Alb�do on 22 Jul 2010 08:29
I have downloaded the zip file and extracted the .sys (which appears to be
slightly different from the one I got: 38 Ko instead of 36, and dated 08/11/2002
00:00 instead of 28/08/2002 23:59--don't these people work late at night ;-) to
the Desktop, but when I try to install it through the device maganer (?)
interface, I get a greyd "OK" button. Should I just replace the file manually
(under safe mode)?
--
a.


From: Paul on 22 Jul 2010 09:38
Alb�do wrote:
> I have downloaded the zip file and extracted the .sys (which appears to be
> slightly different from the one I got: 38 Ko instead of 36, and dated 08/11/2002
> 00:00 instead of 28/08/2002 23:59--don't these people work late at night ;-) to
> the Desktop, but when I try to install it through the device maganer (?)
> interface, I get a greyd "OK" button. Should I just replace the file manually
> (under safe mode)?

FTS_ADMtekFastEthernetAdapterDriver__1000050.zip

Unzip the downloaded file.

Navigate to AN983B_XP_220.

You should see three files.

AN983.SYS
NETAN983.CAT
NETAN983.INF

Right-click the INF file and select "Install".

Whether the driver will install or not, depends on matching a line in the INF
file. For example, this line is a particular instance of network card -

%AN983.DeviceDesc% = AN983.ndi, PCI\VEN_1317&DEV_0985&SUBSYS_100C1734

The SUBSYS entry, specifies a particular brand of network card, with the
ADMTek chip on it. If the entry was like the following, it would be for *any*
network card made with the ADMTek chip on it.

PCI\VEN_1317&DEV_0985

So when the SUBSYS field is missing, the driver matches more cards. This
gives the driver writer, finer control of which cards the driver will
install on.

I don't know what the SUBSYS value of your card is. I could probably
find it if I used Everest or a similar utility that identifies hardware.
If you edit the INF file, it may be possible to force the driver to
install.

*******

Another thing to keep in mind, is your options if this installation
doesn't work right. If you go to "Device Manager", and navigate to
that network card, then use the "Driver" tab, there is a
"Roll Back Driver" button. That will undo one attempt at driver
installation. It will not roll back an infinite number of levels,
only the one level.

A second option, would be to set a "System Restore" point, before
attempting to install the drive. You can then restore that
system restore point, if the driver change did not go well.
System Restore allows more different points in time, than the
single level of rollback supported by the "Roll Back Driver" button.

Good luck,
Paul
From: Alb�do on 24 Jul 2010 06:25
....Hi again, Paul.
*Many* thanks for the detailed explanations.
I'll be on holidays in a few days and in the meantime I need to backup my old
hard disk so I'll postpone the maneuver you mention until I'm back and can give
it some time.
Then I'll be back and let you know how it went!
Cheers from France.
--
a.


First  |  Prev  | 
Pages: 1 2
Prev: Clicking sound in IE
Next: Can't play WAV Files