Ghost Solution Suite

 View Only
  • 1.  Symantec Ghost Runtime Error when adding a DOS driver template

    Posted Apr 25, 2012 09:25 PM

    Hi All - 

    I've just purchased Symantec Ghost and have it installed on a server running Windows 2008 Server R2.  I'm using this to deploy about 70 new machines in my office and unfortunately the Dell network driver as not automatically found when adding the first machine to the console in order to create an image.  

    When trying to add the DOS network interface I get the following error and I'm not sure how to resolve this.  

     

     

    Does anyone know how to get this resolved?

     

    Thanks,

    -Dom



  • 2.  RE: Symantec Ghost Runtime Error when adding a DOS driver template

    Posted Apr 26, 2012 06:09 AM

    DOS has no support for modern hardware. Move to WinPE as I am sure you will find it much more compatible with your hardware.



  • 3.  RE: Symantec Ghost Runtime Error when adding a DOS driver template

    Posted Apr 26, 2012 07:57 AM

    EdT - thanks again for the response as you posted on my other thread.  I've tried using WinPE but nothing happens and it just fails.  Ghost is using the Universal Driver.  



  • 4.  RE: Symantec Ghost Runtime Error when adding a DOS driver template

    Posted Apr 26, 2012 09:26 AM

    Download the correct Vista 32 bit drivers for your NIC hardware and add those to WinPE using the Ghost Boot wizard. Make sure the drivers added are then selected before rebuilding your WinPE image. The following tech note may be helpful:

    How to make a Windows PE boot package with the Ghost Boot Wizard.



  • 5.  RE: Symantec Ghost Runtime Error when adding a DOS driver template

    Posted May 01, 2012 06:46 PM

    Uninstall and reinstall the application and if you still get the Visual C++ error,check if you get the same error with WINPE.If yes,check if the machine is part of domain .If yes, remove it from domain and then try to manipulate Boot Wizard.If this resolves , probably there is a GPO which is preventing from you to manipulate boot wizard.Also check if there is a security software inistalled on the server and disable the same to see if it makes any difference.

    Patch 2269 could also be the solution.