PC Review


Reply
Thread Tools Rate Thread

Re: RIS & Network adapters

 
 
Joe
Guest
Posts: n/a
 
      30th Jun 2003
Thanks for the reply back! I was away Friday but I will check this out ASAP
"WOLFF" <Need@FREEbsd> wrote in message news:(E-Mail Removed)...

here it is
http://support.microsoft.com/default...en-us%3b315074

"WOLFF" <Need@FREEbsd> wrote in message news:(E-Mail Removed)...
> 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" <(E-Mail Removed)> wrote in message
> news:#(E-Mail Removed)...
> >
> >
> > 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
> >
> >

>
>

 
Reply With Quote
 
 
 
 
Joe
Guest
Posts: n/a
 
      30th Jun 2003
I slipstreamed SP4 into the RIS and the copied the driver & edited the sif file, it's did work?
"Joe" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
Thanks for the reply back! I was away Friday but I will check this out ASAP
"WOLFF" <Need@FREEbsd> wrote in message news:(E-Mail Removed)...

here it is
http://support.microsoft.com/default...en-us%3b315074

"WOLFF" <Need@FREEbsd> wrote in message news:(E-Mail Removed)...
> 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" <(E-Mail Removed)> wrote in message
> news:#(E-Mail Removed)...
> >
> >
> > 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
> >
> >

>
>

 
Reply With Quote
 
NIC Student
Guest
Posts: n/a
 
      1st Jul 2003
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?





 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Strange problem : I can not install network adapters -- network categorychanged to unknown in device manager. A.J. Nylander Windows XP Hardware 2 12th Mar 2005 11:24 PM
Strange problem : I can not install network adapters -- network categorychanged to unknown in device manager. A.J. Nylander Microsoft Windows 2000 Hardware 2 12th Mar 2005 11:24 PM
Home Network using Linksys Phoneline USB Network Adapters =?Utf-8?B?V2VuZHk=?= Windows XP Networking 1 8th Feb 2005 07:04 AM
Multiple Network Adapters Browse Network Neighborhood Ryan Windows Networking 0 17th Jun 2004 04:17 AM
Network Connections Folder was unable to retrieve the list of Network adapters JG - SF Windows XP Networking 2 17th Dec 2003 09:36 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 02:09 PM.