Dell Broadcom NetXtreme Family of Adapters Broadcom NetXtreme 57XX User Guide - Page 134

Using the System Preparation Tool - windows xp

Get Dell Broadcom NetXtreme Family of Adapters PDF manuals and user guides View all Dell Broadcom NetXtreme Family of Adapters manuals
Add to My Manuals
Save this manual to your list of manuals

Page 134 highlights

Solution: This problem is not isolated to the Broadcom adapter. However, based on several inquiries, we are publishing the following instructions based on other customers successfully working around this issue: 1. Place the Broadcom driver files in the original image folder (the image folder created when risetup.exe was executed for the first time). Example: i:\RemoteInstall\Setup\English\Images\(Original Image) 2. Place the Broadcom driver files in the i386 subfolder under the original image folder. Example: i:\RemoteInstall\Setup\English\Images\(Original Image)\i386 3. Place the Broadcom driver files for the network adapter in the RIPREP Image folder. Example: i:\RemoteInstall\Setup\English\Images\(RIPREP Image) 4. Place the Broadcom adapter drivers in the i386 subfolder where the RIPREP Image is located. Example: i:\RemoteInstall\Setup\English\Images\(RIPREP Image)\i386 The Microsoft Knowledge base articles listed below were used as a reference for the following instructions: http://support.microsoft.com/default.aspx?scid=kb;EN-US;254078 http://support.microsoft.com/default.aspx?scid=kb;EN-US;246184 1. Create the following path and place all Broadcom driver files in ..\(RIPREP Image)\$oem$\$1\Drivers. 2. Edit the riprep.sif file located in ..\(RIPREP Image)\i386\Template to include the following information under the [Unattend] section: OemPreinstall = yes OemPnPDriversPath = "Drivers DriverSigningPolicy = Ignore 3. Create the following path and place all Broadcom driver files in ..\(Original Image)\$oem$\$1\Drivers. 4. Edit the ristndrd.sif file located in ..\(Original Image)\i386 \templates to include the following information under the [Unattend] section: OemPreinstall = yes OemPnPDriversPath = "Drivers DriverSigningPolicy = Ignore 5. Restart the Remote Installation service. This can be performed from a command line with the following commands: net stop binlsvc net start binlsvc Using the System Preparation Tool Problem: I want to be sure that my Broadcom NetXtreme adapter works properly if I use the System Preparation utility (Sysprep.exe) to install an existing configuration on my system. Solution: On the Sysprep.inf file, modify the [Unattend] header as shown below: [Unattend] OemPnPDriversPath=Drivers\Net OemPreinstall = Yes The driver files for the Broadcom NetXtreme adapter must reside in this folder, which is located on the system drive (where the operating system resides). If other drivers are to be loaded, then Drivers\Net can be appended to the paths listed and separated by a semicolon: Example: OemPnpDriversPath=Drivers\Video;Drivers\Net For Windows XP, the driver files to be included are B57win32.inf, B57win32.cat, and B57xp32.sys. For Windows 2000, the driver files to be included are B57win32.inf, B57win32.cat, and B57w2k.sys. The Sysprep utility must run with the -pnp switch, which enables the system to rescan for new devices that can be added during the mini-setup.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
Solution
: This problem is not isolated to the Broadcom adapter. However, based on several inquiries, we are publishing the
following instructions based on other customers successfully working around this issue:
1. Place the Broadcom driver files in the original image folder (the image folder created when risetup.exe was executed
for the first time).
Example: i:\RemoteInstall\Setup\English\Images\(Original Image)
2. Place the Broadcom driver files in the i386 subfolder under the original image folder.
Example: i:\RemoteInstall\Setup\English\Images\(
Original Image
)\i386
3. Place the Broadcom driver files for the network adapter in the RIPREP Image folder.
Example: i:\RemoteInstall\Setup\English\Images\(RIPREP Image)
4. Place the Broadcom adapter drivers in the i386 subfolder where the RIPREP Image is located.
Example: i:\RemoteInstall\Setup\English\Images\(RIPREP Image)\i386
The Microsoft Knowledge base articles listed below were used as a reference for the following instructions:
1. Create the following path and place all Broadcom driver files in ..\(
RIPREP Image
)\$oem$\$1\Drivers.
2. Edit the riprep.sif file located in ..\(
RIPREP Image
)\i386\Template to include the following information under the
[Unattend] section:
OemPreinstall = yes
OemPnPDriversPath = "Drivers
DriverSigningPolicy = Ignore
3. Create the following path and place all Broadcom driver files in ..\(
Original Image
)\$oem$\$1\Drivers.
4. Edit the ristndrd.sif file located in ..\(
Original Image
)\i386 \templates to include the following information under the
[Unattend] section:
OemPreinstall = yes
OemPnPDriversPath = "Drivers
DriverSigningPolicy = Ignore
5. Restart the Remote Installation service. This can be performed from a command line with the following commands:
net stop binlsvc
net start binlsvc
Using the System Preparation Tool
Problem:
I want to be sure that my Broadcom NetXtreme adapter works properly if I use the System Preparation utility
(Sysprep.exe) to install an existing configuration on my system.
Solution:
On the Sysprep.inf file, modify the [Unattend] header as shown below:
[Unattend]
OemPnPDriversPath=Drivers\Net
OemPreinstall = Yes
The driver files for the Broadcom NetXtreme adapter must reside in this folder, which is located on the system drive (where
the operating system resides). If other drivers are to be loaded, then
Drivers\Net
can be appended to the paths listed and
separated by a semicolon:
Example:
OemPnpDriversPath=Drivers\Video;Drivers\Net
For Windows XP, the driver files to be included are B57win32.inf, B57win32.cat, and B57xp32.sys.
For Windows 2000, the driver files to be included are B57win32.inf, B57win32.cat, and B57w2k.sys.
The Sysprep utility must run with the
–pnp
switch, which enables the system to rescan for new devices that can be added
during the mini-setup.