RIS Driver issues

[Guest]

OK, I'm at my wit's end with this one. I'm creating a RIS image for our
desktop machines and I want the machines to auto-install the drivers. I've
followed the instructions in the article Q254078 (How to Add OEM Plug and
Play Drivers to Windows 2000 Installations) and am still having issues.

My Directory structure is (for the example the sound drivers):
$oem$
-$1
--Drivers
---Sound
----AC97
----allegro
----etc
I've also put into the [Unattended] section the following:
OemPnPDriversPath=Drivers\Sound\AC97;Drivers\Sound\allegro;Drivers\Sound\etc

I restarted the BINL service and still no go. Not sure what I'm doing wrong
but I may just go the Sysprep method of adding the directories right to the
image. Any help would be appreciated.

Thanks

 

[Michael Niehaus [MS]]

Where are you putting the $OEM$ directory structure? It needs to be at the
root of the image directory instead of under I386. See
http://support.microsoft.com/?kbid=315279.

-Michael Niehaus
Senior Consultant
MCS US Centers of Excellence - Deployment AOS
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Guest]

$oem$ is at the same level as i386. In fact, I read that on sysprep it needs
to be under it so I got excited thinking that's where I screwed up only to
find I did it right.

Where are you putting the $OEM$ directory structure? It needs to be at the
root of the image directory instead of under I386. See
http://support.microsoft.com/?kbid=315279.

-Michael Niehaus
Senior Consultant
MCS US Centers of Excellence - Deployment AOS
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.

OK, I'm at my wit's end with this one. I'm creating a RIS image for our
desktop machines and I want the machines to auto-install the drivers.
I've
followed the instructions in the article Q254078 (How to Add OEM Plug and
Play Drivers to Windows 2000 Installations) and am still having issues.

My Directory structure is (for the example the sound drivers):
$oem$
-$1
--Drivers
---Sound
----AC97
----allegro
----etc
I've also put into the [Unattended] section the following:
OemPnPDriversPath=Drivers\Sound\AC97;Drivers\Sound\allegro;Drivers\Sound\etc

I restarted the BINL service and still no go. Not sure what I'm doing
wrong
but I may just go the Sysprep method of adding the directories right to
the
image. Any help would be appreciated.

Thanks

 

[Michael Niehaus [MS]]

By any chance are you dealing with Broadcom drivers? If so, you may want to
check http://support.microsoft.com/?id=823658.

-Michael Niehaus
Senior Consultant
MCS US Centers of Excellence - Deployment AOS
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.

$oem$ is at the same level as i386. In fact, I read that on sysprep it
needs
to be under it so I got excited thinking that's where I screwed up only to
find I did it right.

Where are you putting the $OEM$ directory structure? It needs to be at
the
root of the image directory instead of under I386. See
http://support.microsoft.com/?kbid=315279.

-Michael Niehaus
Senior Consultant
MCS US Centers of Excellence - Deployment AOS
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no
rights.

OK, I'm at my wit's end with this one. I'm creating a RIS image for
our
desktop machines and I want the machines to auto-install the drivers.
I've
followed the instructions in the article Q254078 (How to Add OEM Plug
and
Play Drivers to Windows 2000 Installations) and am still having issues.

My Directory structure is (for the example the sound drivers):
$oem$
-$1
--Drivers
---Sound
----AC97
----allegro
----etc
I've also put into the [Unattended] section the following:
OemPnPDriversPath=Drivers\Sound\AC97;Drivers\Sound\allegro;Drivers\Sound\etc

I restarted the BINL service and still no go. Not sure what I'm doing
wrong
but I may just go the Sysprep method of adding the directories right to
the
image. Any help would be appreciated.

Thanks

 

[Guest]

Yup, have broadcom drivers, but they're working. The image comes down and
sets up correctly, but when I go into device manager my sound and video are
showing as unknown devices. Will I have to use the Sysprep method for the
drivers to install?

By any chance are you dealing with Broadcom drivers? If so, you may want to
check http://support.microsoft.com/?id=823658.

-Michael Niehaus
Senior Consultant
MCS US Centers of Excellence - Deployment AOS
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.

$oem$ is at the same level as i386. In fact, I read that on sysprep it
needs
to be under it so I got excited thinking that's where I screwed up only to
find I did it right.

Where are you putting the $OEM$ directory structure? It needs to be at
the
root of the image directory instead of under I386. See
http://support.microsoft.com/?kbid=315279.

-Michael Niehaus
Senior Consultant
MCS US Centers of Excellence - Deployment AOS
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no
rights.

