Ghost Solution Suite

 View Only

  • 1.  Image creation of E520 - Intel 82562V 10/100 NIC

    Posted May 24, 2007 05:37 PM
    I am having a problem where the NIC is not being recognized within the Ghost console (GSS 2.0).  I tried using the suggestion from the Symantec solution below:
     
    Solution ID: n2002100414292225
    Document URL: http://entsupport.symantec.com/docs/n2002100414292225
     
    However, the PRODOS driver that worked for the Dell 5150 PCs I just created Images of did not work for the E520s.
     
    The 5150s had an Intel Pro 10/100 card in them of some sort and worked fine like I said.
    The E520 has an Intel(R) 82562V 10/100 card.
     
    Could I have done something wrong with the PRODOS drivers from Intel when I modified the NIC templates in Ghost?  or was I right in assuming they SHOULD use the same driver set?


  • 2.  RE: Image creation of E520 - Intel 82562V 10/100 NIC

    Posted May 29, 2007 12:25 AM
    Hi,
     
    It seems that you've replaced .ini and .cfg files that are part of the template with the files that were provided by the driver manufacturer.
    The .ini file that we are using in a ghost template calls protman.dos (protocol manager) file this is used by ghost to identify the NIC.  By replacing it you prevent from ghost the access to the right driver.
    In case where you need to update the driver you only need to replace .doc file and leave other two that we provide.
    Hope this was helpful.
     
    Cheers,
    Orah


  • 3.  RE: Image creation of E520 - Intel 82562V 10/100 NIC

    Posted May 29, 2007 09:35 AM
    I've actually had this problem solved now after an extensive phone call to Symantec for some help.
     
    The problem is that the storage controller and the NIC are on the same IRQ in these Dell Dimension E520 PCs.  If you use the alternative Universal Packet Driver v2.0 with the irqcfg option it will work, as it will attempt to change the IRQ of the NIC.
     
    We had went through several Intel drivers, several switches and tried the standard Universal Packet Driver v2.0 several different wells as well.  After tabing through the reboot we were able to find out that the IRQ was the problem.