Re: Component for new Intel PRO/1000 rev 12 driver

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



I think I figured out 3 of the 4 issues....

(1) The "Characteristics = 0x84" and "BusType = 5" are both set by default
for PnP drivers and can be ignored (thanks KM for an earlier post).

(2) Can't leave machine.ini, keyboard.ini, and msmouse.ini to component
repository because they will conflict with XPe's copy when added to to the
database. Instead copy the new driver .inf to XPe's repository while doing
the import and then remove it or remove them from the component repository
after the .INF is read but before adding into the database.

(3) Since PciIoSpaceNotRequired appeared only in Win2k areas of the new
driver INF, I am going to ignore it.

So, what remains?

According to msdn2.microsoft.com/en-us/aa937905.aspx the line
"Port1FunctionNumber = 0" tells the system how to map the 4 ethernet ports
to the pci function numbers. Since zero is specified, the first ethernet
adapter port maps to pci function zero in XP Pro, the second to pci function
1, etc. In addition "Port1DeviceNumber" could be used instead to map ports
to pci device numbers instead of function number.

So the Port1FunctionNumber entry will probably impact all the reg entries I
see in an XP Pro install via inctrl5. The only way I can get away with
using defaults is if Port1FunctionNumber is the default mapping scheme
between pci and the four ethernet adapter ports -AND- that the default value
of Port1FunctionNumber is zero.

If anyone could confirm this it would be great.

Thanks,

--
JimT

"jimt" <jim_underscore_thalmann_@_avid_dot_com> wrote in message
news:%23KmSM2AaHHA.3272@xxxxxxxxxxxxxxxxxxxxxxx
I am interested in componentizing the new 26Feb07 driver for the Intel
PRO/1000 PT Quad Port Server Adapter, pn EXP19404PT. Since the driver on
the Intel website is newer than AndrewRoy's "Intel PRO/1000 series ethernet
adapters" on xpefiles.com, I would like to componentize the new version.
Has anyone done this for XPe SP2 w/FP2007?

The release notes say that building a "driver disk" is no longer
supported. I installed the new driver "PRO2KXP.exe" on XP Pro with
Inctrl5. Device Manager shows seven files, including the .SYS and (via
PnP ID) .INF files to put into the driver repository. But what about all
the other files that are shown in the Inctrl5 log?

I tried an import of the e1e5132.inf file. Problems are:

- This line: "Characteristics = 0x84 ; NCF_HAS_UI | NCF_PHYSICAL"
caused this error: "cannot handle key "Characteristics". In another NG
post, a value of
0x85 was reported as the default for pNp. So 0x84 is not... Do I need
to add reg
entries for 0x84?

- inf line "Port1FunctionNumber = 0" results in "cannot handle key". No
mention of this
in the inctrl5 log. Ignore it?

- CompDesigner complained "Cannot find included INF File". I copied
machine.inf,
keyboard.inf, and msmouse.inf from the XPe repository to my component
repository.
Error fixed.

- "Cannot find [PciIoSpaceNotRequired] specified in Needs directive in
the current and included INFs." was reported. I searched all .inf files
in the XP Pro Windows\inf dir and
in the XP repository. This does not exist in any of them. How do I
deal with this error?
This symbol appears 4 times in the .INF in sections associated with
Win2k SP1, so
maybe I can ignore this error(?).

Any tips would be very appreciated. Thank you.

--
jimt





.



Relevant Pages

  • Re: Display Driver Installation for testing.
    ... the GenINF program does not create complete .INF files. ... I actually found some old NT4 driver and inf file that I can shamelessly base my test on. ... The home for virtual devices is the system ...
    (microsoft.public.development.device.drivers)
  • Re: Intel 82852 GM + 82801 DB
    ... Thanks I currnetly am tryin to search for the *.inf files and then ill try to ... make the driver compenent that way. ... I get a couple warnings from this. ...
    (microsoft.public.windowsxp.embedded)
  • Re: driver
    ... I thought when you create a Repository all the files in the ... INF, saved it.. ... the driver I need is deployed as an Install ... package instalation and grab them from the temporary folder (then I ...
    (microsoft.public.windowsxp.embedded)
  • Re: Followup Question on PnP INF File
    ... Why use INF files for this? ... Why not just open the serial port from the app ... the consensus seems to be that our driver needs ...
    (microsoft.public.development.device.drivers)
  • Re: FTDI USB Serial Drivers
    ... The DLL accesses the inf for setup ... from the FTDI driver readme: ... Notes on INF files ... particular VID and PID requires access to a registry editor which (unlike ...
    (microsoft.public.windowsce.platbuilder)