GSS 2.5 wont boot into PreOS winPE
Hi,
I need some assistance. I have used GSS 2.5 flawlessly with other setups however this particular system setup it would not reboot into the PreOS.
We have the following system we would like to clone
HP z400
Intel Xeon Quad Core W3550
LSI SAS Controller 3041e-r running a 146GB Fujitsu SAS HDD
Broadcom 5764 gigabit onboard nic
Windows XP 64Bit
GSS client installs fine. However when initializing the task from Ghost console it updates the file and PreOS file, then timesout on the process to reboot into WinPE.
I have updated the WinPE image drivers for the Nic and LSI SAS controller with the latest for Vista. but nothing happens it stalls at that asame point.
Has anyone encountered this problem and know of a workaround? or is this because of the LSI SAS controller?
i have tested with a bootable CD running DOS version and it does recognise the HDDs.
Not sure where i am going wrong?...
Thanks in advanced. :)
There is no workaround. If
There is no workaround. If Console is telling you that you need NIC driver in WInpe then you need to download this exact NIC from manufacture and inject this driver to Winpe via Ghost boot wizard, Winpe editor dialog. Once it has finished compiling Winpe it is ready for you to use.
Please make sure to compare device, vendor and pic ids from INF files against what Console is reporting to you - they must match. INF file usually lists lots more IDs for a single driver but if at least onme is matching on everything reported by the Console then it is the correct driver. You can safely ignore subsystem IDs.
Thanks Eugene.. I have sorted
Thanks Eugene..
I have sorted out the driver for the NIC.
However, when executing the task it updates the files on client and PreOS files, but it does not reboot the computer at all. it just sits there waiting and then timing out.
Thanks,
I would say that one of two
I would say that one of two things happening: a) your system account on that client machine has very limited righs and cannot reboot computer b) you are running 3rd party software that is preventing ghost agent (running under system account) from rebooting your mahcine.
After further testing these
After further testing these are the following results. I would suspect it would be the NIC drivers and/or the WinPE
I have tested using the Universal NIC drivers and PCDOS and it works. ie the system reboots and loads up the ghost environment for imaging.
Going back to your inital response, regarding drivers.
Does it matter if there are several different Drivers from Broadcom being used? I am asking this as there are old Broadcom drivers listed and i've added the new drivers to suit the new NICs on the HP workstations.
However, I found a problem in the template folder where the NDIS drivers are kept the mcassist.cfg file does not contain the PCI TAG of the Broadcom NIC. I've entered it manually and it does give the option to select it on the Client tab of the computer's properties page.
I also have added the drivers for WINPE and rebuilt it.
What do you think i should do now?
Thanks
What is left that is not working?
From your last posting it would appear that you have the reboot working and have sorted out the NIC drivers, so I'm unclear on what is left that is not working as expected.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
NDIS and mcassist.cfg file
NDIS and mcassist.cfg file are for DOS drivers and have no relevance to Winpe. Having both Broadcom drivers in Winpe is generally fine with one exception: when older driver INF is matching hardware ID of the newer one but driver is not capable of supporting new hardware. In this case Winpe will simply match the first driver that matches device based on the INF file and will pick up incorrect driver. I'd suggest that you only use Broadcom drivers that you downloaded for your card and nothing else
Would you like to reply?
Login or Register to post your comment.