Re: RIS & Network adapters

Thanks for the reply back! I was away Friday but I will check this out ASAP
"WOLFF" <Need@FREEbsd> wrote in message news:e28vJOOPDHA.3700@tk2msftngp13.phx.gbl...

here it is
http://support.microsoft.com/defaul...ben-us%3b315074

"WOLFF" <Need@FREEbsd> wrote in message news:OoxAyJOPDHA.1584@TK2MSFTNGP11.phx.gbl...
> Hi Joe,
> Your missing a MS patch, Q314074, or something
> vary close to that Q number, it can only be D/L'd after calling MS support,
> but it's a freebe or you can get it from someone you know !
> Let me go look for this Q
> "Joe" <none@aol.com> wrote in message
> news:#CZQNPBPDHA.3192@tk2msftngp13.phx.gbl...
> >
> >
> > I setup or RIS with a few different images, however I'm having some
> issues
> > with one IBM laptop image. I sent the image up with RISPREP. I can see the
> > Client Installation Wizard then when I tried to pull it down via the pxe,
> I
> > see the others images but then I get 'The operating system image you
> > selected does not contain the necessary drivers for your network adapter'.
> I
> > did a search on the Internet and I tried to add the IMB Nic drivers but
> I'm
> > not sure if I' doing it correctly. I did the following:
> >
> > 1. On the RIS server, copy the OEM-supplied .inf and .sys file for
> the
> > network adapter to the RemoteInstall\Setup\Language\Images\Dir_name\i386
> > folder. This allows Setup to use the driver during the Text-mode portion
> of
> > the installation.
> > 2. At the same level as the I386 folder on the RIS image, create a
> > $oem$ folder with the following structure:
> > \$oem$\$1\Drivers\Nic (is this correct?)
> > (I placed the driver in \$oem$\$1\Drivers\Nic\Win2K\ehternet )
> > 3. Copy the OEM-supplied driver files to this folder. Note the
> folder
> > in which the .inf file looks for its drivers. Some manufacturers place the
> > .inf file in a folder and copy the driver files from a subfolder. If this
> is
> > the case, create the same folder structure below the one you created in
> this
> > step.
> >
> > NOTE: If the RIS image was created with RIPREP, you must perform these
> steps
> > on both the RIPREP image and the RISETUP image that corresponds to the
> > RIPREP image. (what do they mean by this)
> >
> >
> > 4. Make the following changes to the .sif file to be used for this
> > image installation:
> > [Unattended]
> > OemPreinstall = yes
> >
> > OemPnpDriversPath = \Drivers\Nic
> > (I changed this to \Drivers\Nic\Win2K\ehternet,, is this correct)
> > 5. Stop and restart the BINL service on the RIS server. Type the
> > following lines at the command prompt, pressing ENTER after each command:
> > net stop binlsvc
> > net start binlsvc
> > Do I actually create a folder called $oem$, any help would be greatly
> > appreciated
> >
> >
>
>

I slipstreamed SP4 into the RIS and the copied the driver & edited the sif file, it's did work?
"Joe" <none@aol.com> wrote in message news:erHDbixPDHA.2852@tk2msftngp13.phx.gbl...
Thanks for the reply back! I was away Friday but I will check this out ASAP
"WOLFF" <Need@FREEbsd> wrote in message news:e28vJOOPDHA.3700@tk2msftngp13.phx.gbl...

here it is
http://support.microsoft.com/defaul...ben-us%3b315074

"WOLFF" <Need@FREEbsd> wrote in message news:OoxAyJOPDHA.1584@TK2MSFTNGP11.phx.gbl...
> Hi Joe,
> Your missing a MS patch, Q314074, or something
> vary close to that Q number, it can only be D/L'd after calling MS support,
> but it's a freebe or you can get it from someone you know !
> Let me go look for this Q
> "Joe" <none@aol.com> wrote in message
> news:#CZQNPBPDHA.3192@tk2msftngp13.phx.gbl...
> >
> >
> > I setup or RIS with a few different images, however I'm having some
> issues
> > with one IBM laptop image. I sent the image up with RISPREP. I can see the
> > Client Installation Wizard then when I tried to pull it down via the pxe,
> I
> > see the others images but then I get 'The operating system image you
> > selected does not contain the necessary drivers for your network adapter'.
> I
> > did a search on the Internet and I tried to add the IMB Nic drivers but
> I'm
> > not sure if I' doing it correctly. I did the following:
> >
> > 1. On the RIS server, copy the OEM-supplied .inf and .sys file for
> the
> > network adapter to the RemoteInstall\Setup\Language\Images\Dir_name\i386
> > folder. This allows Setup to use the driver during the Text-mode portion
> of
> > the installation.
> > 2. At the same level as the I386 folder on the RIS image, create a
> > $oem$ folder with the following structure:
> > \$oem$\$1\Drivers\Nic (is this correct?)
> > (I placed the driver in \$oem$\$1\Drivers\Nic\Win2K\ehternet )
> > 3. Copy the OEM-supplied driver files to this folder. Note the
> folder
> > in which the .inf file looks for its drivers. Some manufacturers place the
> > .inf file in a folder and copy the driver files from a subfolder. If this
> is
> > the case, create the same folder structure below the one you created in
> this
> > step.
> >
> > NOTE: If the RIS image was created with RIPREP, you must perform these
> steps
> > on both the RIPREP image and the RISETUP image that corresponds to the
> > RIPREP image. (what do they mean by this)
> >
> >
> > 4. Make the following changes to the .sif file to be used for this
> > image installation:
> > [Unattended]
> > OemPreinstall = yes
> >
> > OemPnpDriversPath = \Drivers\Nic
> > (I changed this to \Drivers\Nic\Win2K\ehternet,, is this correct)
> > 5. Stop and restart the BINL service on the RIS server. Type the
> > following lines at the command prompt, pressing ENTER after each command:
> > net stop binlsvc
> > net start binlsvc
> > Do I actually create a folder called $oem$, any help would be greatly
> > appreciated
> >
> >
>
>

You are welcome to browse the documents I posted last summer to overcome
these "driver not found" issues. It will just give you an idea of the
steps - mainly you need to look to IBM for the driver files.

http://www.mvps.org/pictureit/RIS/Intel100VM.htm

--
Scott Baldridge
Windows Server MVP, MCSE

I'm sorry, I meant to say it did not work...what I did was copy the Win2000
CD the the E:\ on the RIS & Slipstreamed SP4into it...then I Added the SP4
image to the RIS so now I have another Win2000 image (only with SP4)....then
I edited that sif file & created the $oem$ folder on the same level as the
i386 folder and added the drivers to \$oem$\$1\Drivers\Nic and tried to pull
it down, same thing, I could see the Ris Wizard but it fails with the
"Operating System Image You Selected Does Not Contain the Necessary Drivers"
.. I removed the nic folder and re-edited the sif file back...tomorrow I will
push the SP4 image up FROM the laptop then add the \$oem$\$1\Drivers\Nic
path & edit the sif on that setup folder to see if that works?