Drivers Could not be found in the PreOS
Hello,
I am having trouble getting past the following error message:
Details for: To Virtual Partition
Drivers could not be found in the PreOS for the following devices:
Manufacture: "Intel", Description: "Intel(r) ICH9M-E/M SATA AHCI Controller", PCI Vendor: 0x8086, PCI Device: 0x2929, PCI Subsystem: 0x2631028
I am trying to create an image from a Dell Latitude E5500 to push down to 2 more E5500's.
I have added the correct driver (verified by Dell) to the PreOS (WinPE-512) for my operating system (Windows XP SP 3) that runs on the laptops and I got the same error message.
Eventually, I just added the PCI information to the skip.pci.manifest.txt file in this format:
{
0x8086 = {
0x2929 = (0x2631028)
}
}
then refreshed the WinPE-512 image, and I STILL get that error.
This is pretty much a fresh install of Ghost Enterprise edition we purchased 3 or so weeks ago. I have run live update and updated the program. My ghost console tells me it is program version 11.5.0.2113. I am running the console on a Windows server standard 2008 (32-Bit), Dual 2.0 Xeon processors, 4 Gig RAM.
I am totally lost and don't know what to do. If you can shed any light on this, I would GREATLY appreciate it.
Thanks in advance!
i have some 5500's
and about 30 other models. i ALWAYS use the dos based driver and it always works on everything. the symantec guys will tell you there is a performance hit but i can shoot these images down at over 600mb/min
Thank you
Kurbycar,
Thank you for your sugestions. I am going to try and get this skip.pci.manifest.txt to work. If I can't, I am going to follow your lead and try to get the DOS version working. Would you recommend the DOS or PC-DOS PE?
Thanks again
David
Hi Vining Sparks, If you have
Hi Vining Sparks,
If you have run Live update then you can check whether you Ghost boot wizard of build 2165 (I think that what it should be). If it is anything but 2113 then you can use skip.pci manifest file and refresh will work with your Winpe. You need to know that manifest files are not text files even though they appear as such. They are serialised hashmaps so having bracket in the wrong place can lead to file not being read and interpreted. You can verify whether skipped device has been inserted by opening device.manifest.txt in the Winpe folder of your choice and searching for this device tag that you inserted. WInpe folders are located off the same folder where skip.pci.manifest file is.
Generic AHCI driver that is present in Winpe is usually sufficient to handle AHCI controller but some may be special. Virtual partition code cannot tell which one will work and which one will not so it compains of any missing storage or NIC driver. For NIC you need to have at least your primary NIC driver.
As to the speed - you can get good speeds from DOS as long as your driver performs well. Generally you get much better performance out of Windows drivers and for big cloning operations (like cloning Vista) you will get better performance using Winpe with longer startup than DOS.
Thank you
Thanks for the info Eugene. I got that particular error message to go away, now I am dealing with an error message that says "Failed to reboot client to recovery partition"...
I have done some research on this on the symantec website, and it appears that this is a network connectivity issue. I am pretty sure I am using the correct network driver though. Any thoughts on that one?
thanks again for your help and for your responce!
David
Hi David, I suggest you build
Hi David,
I suggest you build standalone "one click virtual partition" WInpe based boot package from Ghost boot wizard, take it to this machine and execute. It will tell you on the command line if there are any problems. One-click VP package is just a zip file with exe to run it. You can add your user files to it as well but you need to modify manifest.txt inside zip file.
Also when you are executing task from the Console you can right-click on failed task step and get additional error information.
Failed to reboot client most likely is not related to NIC driver. I would say it is either privilege (Vista?) or not enough disk space or very fragmented volume to create virtual partition but executing VP package should tell you what it is.
Thank you!
Hello!
I got the PC-DOS VP working last night. It connected to my server and pulled an image. I actually was able to put that image on another computer, but had an IP address conflict when it came up. I think I am using the same windows key also. I am going to investigate what went wrong here in a few.
Thank you very much for your help. I am truly gratefuil!
Dave
Would you like to reply?
Login or Register to post your comment.