HI, the $OEM$ is used under and/or after Windows has installed on the client.
Under the initial filecopy from the server, the NIC files have to be located in the i386 folder or else you get that error message with "no driver found for NIC"
Don't worry about the NTLDR, that was a RIS Windows 2000 Server issue. There is a Windows 2003 "hotfix" which replaces a newer version of the binlsvc.dll file (Remote Installation service), which was pointed out to me by Microsoft when I called to ask for the NTLDR hotfix.
Anyway, the way this was solved was by looking at the images on your RIS server. Note that the DEFAULT image which was created the first time you ran RIS Setup and put a Windows XP disk in the CD-ROM drive of the server. In this folder, you will see that the i386 folder contains hundreds of files, all of which map to various things, including, most importantly, drivers!
If you copy your drivers from the $OEM$ folder to this i386 folder, then your problems should be solved. If not, do what I did and make a $OEM$ folder hierarchy in each (including the DEFAULT) folder, and put the three driver files in each i386 folder as well.
Thank you very much for your answer, worked a treat!
Maybe one day, microsoft will just give you a nice little wizard when creating the image that asks for your driver files - EVEN if they are supported natively...
MattiasMattias
3 Posts
0
August 23rd, 2004 08:00
The search order is a mystery to me?
NordicL2
53 Posts
0
August 23rd, 2004 12:00
HI, the $OEM$ is used under and/or after Windows has installed on the client.
Under the initial filecopy from the server, the NIC files have to be located in the i386 folder or else you get that error message with "no driver found for NIC"
Sismann
9 Posts
0
October 13th, 2004 14:00
Hi,
I have the same problem but still not solved... What do you mean by "I Tryed the Setupldr.exe/NTLD from SP2" ?
Thank you !
WillShakespeare
7 Posts
0
November 1st, 2004 11:00
sysman,
Don't worry about the NTLDR, that was a RIS Windows 2000 Server issue. There is a Windows 2003 "hotfix" which replaces a newer version of the binlsvc.dll file (Remote Installation service), which was pointed out to me by Microsoft when I called to ask for the NTLDR hotfix.
Anyway, the way this was solved was by looking at the images on your RIS server. Note that the DEFAULT image which was created the first time you ran RIS Setup and put a Windows XP disk in the CD-ROM drive of the server. In this folder, you will see that the i386 folder contains hundreds of files, all of which map to various things, including, most importantly, drivers!
If you copy your drivers from the $OEM$ folder to this i386 folder, then your problems should be solved. If not, do what I did and make a $OEM$ folder hierarchy in each (including the DEFAULT) folder, and put the three driver files in each i386 folder as well.
Ziggy1980
1 Message
0
November 26th, 2004 10:00
Arghhh!! Microsoft!
Thank you very much for your answer, worked a treat!
Maybe one day, microsoft will just give you a nice little wizard when creating the image that asks for your driver files - EVEN if they are supported natively...
One day...
Cheers,
Sismann
9 Posts
0
November 26th, 2004 12:00