OK, I'm at my wit's end with this one. I'm creating a RIS image for
our
desktop machines and I want the machines to auto-install the drivers.
I've
followed the instructions in the article Q254078 (How to Add OEM Plug
and
Play Drivers to Windows 2000 Installations) and am still having issues.

My Directory structure is (for the example the sound drivers):
$oem$
-$1
--Drivers
---Sound
----AC97
----allegro
----etc
I've also put into the [Unattended] section the following:
OemPnPDriversPath=Drivers\Sound\AC97;Drivers\Sound\allegro;Drivers\Sound\etc

I restarted the BINL service and still no go. Not sure what I'm doing
wrong
but I may just go the Sysprep method of adding the directories right to
the
image. Any help would be appreciated.

Thanks

 

[Michael Niehaus [MS]]

You shouldn't have to (although there may be unrelated reasons that you
would want to). If you delete the devices out of Device Manager and then
detect new hardware, does Windows find the drivers? If not, Windows doesn't
think it has an appropriate driver. Check
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath" to
make sure that the directories are in the path and that it is a
REG_EXPAND_SZ value. If they are there (prefixed by %SystemRoot%), then you
probably need to look at the SETUPAPI.LOG. See
http://msdn.microsoft.com/library/d..._836ef6f8-9331-4228-8b49-65484adef442.xml.asp
for more information.

Any chance those drivers aren't signed and that you haven't enabled the
option of installing unsigned drivers?

-Michael Niehaus
Senior Consultant
MCS US Centers of Excellence - Deployment AOS
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.

Yup, have broadcom drivers, but they're working. The image comes down and
sets up correctly, but when I go into device manager my sound and video
are
showing as unknown devices. Will I have to use the Sysprep method for the
drivers to install?

By any chance are you dealing with Broadcom drivers? If so, you may want
to
check http://support.microsoft.com/?id=823658.

-Michael Niehaus
Senior Consultant
MCS US Centers of Excellence - Deployment AOS
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no
rights.

$oem$ is at the same level as i386. In fact, I read that on sysprep it
needs
to be under it so I got excited thinking that's where I screwed up only
to
find I did it right.

:

Where are you putting the $OEM$ directory structure? It needs to be
at
the
root of the image directory instead of under I386. See
http://support.microsoft.com/?kbid=315279.

-Michael Niehaus
Senior Consultant
MCS US Centers of Excellence - Deployment AOS
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no
rights.

OK, I'm at my wit's end with this one. I'm creating a RIS image for
our
desktop machines and I want the machines to auto-install the
drivers.
I've
followed the instructions in the article Q254078 (How to Add OEM
Plug
and
Play Drivers to Windows 2000 Installations) and am still having
issues.

My Directory structure is (for the example the sound drivers):
$oem$
-$1
--Drivers
---Sound
----AC97
----allegro
----etc
I've also put into the [Unattended] section the following:
OemPnPDriversPath=Drivers\Sound\AC97;Drivers\Sound\allegro;Drivers\Sound\etc

I restarted the BINL service and still no go. Not sure what I'm
doing
wrong
but I may just go the Sysprep method of adding the directories right
to
the
image. Any help would be appreciated.

Thanks

 

[Guest]

Michael, first of all let me say thanks for sticking with me on this. I
checked that key and it looks like there is ONLY %Systemroot%/inf in the
driverpath. Should this be changed for my image? I'll check the log as you
suggested. As for signed drivers, I do not have the unsigned driver option
set but I did install the drivers from the $oem$ directory on the server to
validate they are correct and wasn't prompted to allow them so they should be
signed. I think you may be onto something with the driverpath regkey though.

You shouldn't have to (although there may be unrelated reasons that you
would want to). If you delete the devices out of Device Manager and then
detect new hardware, does Windows find the drivers? If not, Windows doesn't
think it has an appropriate driver. Check
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath" to
make sure that the directories are in the path and that it is a
REG_EXPAND_SZ value. If they are there (prefixed by %SystemRoot%), then you
probably need to look at the SETUPAPI.LOG. See
http://msdn.microsoft.com/library/d..._836ef6f8-9331-4228-8b49-65484adef442.xml.asp
for more information.

Any chance those drivers aren't signed and that you haven't enabled the
option of installing unsigned drivers?

-Michael Niehaus
Senior Consultant
MCS US Centers of Excellence - Deployment AOS
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.

Yup, have broadcom drivers, but they're working. The image comes down and
sets up correctly, but when I go into device manager my sound and video
are
showing as unknown devices. Will I have to use the Sysprep method for the
drivers to install?

By any chance are you dealing with Broadcom drivers? If so, you may want
to
check http://support.microsoft.com/?id=823658.

