5 Replies Latest reply on Dec 16, 2003 8:31 AM by map

    What's the role of generic Intel PXE-2.0 build 082 driver?

    gulite Rookie
      Can this driver be used on any NIC from different vendors just as its name indicates, 'generic'?

      If yes, what do NIC vendors need to do to support this 'generic' driver?

      And is there any document about it?

      regards
      Kevin
        • 1. Re: What's the role of generic Intel PXE-2.0 build 082 driver?
          map Specialist
          Kevin,
          you're right - as the name indicates, the generic Intel PXE driver is supposed to work with all PXE2.0 compatible NICs. Thats why we use it for OSD
          (this is because it talks to the PXE, not to the NICs hardware directly)

          So that is exactly what NIC vendors needs to do: make their cards PXE2.0 compliant; almost 100% you get these days are.

          The specs for PXE should be available on Intel's Website.

          what exactly is the background of your question?

          Martin
          • 2. Re: What's the role of generic Intel PXE-2.0 build 082 driver?
            gulite Rookie
            Thanks a lot for your answer.

            I am a software engineer from a NIC vendor. One of our customers used OSD. If they use our NDIS2 driver, there is no problem to install OS. But When they use the generic UNDI-NDIS driver along with OSD, the installation process is somewhat slow and always hangs at the same place, i.e. copying the Driver.CAB file, u know, it is a big file.

            I can't figure out which part is wrong.

            BTW, Could you Pls explain how OSD determines to use generic UNDI-NDIS driver, according to which part of the NIC?

            Thanks in advance.
            • 3. Re: What's the role of generic Intel PXE-2.0 build 082 driver?
              map Specialist
              Sorry for the delayed answer!

              suggestion: please ask your customer if he uses the latest version of the Intel driver. it seems there was an issue with earlier versions.
              It is available at Intels website.

              your question about how OSD determines which driver to use:
              if you use PXE, it doesn´t try. it will always just use the generic driver.

              if the customer has a very homogenous hardware environment (that is, *only* uses nics with that behaviour) than he could just modify the bootdisk-Image setup.px to always use your NDIS2 driver as a workaround.
              In my experience the generic driver works fine with all kind of NICs; it there was an issue it could usually be fixed by flashing the BIOS.
              But i'll double check the german OSD-Newsgroup at the weekend and post here again if i find anything.
              can you PM me your NICs brand?

              regards,
              Martin Appel
              Team NetSupport

              Thanks a lot for your answer.

              I am a software engineer from a NIC vendor. One of our customers used OSD. If they use our NDIS2 driver, there is no problem to install OS. But When they use the generic UNDI-NDIS driver along with OSD, the installation process is somewhat slow and always hangs at the same place, i.e. copying the Driver.CAB file, u know, it is a big file.

              I can't figure out which part is wrong.

              BTW, Could you Pls explain how OSD determines to use generic UNDI-NDIS driver, according to which part of the NIC?
              e.

              • 4. Re: What's the role of generic Intel PXE-2.0 build 082 driver?
                gulite Rookie
                Thanks for your answer.

                The customer uses the Intel PXE-2.0 build 082 driver. The customer also tested adapters from another vendor. The result is OK.

                regards
                kevin
                • 5. Re: What's the role of generic Intel PXE-2.0 build 082 driver?
                  map Specialist

                  Thanks for your answer.

                  The customer uses the Intel PXE-2.0 build 082 driver. The customer also tested adapters from another vendor. The result is OK.

                  regards
                  kevin


                  Kevin,

                  does the SERVER have a Gigabyte-Card? If so, it might be a config problem at the Servers network card.

                  Martin