K
Kevin Conley
I am not sure this is the right newsgroup but it seemed like the best fit.
Please advise if there is a better group.
Background:
I have used RIS to build my production machines and it works great. Once the
initial WinPE comes up under RIS, it runs my WINBom.ini file that creates 4
drive partitions. It goes on to copy another version of WinPE (basic, no
network) to one partition (drive E) and the future embedded image to one of
the other partions (Drive F). Drive F is used as the virgin "Factory
Restore" drive. It then sets the bootable partition to the WinPE drive
(Drive E) and then reboots the machine. The machine then comes up under
WinPE on the hard drive. That WinPE environment copies the embedded image
from the "Factory Restore" partition (Drive F) to the C drive to complete
the imaging process. Finaly, it sets the active partition to the C drive and
reboots the machine. The machine finaly comes up on the C drive and has a
freash copy of the embedded image. It runs through the FBA and then it is
ready for use. So at this point, the machine has already been through the
"Factory Restore" operation and it is ready for shipping to a customer.
We have a LCD on the machine. If the unit gets hosed in the field., the user
can perform a Factory Restore using the menu on the LCD. All we do when this
is selected is run diskpart and set the active partition to the WinPE
partition (Drive E) and reboot. The process above is repeated and the unit
is reset to factory new. This has worked great and manufacturing loves the
imaging process.
Now the problem:
I have to create a new RIS image because I have another motherboard to
support. This board has Broadcom Gig NICs.
Creating the RIS image as before fails because the Broadcom drivers fail in
the switch to text mode. Following instructions from Broadcom,
I created a ISO of the WinPE files. This image has the Broadcom NIC drivers
loaded using the drvinst.exe utility. In the RIS Templates\WinNT.sif file, I
specify the ISO image in the OsLoadOptions and provide the BootDevice
="ramdisk(0)".
The WinPE does start now from the iso image but it fails to process my
WinBOM.ini file. It does execute the proper Startnet.cmd from the ISO image
and WinPE looks like it is following a WinBOM.ini script but it is not my
script. There are no other WinBOM.ini files in the ISO image so I do not
understand what script it is running. The WinBOM.ini is in the same
directory as the factory.exe so it should find and use my file.
Any help would be appreciated.
Kevin C.
FYI: here is a link to the product:
http://viewcast.com/pages.asp?page=niagara-GoStream
Please advise if there is a better group.
Background:
I have used RIS to build my production machines and it works great. Once the
initial WinPE comes up under RIS, it runs my WINBom.ini file that creates 4
drive partitions. It goes on to copy another version of WinPE (basic, no
network) to one partition (drive E) and the future embedded image to one of
the other partions (Drive F). Drive F is used as the virgin "Factory
Restore" drive. It then sets the bootable partition to the WinPE drive
(Drive E) and then reboots the machine. The machine then comes up under
WinPE on the hard drive. That WinPE environment copies the embedded image
from the "Factory Restore" partition (Drive F) to the C drive to complete
the imaging process. Finaly, it sets the active partition to the C drive and
reboots the machine. The machine finaly comes up on the C drive and has a
freash copy of the embedded image. It runs through the FBA and then it is
ready for use. So at this point, the machine has already been through the
"Factory Restore" operation and it is ready for shipping to a customer.
We have a LCD on the machine. If the unit gets hosed in the field., the user
can perform a Factory Restore using the menu on the LCD. All we do when this
is selected is run diskpart and set the active partition to the WinPE
partition (Drive E) and reboot. The process above is repeated and the unit
is reset to factory new. This has worked great and manufacturing loves the
imaging process.
Now the problem:
I have to create a new RIS image because I have another motherboard to
support. This board has Broadcom Gig NICs.
Creating the RIS image as before fails because the Broadcom drivers fail in
the switch to text mode. Following instructions from Broadcom,
I created a ISO of the WinPE files. This image has the Broadcom NIC drivers
loaded using the drvinst.exe utility. In the RIS Templates\WinNT.sif file, I
specify the ISO image in the OsLoadOptions and provide the BootDevice
="ramdisk(0)".
The WinPE does start now from the iso image but it fails to process my
WinBOM.ini file. It does execute the proper Startnet.cmd from the ISO image
and WinPE looks like it is following a WinBOM.ini script but it is not my
script. There are no other WinBOM.ini files in the ISO image so I do not
understand what script it is running. The WinBOM.ini is in the same
directory as the factory.exe so it should find and use my file.
Any help would be appreciated.
Kevin C.
FYI: here is a link to the product:
http://viewcast.com/pages.asp?page=niagara-GoStream