-Michael Niehaus
Senior Consultant
MCS US Centers of Excellence - Deployment AOS
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no
rights.


$oem$ is at the same level as i386. In fact, I read that on sysprep it
needs
to be under it so I got excited thinking that's where I screwed up only
to
find I did it right.

:

Where are you putting the $OEM$ directory structure? It needs to be
at
the
root of the image directory instead of under I386. See
http://support.microsoft.com/?kbid=315279.

-Michael Niehaus
Senior Consultant
MCS US Centers of Excellence - Deployment AOS
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no
rights.

OK, I'm at my wit's end with this one. I'm creating a RIS image for
our
desktop machines and I want the machines to auto-install the
drivers.
I've
followed the instructions in the article Q254078 (How to Add OEM
Plug
and
Play Drivers to Windows 2000 Installations) and am still having
issues.

My Directory structure is (for the example the sound drivers):
$oem$
-$1
--Drivers
---Sound
----AC97
----allegro
----etc
I've also put into the [Unattended] section the following:
OemPnPDriversPath=Drivers\Sound\AC97;Drivers\Sound\allegro;Drivers\Sound\etc

I restarted the BINL service and still no go. Not sure what I'm
doing
wrong
but I may just go the Sysprep method of adding the directories right
to
the
image. Any help would be appreciated.

Thanks

 

[Guest]

Michael, the setupapi.log file has no mention of any .inf as it should
(according to the linked article). Below is what is in the log:

---------Start----------
[SetupAPI Log]
OS Version = 5.1.2600 Service Pack 1
Platform ID = 2 (NT)
Service Pack = 1.0
Suite = 0x0100
Product Type = 1
Architecture = x86
[2005/05/03 16:17:49 772.1]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup.exe
-newsetup -mini
#W082 Could not locate a non-empty service section [Clean.Services] in
"C:\WINDOWS\System32\$winnt$.inf". Error 0xe0000102: The required line was
not found in the INF.
[2005/05/03 16:18:24 772.50]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup.exe
-newsetup -mini
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "ROOT\MS_PSCHEDMP\0000".
#I306 DICS_START: Device has been started.
[2005/05/03 16:18:24 772.51]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup.exe
-newsetup -mini
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "ROOT\MS_PSCHEDMP\0001".
#I306 DICS_START: Device has been started.
[2005/05/03 16:18:25 772.66]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup.exe
-newsetup -mini
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "ROOT\MS_PSCHEDMP\0000".
#I306 DICS_START: Device has been started.
[2005/05/03 16:18:25 772.67]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup.exe
-newsetup -mini
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "ROOT\MS_PSCHEDMP\0001".
#I306 DICS_START: Device has been started.
[2005/05/03 16:18:25 772.82]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup.exe
-newsetup -mini
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "ROOT\MS_PSCHEDMP\0000".
#I306 DICS_START: Device has been started.
[2005/05/03 16:18:25 772.83]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup.exe
-newsetup -mini
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "ROOT\MS_PSCHEDMP\0001".
#I306 DICS_START: Device has been started.
[2005/05/03 16:18:26 772.96]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup.exe
-newsetup -mini
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "ROOT\MS_PSCHEDMP\0000".
#I306 DICS_START: Device has been started.
[2005/05/03 16:18:26 772.97]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup.exe
-newsetup -mini
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "ROOT\MS_PSCHEDMP\0001".
#I306 DICS_START: Device has been started.
---------End----------

I may just end up adding the drivers into a directory on the base image and
change the devicepath to reflect it. I'll give this a few more tries but if
it doesn't work I'll have to go that route.

You shouldn't have to (although there may be unrelated reasons that you
would want to). If you delete the devices out of Device Manager and then
detect new hardware, does Windows find the drivers? If not, Windows doesn't
think it has an appropriate driver. Check
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath" to
make sure that the directories are in the path and that it is a
REG_EXPAND_SZ value. If they are there (prefixed by %SystemRoot%), then you
probably need to look at the SETUPAPI.LOG. See
http://msdn.microsoft.com/library/d..._836ef6f8-9331-4228-8b49-65484adef442.xml.asp
for more information.

Any chance those drivers aren't signed and that you haven't enabled the
option of installing unsigned drivers?

-Michael Niehaus
Senior Consultant
MCS US Centers of Excellence - Deployment AOS
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.

Yup, have broadcom drivers, but they're working. The image comes down and
sets up correctly, but when I go into device manager my sound and video
are
showing as unknown devices. Will I have to use the Sysprep method for the
drivers to install?

By any chance are you dealing with Broadcom drivers? If so, you may want
to
check http://support.microsoft.com/?id=823658.

