More RIS added NIC issues

[Diane McCorkle]

Greetings,

I'm beginning to doubt my sanity.

I'd finally got the Intel1000 Nics up and running, and I'm testing a 2k3 RIS
server and all my OS related version issues are gone, but I can't get a
viable solution to the new Broadcom NIC's Dell is using on their lines.

All 3 files that the Broadcom uses are in the NETWORK\ONBOARD folder
B57XP32.CAT
B57XP32.INF
B57XP32.SYS

I've created the following structure:

\Images\X300V1.0\i386\templates
\Images\X300V1.0\i386\Mirror1
\Images\X300V1.0\$OEM$\$1\DRIVERS\NETWORK\ONBOARD

My Riprep.sif has the following section:
[Unattended]
OemPreinstall = yes
Oempnpdriverspath = DRIVERS\NETWORK\ONBOARD
DriverSigningPolicy = ignore
FileSystem = leavealone
ExtendOEMPartition = 0
TargetPath = \WINDOWS
OemSkipEula = yes
InstallFilesPath = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"
LegacyNIC = 1

I have only the flat XP image and this laptop image on the Lab

I still get "the image selected does not contain drivers for your hardware."

I'm at a loss, and this is a "must be fixed issue"

thanks

Diane

 

[Matt Renwick]

If you are trying to deploy an RIPrep'd image, the drivers must also be
added into the userdata folder for the riprep image and the
"OemPnPDriversPath = Drivers\NIC" or similar statement in the riprep.sif
file....

Hope this helps....And I think MS should have a "new hardware wizard" to
help patch new drivers back into the drivers cab so this issue would go
away....while they are at it they could correct the F3 function to allow a
HAL change from an Riprep image just as if you were installing from
CD...today, the F3 function acts like it will work, but does nothing when
loading an RIPrep image.


Matt Renwick

Diane, this Dell system... you said it was a laptop?

Have you tried the RIS Bootdisk?

RIS doesn'\t support laptops UNLESS the laptop is connected in a docking
station.

