RIS with nForce2 motherboards and XP

[Erick Thompson]

I have a large number of users with systems that have the nForce2
motherboards. I am trying to install Windows XP from a Windows 2003 RIS
server. I was able to get Windows 2000 to install from RIS using $oem$
information from Q315279, but that process doesn't seem to work with XP
and/or the XP versions of the drivers that I downloaded from nVidia. Has
anyone been able to use RIS to install XP on nForce2 motherboards? Are there
special problems with XP and nForce boards?

Thanks,
Erick

 

[NIC Student]

Crap, Erick. Did you post to enough groups???

I've never used nForce2 drivers, but I thought I'd ask if you have tried the
Win2000 drivers that you used successfully with RIS instead of the XP ones
as a test (with the $oem$ folder)?

Have you downloaded the latest drivers from nvidia? Tried both 2000 and XP
drivers?

When you copy the drivers into the i386 folder and are asked about
owerwriting, that means you might need to locate the driverfilename.pnf file
and delete it. In fact, you can delete all PNF files in the i386 directory
and when you restart the Remote Install Service, they will be rebuilt. I've
done this many times, the first time you RIS a client, there will be a
little longer delay than normal.

What is the exact error message you receive?

 

[Erick Thompson]

lol The post was a touch cross posted, but I wasn't sure which group would
be best.

The error I've been getting is that right after I start the setup (while
it's still text mode), it says that the image I've chosen does not support
my network adapter, and so setup cannot continue.

Your post triggered an idea, which worked rather well. I fixed the problem
by putting the driver files in both imagebase\$oem$\etc and imagebase. This
wasn't mentioned in KB315279, which is very annoying, as that seems to be
all that was needed. If you have any contacts as an MVP, you might want to
mention that omission...

Do you know for the other drivers, do I also need to copy all the driver
files to both the $oem$ structure and the image base?

Thanks!
Erick

 

[NIC Student]

Hi Erik,

I'm glad you figured it out!! This is actually a common problem, your
drivers indeed must go to the $oem$ and i386 of the cd-based image. I will
mention it to M$. You used to be able to comment each KB article - I wish
they would bring that function back.

The article does say " Adding a network adapter that requires an OEM driver
to a CD-ROM-based RIS image involves some of the same steps... " but doesn't
mention the RIPREP images that inevitably follow.

Thanks for your follow-up.