-Michael Niehaus
Senior Consultant
MCS US Centers of Excellence - Deployment AOS
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no
rights.


$oem$ is at the same level as i386. In fact, I read that on sysprep it
needs
to be under it so I got excited thinking that's where I screwed up only
to
find I did it right.

:

Where are you putting the $OEM$ directory structure? It needs to be
at
the
root of the image directory instead of under I386. See
http://support.microsoft.com/?kbid=315279.

-Michael Niehaus
Senior Consultant
MCS US Centers of Excellence - Deployment AOS
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no
rights.

OK, I'm at my wit's end with this one. I'm creating a RIS image for
our
desktop machines and I want the machines to auto-install the
drivers.
I've
followed the instructions in the article Q254078 (How to Add OEM
Plug
and
Play Drivers to Windows 2000 Installations) and am still having
issues.

My Directory structure is (for the example the sound drivers):
$oem$
-$1
--Drivers
---Sound
----AC97
----allegro
----etc
I've also put into the [Unattended] section the following:
OemPnPDriversPath=Drivers\Sound\AC97;Drivers\Sound\allegro;Drivers\Sound\etc

I restarted the BINL service and still no go. Not sure what I'm
doing
wrong
but I may just go the Sysprep method of adding the directories right
to
the
image. Any help would be appreciated.

Thanks

 

[Guest]

**Bump**

I've tried adding the drivers to the local image and added the driver
location to the registry. Upon re-RISing the devices STILL aren't manually
found. What's odd is that I can go into Add/Remove hardware, select the
unknown device and have Windows automatically find the drivers for it. When
I do this the drivers are found and installed. Why would it install this way
but not on reboot?? I don't get it.

You shouldn't have to (although there may be unrelated reasons that you
would want to). If you delete the devices out of Device Manager and then
detect new hardware, does Windows find the drivers? If not, Windows doesn't
think it has an appropriate driver. Check
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath" to
make sure that the directories are in the path and that it is a
REG_EXPAND_SZ value. If they are there (prefixed by %SystemRoot%), then you
probably need to look at the SETUPAPI.LOG. See
http://msdn.microsoft.com/library/d..._836ef6f8-9331-4228-8b49-65484adef442.xml.asp
for more information.

Any chance those drivers aren't signed and that you haven't enabled the
option of installing unsigned drivers?

-Michael Niehaus
Senior Consultant
MCS US Centers of Excellence - Deployment AOS
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.

Yup, have broadcom drivers, but they're working. The image comes down and
sets up correctly, but when I go into device manager my sound and video
are
showing as unknown devices. Will I have to use the Sysprep method for the
drivers to install?

By any chance are you dealing with Broadcom drivers? If so, you may want
to
check http://support.microsoft.com/?id=823658.

-Michael Niehaus
Senior Consultant
MCS US Centers of Excellence - Deployment AOS
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no
rights.


$oem$ is at the same level as i386. In fact, I read that on sysprep it
needs
to be under it so I got excited thinking that's where I screwed up only
to
find I did it right.

:

Where are you putting the $OEM$ directory structure? It needs to be
at
the
root of the image directory instead of under I386. See
http://support.microsoft.com/?kbid=315279.

-Michael Niehaus
Senior Consultant
MCS US Centers of Excellence - Deployment AOS
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no
rights.

OK, I'm at my wit's end with this one. I'm creating a RIS image for
our
desktop machines and I want the machines to auto-install the
drivers.
I've
followed the instructions in the article Q254078 (How to Add OEM
Plug
and
Play Drivers to Windows 2000 Installations) and am still having
issues.

My Directory structure is (for the example the sound drivers):
$oem$
-$1
--Drivers
---Sound
----AC97
----allegro
----etc
I've also put into the [Unattended] section the following:
OemPnPDriversPath=Drivers\Sound\AC97;Drivers\Sound\allegro;Drivers\Sound\etc

I restarted the BINL service and still no go. Not sure what I'm
doing
wrong
but I may just go the Sysprep method of adding the directories right
to
the
image. Any help would be appreciated.

Thanks

 

[Rex Dieter]

I've also put into the [Unattended] section the following:
OemPnPDriversPath=Drivers\Sound\AC97;Drivers\Sound\allegro;Drivers\Sound\etc

We've been wrestling with getting this to work for *years* with no
success. We've since discovered much of MS's docs are incorrect on how
to set OemPnPDriversPath. Turns out entries (oftentimes) need to start
with \. Once prefixed with \'s, it started to work for us. Try
OemPnPDriversPath=\Drivers\Sound\AC97;\Drivers\Sound\allegro;\Drivers\Sound\etc
instead. (-:

-- Rex