Ghost Solution Suite

 View Only
Expand all | Collapse all

Multicard Template

  • 1.  Multicard Template

    Posted Jun 14, 2010 04:51 PM
    I have been trying to create a USB boot disk for a number of days now. Using the boot menu, I have selected the USB drive and it proceeds through the process of finding the NIC card but bypasses the NIC driver going through every driver on the card and reporting that the driver was not found. I have checked this on multiple machines with multiple NICs. All do the same. Do I need to create the autoexe.bat and and the config.sys files and add them to the boot disk. I am using GSS 2.5 and XP pro computers. I have read that to do this manually I need to edit the autoexe.bat and the config.sys files but I do not find them on the boot disk.


  • 2.  RE: Multicard Template

    Posted Jun 15, 2010 04:37 AM
    Are you trying to create a DOS bootable USB key?  (as you refer to config.sys and autoexec.bat)
    Frankly, the ability of DOS to support modern drivers is quite limited, so I would strongly recommend using WinPE as your boot environment and then you can use the appropriate Vista drivers for your various NICs. 


  • 3.  RE: Multicard Template

    Posted Jun 15, 2010 09:19 AM
    We have no modem in the district. Yes I am trying to create a DOS bootable USB key, just with multiple NIC cards.


  • 4.  RE: Multicard Template

    Posted Jun 15, 2010 09:29 AM
    Hi there,

    I totally agree with EdT here... WinPE is definitely the best option. If you find you need to add newer drivers to the multicard template, here is an article that may help:


    How to manually add a NIC to the Multicard Template

    Thank you,

    Randy


  • 5.  RE: Multicard Template

    Posted Jun 15, 2010 10:03 AM
    I wrote MODERN and not MODEM !!

    For a DOS boot environment that supports huge numbers of NICS, have a look at:  http://www.netbootdisk.com/

    You can then use the HP utility for making USB sticks DOS bootable and add the netbootdisk stuff onto the flash device. Just be aware that depending on the way the bios works on your various systems, some may mount the USB stick as drive A  (recognising it as a floppy disk) and some systems will mount it as drive C (recognising it as a hard disk). So any batch files you use need to figure out what drive letter the USB stick mounts as.

    However, it is soooooo much easier with WinPE that you would be much better off just working with that instead of DOS. Since most hard disks and optical drives are now SATA, your DOS boot is pretty much worthless now, as DOS cannot work with SATA devices unless you switch them to IDE emulation in the BIOS first.


  • 6.  RE: Multicard Template

    Posted Jun 15, 2010 10:30 AM

    First off thanks so much for your help. Now you have sold me on the WinPE solutions. Is there a whitepaper on how to set it up? I have gone through the wizard but I see no where to add drivers.



  • 7.  RE: Multicard Template

    Posted Jun 15, 2010 10:39 AM
    Here are the articles you should use:
     
    Why does Symantec Ghost need drivers for Windows Vista when imaging some other operating system?
    http://service1.symantec.com/support/on-technology.nsf/docid/2009061216045160
     
    How to get started in Ghost Solution Suite 2.5 with Boot Disks and the Ghostcast Server
    http://service1.symantec.com/SUPPORT/on-technology.nsf/docid/2009052715374860

    Thank you,

    Randy


  • 8.  RE: Multicard Template

    Posted Jun 15, 2010 10:41 AM
    Search the Articles forum on "WinPE"  and maybe throw in drivers as a search term. There are plenty of articles on all aspects of WinPE and its usage.


  • 9.  RE: Multicard Template
    Best Answer

    Posted Jun 15, 2010 10:45 AM
    Thanks a bunch I will try these out. I do appreciate everyone's help. I am glad to say that I did finally get a DOS USB bootable stick to work. But there is nothing wrong with having two options. EdT I do apologize for my misreading of your message about modern NIC drivers.


  • 10.  RE: Multicard Template

    Posted Jun 15, 2010 11:09 AM
    The solution referred to in the document by Randy above was the one that worked us - we needed to stay in DOS for various reasons (other tools we have that work in DOS and are a part of our boot usb).  I don't want to repeat the solution here but would just add an example of a line from one of our mcassist.cfg files

    PCI-TAG = 8086 10BD : Intel 825xx Gigabit$