Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.hardware,microsoft.public.windowsxp.network_web (
More info?)
How to get the Hardware ID of a NIC
1.. Close all open instances of Device Manager.
2.. Open a command prompt.
3.. In the command prompt type set devmgr_show_details=1
4.. In the command prompt type devmgmt.msc to go to the Device Manager.
5.. Click the plus sign next to Network Adapters so that you can see the
NIC in question.
6.. Double click the name of the NIC in question.
7.. There should be a Details tab, go to it.
8.. In the Details tab select Hardware Ids from the drop down menu.
9.. Highlight the top line (this is the Hardware ID) and copy it (Ctrl-C).
10.. Paste this into a mail and send it back to me.
if you have a driver (.sys file) and corresponding inf (.inf file) you can
search for the hardware ID in the inf you suspect will work- if it is there,
you have the right driver/inf
not necessarily the most current one but one that should work
Alternately you can find the company of manufacture at
http://www.pcisig.com/membership/vid_search/
number from details tab= PCI\VEN_some#letters&DEV_#&subsys_#
look up the "some#letters" in hex at the above link click search & you can
confirm the company of manufacture
Hope this helps
--
John McVea [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Hermes" <hermes@messenger.net> wrote in message
news
an.2004.05.11.04.32.53.851182@BWAHAHAHAHAHA!!!...
> Before the MVP (M$ Victim Poster) Hermes responded, Bruce Chambers typed:
>
> > Greetings --
> >
> > What's the FCC number on it? Cards are usually easier to track
> > down using the FCC number.
> >
> > Bruce Chambers
> >
> > --
> > Help us help you:
> >
http://dts-l.org/goodpost.htm
> >
http://www.catb.org/~esr/faqs/smart-questions.html
> >
> >
> > You can have peace. Or you can have freedom. Don't ever count on
> > having both at once. -- RAH
> >
> >
> > "hermes" <hermes@messenger.net> wrote in message
> > news:ObfAyNtNEHA.3016@tk2msftngp13.phx.gbl...
> >> and where can I find drivers for it?
> >>
> >> It has a realtek chipset (not sure which one), I think it is a
> >> generic oem
> >> as there is absolutely no info on it except the following:
> >> Serial number: AHN6303023707
> >> Part Number: 18-0B-F200-B100
> >>
> >> The following is all I can turn up on it after searching the
> >> internet (web
> >> and usenet):
> >>
> >>
http://www.google.com/search?sourceid=navclient&ie=UTF-8&oe=UTF-8&q=18%2D0B%
> >> 2DF200%2DB100
> >>
> >> I apologize for posting slightly OT and appreciate any assistance.
> >>
> >> --
> >> hermes
> >> DRM sux! Treacherous Computing kills our virtual civil liberties!
> >>
http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html
> >>
> >> Windows XP crashed.
> >> I am the Blue Screen of Death.
> >> No one hears your screams.
> >>
> >> Yesterday it worked.
> >> Today it is not working.
> >> Windows is like that.
> >>
> >>
>
> Thanks for the response Bruce. I tried the FCC # that was on the card,
> but it didn't bring up anything. Dispite our occasional "discussions" in
> these groups, I appreciate and respect your willingness to help.
>
> --
> hermes
> DRM sux! Treacherous Computing kills our virtual civil liberties!
>
http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html
>
> Windows XP crashed.
> I am the Blue Screen of Death.
> No one hears your screams.
>
> Yesterday it worked.
> Today it is not working.
> Windows is like that.
>