We have a few of Broadcom in our Dell desktops... works fine with our basic
RIS implementation (we didn't even add the Broadcome drivers)... it's being
detected as another Intel based card... (haven't checked but the Broadcoms
might indeed be using an Intel chip).

--
Re~Silient
_
"Diane McCorkle" <diane.mccorkle at atcassociates dot com> wrote in message

Greetings,

I'm beginning to doubt my sanity.

I'd finally got the Intel1000 Nics up and running, and I'm testing a 2k3 RIS
server and all my OS related version issues are gone, but I can't get a
viable solution to the new Broadcom NIC's Dell is using on their lines.

All 3 files that the Broadcom uses are in the NETWORK\ONBOARD folder
B57XP32.CAT
B57XP32.INF
B57XP32.SYS

I've created the following structure:

\Images\X300V1.0\i386\templates
\Images\X300V1.0\i386\Mirror1
\Images\X300V1.0\$OEM$\$1\DRIVERS\NETWORK\ONBOARD

My Riprep.sif has the following section:
[Unattended]
OemPreinstall = yes
Oempnpdriverspath = DRIVERS\NETWORK\ONBOARD
DriverSigningPolicy = ignore
FileSystem = leavealone
ExtendOEMPartition = 0
TargetPath = \WINDOWS
OemSkipEula = yes
InstallFilesPath = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"
LegacyNIC = 1

I have only the flat XP image and this laptop image on the Lab

I still get "the image selected does not contain drivers for your hardware."

I'm at a loss, and this is a "must be fixed issue"

thanks

Diane

 

[Matt Renwick]

Note that the location of the drivers is different on the RIPrep image (in
Userdata) than the flat image (in $1), but both the Riprep.sif and
ristndrd.sif file need the OemPnPDriversPath statement....


Good luck.
Matt

If you are trying to deploy an RIPrep'd image, the drivers must also be
added into the userdata folder for the riprep image and the
"OemPnPDriversPath = Drivers\NIC" or similar statement in the riprep.sif
file....

Hope this helps....And I think MS should have a "new hardware wizard" to
help patch new drivers back into the drivers cab so this issue would go
away....while they are at it they could correct the F3 function to allow a
HAL change from an Riprep image just as if you were installing from
CD...today, the F3 function acts like it will work, but does nothing when
loading an RIPrep image.


Matt Renwick

Diane, this Dell system... you said it was a laptop?

Have you tried the RIS Bootdisk?

RIS doesn'\t support laptops UNLESS the laptop is connected in a docking
station.

We have a few of Broadcom in our Dell desktops... works fine with our basic
RIS implementation (we didn't even add the Broadcome drivers)... it's being
detected as another Intel based card... (haven't checked but the Broadcoms
might indeed be using an Intel chip).

--
Re~Silient
_
"Diane McCorkle" <diane.mccorkle at atcassociates dot com> wrote in message

Greetings,

I'm beginning to doubt my sanity.

I'd finally got the Intel1000 Nics up and running, and I'm testing a

2k3
RIS

server and all my OS related version issues are gone, but I can't get a
viable solution to the new Broadcom NIC's Dell is using on their lines.

All 3 files that the Broadcom uses are in the NETWORK\ONBOARD folder
B57XP32.CAT
B57XP32.INF
B57XP32.SYS

I've created the following structure:

\Images\X300V1.0\i386\templates
\Images\X300V1.0\i386\Mirror1
\Images\X300V1.0\$OEM$\$1\DRIVERS\NETWORK\ONBOARD

My Riprep.sif has the following section:
[Unattended]
OemPreinstall = yes
Oempnpdriverspath = DRIVERS\NETWORK\ONBOARD
DriverSigningPolicy = ignore
FileSystem = leavealone
ExtendOEMPartition = 0
TargetPath = \WINDOWS
OemSkipEula = yes
InstallFilesPath = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"
LegacyNIC = 1

I have only the flat XP image and this laptop image on the Lab

I still get "the image selected does not contain drivers for your hardware."

I'm at a loss, and this is a "must be fixed issue"

thanks

Diane

 

[Diane McCorkle]

Thanks,

As far as Silent's comments,
The Dells are all onboard NIC's, but only as of the brand new D series are
they using the new Broadcom 100/1000 NICs

One issue of concern is that I've seen oempnpdrivers path referred to in the
following manners:

Oempnpdriverspath = "DRIVERS\NETWORK\ONBOARD"
Oempnpdriverspath = DRIVERS\NETWORK\ONBOARD
Oempnpdriverspath = "\DRIVERS\NETWORK\ONBOARD"
Oempnpdriverspath = \DRIVERS\NETWORK\ONBOARD

Thanks for your input, and off to bang my head against the wall some more

Diane

Note that the location of the drivers is different on the RIPrep image (in
Userdata) than the flat image (in $1), but both the Riprep.sif and
ristndrd.sif file need the OemPnPDriversPath statement....


Good luck.
Matt

If you are trying to deploy an RIPrep'd image, the drivers must also be
added into the userdata folder for the riprep image and the
"OemPnPDriversPath = Drivers\NIC" or similar statement in the riprep.sif
file....

Hope this helps....And I think MS should have a "new hardware wizard" to
help patch new drivers back into the drivers cab so this issue would go
away....while they are at it they could correct the F3 function to allow a
HAL change from an Riprep image just as if you were installing from
CD...today, the F3 function acts like it will work, but does nothing when
loading an RIPrep image.


Matt Renwick

get

a

viable solution to the new Broadcom NIC's Dell is using on their lines.

All 3 files that the Broadcom uses are in the NETWORK\ONBOARD folder
B57XP32.CAT
B57XP32.INF
B57XP32.SYS

I've created the following structure:

\Images\X300V1.0\i386\templates
\Images\X300V1.0\i386\Mirror1
\Images\X300V1.0\$OEM$\$1\DRIVERS\NETWORK\ONBOARD

My Riprep.sif has the following section:
[Unattended]
OemPreinstall = yes
Oempnpdriverspath = DRIVERS\NETWORK\ONBOARD
DriverSigningPolicy = ignore
FileSystem = leavealone
ExtendOEMPartition = 0
TargetPath = \WINDOWS
OemSkipEula = yes
InstallFilesPath = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"
LegacyNIC = 1

I have only the flat XP image and this laptop image on the Lab

I still get "the image selected does not contain drivers for your
hardware."

I'm at a loss, and this is a "must be fixed issue"

thanks

Diane

 

[Re~Silient]

Diane, original post:
"I have only the flat XP image and this laptop image on the Lab"

But are they laptops?

--
Re~Silient
_

Thanks,

As far as Silent's comments,
The Dells are all onboard NIC's, but only as of the brand new D series are
they using the new Broadcom 100/1000 NICs

One issue of concern is that I've seen oempnpdrivers path referred to in the
following manners:

Oempnpdriverspath = "DRIVERS\NETWORK\ONBOARD"
Oempnpdriverspath = DRIVERS\NETWORK\ONBOARD
Oempnpdriverspath = "\DRIVERS\NETWORK\ONBOARD"
Oempnpdriverspath = \DRIVERS\NETWORK\ONBOARD

Thanks for your input, and off to bang my head against the wall some more

Diane

Note that the location of the drivers is different on the RIPrep image (in
Userdata) than the flat image (in $1), but both the Riprep.sif and
ristndrd.sif file need the OemPnPDriversPath statement....


Good luck.
Matt

allow

a

HAL change from an Riprep image just as if you were installing from
CD...today, the F3 function acts like it will work, but does nothing when
loading an RIPrep image.


Matt Renwick
Diane, this Dell system... you said it was a laptop?

Have you tried the RIS Bootdisk?

RIS doesn'\t support laptops UNLESS the laptop is connected in a docking
station.

We have a few of Broadcom in our Dell desktops... works fine with our
basic
RIS implementation (we didn't even add the Broadcome drivers)... it's
being
detected as another Intel based card... (haven't checked but the Broadcoms
might indeed be using an Intel chip).

--
Re~Silient
_
"Diane McCorkle" <diane.mccorkle at atcassociates dot com> wrote in
message
Greetings,

I'm beginning to doubt my sanity.

I'd finally got the Intel1000 Nics up and running, and I'm testing

a
2k3

RIS
server and all my OS related version issues are gone, but I can't

get

a
viable solution to the new Broadcom NIC's Dell is using on their lines.

All 3 files that the Broadcom uses are in the NETWORK\ONBOARD folder
B57XP32.CAT
B57XP32.INF
B57XP32.SYS

I've created the following structure:

\Images\X300V1.0\i386\templates
\Images\X300V1.0\i386\Mirror1
\Images\X300V1.0\$OEM$\$1\DRIVERS\NETWORK\ONBOARD

My Riprep.sif has the following section:
[Unattended]
OemPreinstall = yes
Oempnpdriverspath = DRIVERS\NETWORK\ONBOARD
DriverSigningPolicy = ignore
FileSystem = leavealone
ExtendOEMPartition = 0
TargetPath = \WINDOWS
OemSkipEula = yes
InstallFilesPath = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"
LegacyNIC = 1

I have only the flat XP image and this laptop image on the Lab

I still get "the image selected does not contain drivers for your
hardware."

I'm at a loss, and this is a "must be fixed issue"

thanks

Diane

 

[Re~Silient]

Diane,
I'll check those Broadcom/Dell's we have and see which drivers we're
loading...

--
Re~Silient
WPO11SP1
Windows XP SP1 Pro
_

Silent,

A flat XP image with proper drivers, and this laptop, yes,

but these are new laptops with PXE PCI NIC's built in, they're fully RISable
except for the download of the OS, I'm aware that in the past we had to RIS
via docking station before the mini-PCI days. I've been RISing older Dell
laptops, i.e. the past year and a half with Intel NIC's just fine.. thats
one of the reasons this is so annoying.

HTH

Diane

Diane, original post:
"I have only the flat XP image and this laptop image on the Lab"

But are they laptops?

--
Re~Silient
_
"Diane McCorkle" <diane.mccorkle at atcassociates dot com> wrote in message

Thanks,

As far as Silent's comments,
The Dells are all onboard NIC's, but only as of the brand new D series are
they using the new Broadcom 100/1000 NICs

One issue of concern is that I've seen oempnpdrivers path referred to

in
the

following manners:

Oempnpdriverspath = "DRIVERS\NETWORK\ONBOARD"
Oempnpdriverspath = DRIVERS\NETWORK\ONBOARD
Oempnpdriverspath = "\DRIVERS\NETWORK\ONBOARD"
Oempnpdriverspath = \DRIVERS\NETWORK\ONBOARD

Thanks for your input, and off to bang my head against the wall some more

Diane


Note that the location of the drivers is different on the RIPrep

image
(in

Userdata) than the flat image (in $1), but both the Riprep.sif and
ristndrd.sif file need the OemPnPDriversPath statement....


Good luck.
Matt

If you are trying to deploy an RIPrep'd image, the drivers must

also
be

added into the userdata folder for the riprep image and the
"OemPnPDriversPath = Drivers\NIC" or similar statement in the riprep.sif
file....

Hope this helps....And I think MS should have a "new hardware

wizard"

to
help patch new drivers back into the drivers cab so this issue

would
go

away....while they are at it they could correct the F3 function to allow
a
HAL change from an Riprep image just as if you were installing from
CD...today, the F3 function acts like it will work, but does nothing
when
loading an RIPrep image.


Matt Renwick
Diane, this Dell system... you said it was a laptop?

Have you tried the RIS Bootdisk?

RIS doesn'\t support laptops UNLESS the laptop is connected in a
docking
station.

We have a few of Broadcom in our Dell desktops... works fine

with
our

basic
RIS implementation (we didn't even add the Broadcome drivers)... it's
being
detected as another Intel based card... (haven't checked but the
Broadcoms
might indeed be using an Intel chip).

--
Re~Silient
_
"Diane McCorkle" <diane.mccorkle at atcassociates dot com> wrote in
message
Greetings,

I'm beginning to doubt my sanity.

I'd finally got the Intel1000 Nics up and running, and I'm

testing

a
2k3
RIS
server and all my OS related version issues are gone, but I can't
get
a
viable solution to the new Broadcom NIC's Dell is using on their
lines.

All 3 files that the Broadcom uses are in the NETWORK\ONBOARD folder
B57XP32.CAT
B57XP32.INF
B57XP32.SYS

I've created the following structure:

\Images\X300V1.0\i386\templates
\Images\X300V1.0\i386\Mirror1
\Images\X300V1.0\$OEM$\$1\DRIVERS\NETWORK\ONBOARD

My Riprep.sif has the following section:
[Unattended]
OemPreinstall = yes
Oempnpdriverspath = DRIVERS\NETWORK\ONBOARD
DriverSigningPolicy = ignore
FileSystem = leavealone
ExtendOEMPartition = 0
TargetPath = \WINDOWS
OemSkipEula = yes
InstallFilesPath =
"\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"
LegacyNIC = 1

I have only the flat XP image and this laptop image on the Lab

I still get "the image selected does not contain drivers for your
hardware."

I'm at a loss, and this is a "must be fixed issue"

thanks

Diane

 

[AlanJ]

Diane,
I'll check those Broadcom/Dell's we have and see which drivers we're
loading...

--
Re~Silient
WPO11SP1
Windows XP SP1 Pro
_

Silent,

A flat XP image with proper drivers, and this laptop, yes,

but these are new laptops with PXE PCI NIC's built in, they're fully RISable
except for the download of the OS, I'm aware that in the past we had to RIS
via docking station before the mini-PCI days. I've been RISing older Dell
laptops, i.e. the past year and a half with Intel NIC's just fine.. thats
one of the reasons this is so annoying.

HTH

Diane

Diane, original post:
"I have only the flat XP image and this laptop image on the Lab"

But are they laptops?

--
Re~Silient
_
"Diane McCorkle" <diane.mccorkle at atcassociates dot com> wrote in message
Thanks,

As far as Silent's comments,
The Dells are all onboard NIC's, but only as of the brand new D series are
they using the new Broadcom 100/1000 NICs

One issue of concern is that I've seen oempnpdrivers path referred to

in
the

following manners:

Oempnpdriverspath = "DRIVERS\NETWORK\ONBOARD"
Oempnpdriverspath = DRIVERS\NETWORK\ONBOARD
Oempnpdriverspath = "\DRIVERS\NETWORK\ONBOARD"
Oempnpdriverspath = \DRIVERS\NETWORK\ONBOARD

Thanks for your input, and off to bang my head against the wall some more

Diane


Note that the location of the drivers is different on the RIPrep

image
(in

Userdata) than the flat image (in $1), but both the Riprep.sif and
ristndrd.sif file need the OemPnPDriversPath statement....


Good luck.
Matt

If you are trying to deploy an RIPrep'd image, the drivers must

also
be

added into the userdata folder for the riprep image and the
"OemPnPDriversPath = Drivers\NIC" or similar statement in the riprep.sif
file....

Hope this helps....And I think MS should have a "new hardware

wizard"
to

help patch new drivers back into the drivers cab so this issue

would
go

away....while they are at it they could correct the F3 function to

allow
a

HAL change from an Riprep image just as if you were installing from
CD...today, the F3 function acts like it will work, but does

nothing
when

loading an RIPrep image.


Matt Renwick
Diane, this Dell system... you said it was a laptop?

Have you tried the RIS Bootdisk?

RIS doesn'\t support laptops UNLESS the laptop is connected in a docking
station.

We have a few of Broadcom in our Dell desktops... works fine

with
our
basic

RIS implementation (we didn't even add the Broadcome drivers)...

it's
being

detected as another Intel based card... (haven't checked but the Broadcoms
might indeed be using an Intel chip).

in
message

Greetings,

I'm beginning to doubt my sanity.

I'd finally got the Intel1000 Nics up and running, and I'm

testing
a
2k3
RIS

server and all my OS related version issues are gone, but I

can't
get
a

viable solution to the new Broadcom NIC's Dell is using on

their
lines.

All 3 files that the Broadcom uses are in the NETWORK\ONBOARD folder
B57XP32.CAT
B57XP32.INF
B57XP32.SYS

I've created the following structure:

\Images\X300V1.0\i386\templates
\Images\X300V1.0\i386\Mirror1
\Images\X300V1.0\$OEM$\$1\DRIVERS\NETWORK\ONBOARD

My Riprep.sif has the following section:
[Unattended]
OemPreinstall = yes
Oempnpdriverspath = DRIVERS\NETWORK\ONBOARD
DriverSigningPolicy = ignore
FileSystem = leavealone
ExtendOEMPartition = 0
TargetPath = \WINDOWS
OemSkipEula = yes
InstallFilesPath = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"
LegacyNIC = 1

I have only the flat XP image and this laptop image on the Lab

I still get "the image selected does not contain drivers for

your
hardware."

I'm at a loss, and this is a "must be fixed issue"

thanks

Diane

Diane,


Found a post on Dell's site for this for D400's. Put the Win2K (as
opposed to XP) version of the drivers in the source XP i386 directory.
I had the same and this cured it.

 

[Diane McCorkle]

FYI,

I found out just this week I was chasing my tail,

the drivers I had been provided had a bad INF file,

new drivers from Dell's internal folks with the right inf, everything is all
set.

Diane

"Re~Silient" <[email protected]> wrote in message

Diane,
I'll check those Broadcom/Dell's we have and see which drivers we're
loading...

--
Re~Silient
WPO11SP1
Windows XP SP1 Pro
_
"Diane McCorkle" <diane.mccorkle at atcassociates dot com> wrote in message

Silent,

A flat XP image with proper drivers, and this laptop, yes,

but these are new laptops with PXE PCI NIC's built in, they're fully RISable
except for the download of the OS, I'm aware that in the past we had

to
RIS

via docking station before the mini-PCI days. I've been RISing older Dell
laptops, i.e. the past year and a half with Intel NIC's just fine.. thats
one of the reasons this is so annoying.

HTH

Diane


Diane, original post:
"I have only the flat XP image and this laptop image on the Lab"

But are they laptops?

--
Re~Silient
_
"Diane McCorkle" <diane.mccorkle at atcassociates dot com> wrote in message
Thanks,

As far as Silent's comments,
The Dells are all onboard NIC's, but only as of the brand new D

series
are

they using the new Broadcom 100/1000 NICs

One issue of concern is that I've seen oempnpdrivers path referred

to
in
the

following manners:

Oempnpdriverspath = "DRIVERS\NETWORK\ONBOARD"
Oempnpdriverspath = DRIVERS\NETWORK\ONBOARD
Oempnpdriverspath = "\DRIVERS\NETWORK\ONBOARD"
Oempnpdriverspath = \DRIVERS\NETWORK\ONBOARD

Thanks for your input, and off to bang my head against the wall

some
more

Diane


Note that the location of the drivers is different on the RIPrep image
(in
Userdata) than the flat image (in $1), but both the Riprep.sif and
ristndrd.sif file need the OemPnPDriversPath statement....


Good luck.
Matt

If you are trying to deploy an RIPrep'd image, the drivers

must
also
be

added into the userdata folder for the riprep image and the
"OemPnPDriversPath = Drivers\NIC" or similar statement in the riprep.sif
file....

Hope this helps....And I think MS should have a "new hardware wizard"
to
help patch new drivers back into the drivers cab so this issue would
go
away....while they are at it they could correct the F3

function to
allow
a

HAL change from an Riprep image just as if you were installing from
CD...today, the F3 function acts like it will work, but does nothing
when
loading an RIPrep image.


Matt Renwick
Diane, this Dell system... you said it was a laptop?

Have you tried the RIS Bootdisk?

RIS doesn'\t support laptops UNLESS the laptop is connected

in a
docking

station.

We have a few of Broadcom in our Dell desktops... works fine with
our
basic
RIS implementation (we didn't even add the Broadcome

drivers)...
it's
being

detected as another Intel based card... (haven't checked but

the
Broadcoms

might indeed be using an Intel chip).

wrote
in
message

Greetings,

I'm beginning to doubt my sanity.

I'd finally got the Intel1000 Nics up and running, and I'm testing
a
2k3
RIS
server and all my OS related version issues are gone, but

I
can't
get
a

viable solution to the new Broadcom NIC's Dell is using on their
lines.

All 3 files that the Broadcom uses are in the

NETWORK\ONBOARD
folder

B57XP32.CAT
B57XP32.INF
B57XP32.SYS

I've created the following structure:

\Images\X300V1.0\i386\templates
\Images\X300V1.0\i386\Mirror1
\Images\X300V1.0\$OEM$\$1\DRIVERS\NETWORK\ONBOARD

My Riprep.sif has the following section:
[Unattended]
OemPreinstall = yes
Oempnpdriverspath = DRIVERS\NETWORK\ONBOARD
DriverSigningPolicy = ignore
FileSystem = leavealone
ExtendOEMPartition = 0
TargetPath = \WINDOWS
OemSkipEula = yes
InstallFilesPath = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"
LegacyNIC = 1

I have only the flat XP image and this laptop image on the Lab

I still get "the image selected does not contain drivers

for
your
hardware."

I'm at a loss, and this is a "must be fixed issue"

thanks

Diane

Diane,


Found a post on Dell's site for this for D400's. Put the Win2K (as
opposed to XP) version of the drivers in the source XP i386 directory.
I had the same and this cured it.