Ghost Solution Suite

Trying to create bootable USB drives for multicast and peer-peer ghosting. Not able to initialize cards in order to get IP Address. Tried PC-DOS and WinPE with drivers directly from Dell and Intel. All kinds of issues with both. Any suggestions, help, ideas?

Using Ghost Solution Suite 2.5.1, Console 11.5.1.2266.
 

Are you adding the Windows Vista 32bit drivers? These are what WInPE uses.

Thank you,

Randy

Found anything new for PC-DOS?

Thanks

PC-DOS is unlikely to work at all due to the SATA controllers. 

I booting the PC-DOS from CD, haven't even got load the network card or Ghost yet, just hangs on the PC-Dos cursor.

When I changed the settings it worked, but did it again and now it only works randomly. You think its a Dell issue, it works with our e6500?

How do you load drivers when using WinPE? When I build a boot disk using WinPE there is no option to add specific drivers (that I know of).  Unlike when building a MS-DOS package how there is the option to pick a specific driver.  If there is a way to specify Vista drivers for WinPE could someone point me in the right direction?

As it stands right now I can boot up in WinPE but there is no network activity, the switchport doesn't even show a MAC address for the port this laptop is on.

Thanks

Hello,

When using WinPE, you don't choose a specific driver, but WinPE dynamically assigns a driver from its library. Here are instructions for adding the drivers:
As for the network cards, you will need to check the device manager and download the latest Vista 32bit drivers from the specific manufacturer. 

I hope that helps!

Randy

We just received a shipment of E6410 and E6510. I changed the SATA settings, and that did not help. Is there a solution to this?

Before adding the drivers.
Make sure that you are adding the correct drivers.
To ensure after downloading the drivers match the Device_ ID & Vendor_ ID in the .inf file.
You can get this information Start-> Run->type msinfo32.exe.
You will get the System Information page.
Select  Components-> Network -> Adapter.
You need to locate to Ethernet Adapter type.
In that Pnp Device ID : You can see your network card's Device Id ( dev_Id) & Vendor ID ( Ven_ID).
Once we confirm you can add the drivers and create the WINPE package.
Get us the device id and vendor id will tell you the link to download the driver.

thanks
Sockkalingam.S

Thank you for the reply sockkalingam, and once I can get the CD to boot I will make sure we do that.  However, the problem begins with the fact that we can't even boot to the CD. The same as the other comments above.  It just either sits at a blinking cursor or says invalid boot disk.
Thank you.

I'm sorry, I neglected to include the NIC info as you requested.
PNP Device ID PCI\VEN_8086&DEV_10EA&SUBSYS_040A1028&REV_05\3&11583659&0&C8

We have successfully created and used a boot disk for the Latitude E6400 and E6500 with what I believe is the same NIC. But the E6410 and E6510 will not even begin to boot from the CD.
Thank you.

Look for and remove the mouse.ini file created by the ghost boot wizard. For what ever reason that seems to be the issue with E6410 and E6510 machines. Once that file is removed, you will need to navigate with the keyboard, but at least you should be able to ghost your machines.

ourcats5

Thank you for your responses. I got it to work. Here is how.  I updated our installation of Ghost Solution Suite to ver 11.5.1.2266 so that I could create the boot disk using WinPE.  I edited the WinPE configuration to add the Nic (Intel.82567LM.3) for my operating system and on the Storage tab, I added the ATI.SATA.AHCI_32.  I first tried building a bootable USB and I was unsuccessful. I got error messages stating that the winlogon.exe was missing. I didn't spend a lot of time troubleshooting this. I went back to my old stand-by method of booting from a CD. I created an ISO and burned a bootable CD. Worked like a charm.

I just want to clarify my last post a little bit, in case someone else is able to use this information.

I had a slight issue connecting with the NIC that I specified above "for my operating system".  While 'my' operating system for that computer is XP, what the Windows PE boot disk needed for network drivers was the Vista 32 bit driver. I found that in another post, when researching my problem.

So, to summarize, i updated our Ghost Suite to the most current version, made a Windows PE Ghost Boot Disk, edited PE to include the Vista 32 bit drivers for the 82557LM Gigabit NIC card and I added the storage support for the ATI.SATA.AHCI_32.  

I made an ISO image and burned a CD. I am now happily taking an image with this CD.

Hi

Iam glad that you fixed the problem that you had with you had with your E6410 and E6510 machines.
Adding to your comments the below link will explain all as why does Ghost needs Vista drivers when imaging other operating systems.

http://service1.symantec.com/support/on-technology.nsf/docid/2009061216045160?Open&seg=w

If this post is helpful to fix your issue extending it will also be appreciated if your mark it as helpful.

Thanks
Sockkalingam

Thanks this worked great for me!!!

Thanks

Hello All,

Had the same problem with Dell 6510 Win 7 32 bit laptop with Intel 82577LM Gig controller.

When building the jump drive edit the config file and remove the line about mouse.com them it boots with no problem.


 

PC- DOS
Network Boot Packet
Intel 82577LM NDIS
Start editing
Config File
Remove

if exist MOUSE.COM MOUSE.COM

 

The mouse fix is working for me.  One problem....

I am running Ghost ver 11.0.0.1502.  I downloaded the latest Intel 82577 ndis drivers & have successfully imaged a single laptop by booting from a USB drive.  When I try to unicast to > 1 laptop the session terminates with a 19905 error.  I have been imaging multiple workstations in this manner for several years on our network with no problem.  So for testing I just imaged multiple Latitude 505s with no problem so this is not a switch issue.  I notice when the ndis driver loads on the 6410 it will only run at 10 mbps no matter what configuration I specify.  Switch is a gig.  I'm wondering if this is the problem?  Anyone able to image multiple 6410s?

WY-Tech,

I used Intel 15.2 from intels web site but I'm using 11.5.1. I did have problems with the earlier version of ghost with Vista so I upgraded.

I am reading thru the posts and I must say that it's a little difficult to follow....
I would like some assistance with figuring out just how I can remove the
if exist MOUSE.COM MOUSE.COM
Line in the AUTOEXEC.BAT config when using the Ghost Boot Disk Wizard.
If possible, I need either the exact location of this file so that i can edit it out or if that's not possible, I need to know exactly what I will need to do.

Thank you all in advance.

Hi,

Once you navigate the screen in the Ghost Boot Wizard you will have a screen called review page where you will have a tab called as START EDITING.
Click on START EDITING and delete the line and click on STOP EDITING and then proceed in creating the boot disk.
Don't forget to click on Stop editing.

Thanks
Sockkalingam

Sockkalingam,

I don't happen to have the START EDITING button. I am using Ghost 11.0.0.1502, do I require an update? If so, where can I get this update and is it a free update or one that must be purchased?

Thanx,
Alpa

Hi,

Follow the instructions in the document given below,

http://service1.symantec.com/support/on-technology.nsf/854fa02b4f5013678825731a007d06af/974fe1f8a70ae4a180257768003b619e?OpenDocument

Hope this helps

Regards,
Prasanna Rajagopalan

Unfortunately this did not work... :-/
I get stuck at  Starting PC DOS....
When I press F8 or Ctrl-X nothing happens.

Thanx for the suggestion

Hi Alpa_Chino,

You could give it a Shot with WinPE as it would have a greater support for the Mass Storage drivers which PC DOS lacks.

Hope this helps !

Hi Alpa_Chino,

If you are still at the version of 11.0 you would need to update to the latest version of Symantec ghost 11.5 to be able to use WinPE as the version 11.0 would not have it.

Are you using a jump drive or CD? because you can probably just remove that line in the config file after you create the network boot jump drive..I haven't used 11.0 since we went to Vista and Win7. Below is my ghost ISO before I burnt it.....
Network Driver:

Template: Intel 82577LM IBM

Driver: E1000.DOS

Driver Type: NDIS2 Driver

Configuration Files:

AUTOEXEC.BAT:

@echo off

SET TZ=GHO+05:00

prompt $p$g

\net\netbind.com

if exist MOUSE.COM MOUSE.COM

echo Loading...

CD \GHOST

GHOST.EXE

CONFIG.SYS:

DEVICE=\net\protman.dos /I:\net

DEVICE=\net\dis_pkt.dos

DEVICE=\net\E1000.DOS

LASTDRIVE = Z

PROTOCOL.INI:

[protman]

drivername=PROTMAN$

[pktdrv]

drivername=PKTDRV$

bindings=nic

intvec=0x60

chainvec=0x66

[nic]

drivername = E1000$

Hi Alpha_chino,

You can try to  upgrade yourproduct from 11.0.0.1502 to 11.5.1.2266 by logging to www.fileconnect.symantec.com
Enter your serial number if you get an option for downloading 2.5.1 thats the latest version.
Else you can contact the licensing team and they will assist you to upgrade.

The above message about the config change on a jump drive was a reply to Alpha_chino. I hope this helped...

 

Hi Mr. Sockkalingam,

          I got my Dell Latitude E6510 Device driver and Vendor ID. Please provide me the link to dos driver for creating Dos bootable floppy disc. I m using Symantec ghost boot wizard for creating bootable floppy disc.

Ethernet Adapter type: 802.3
Name: Intel centrino Advanced N 6250 AGN
Device ID: 0087
Vendor ID: 8086

Raviteja Kancherla,

I have never tried to use a wireless adapter to ghost but it would be of interest to me. If you ever get it to work please post results...


The Bear 8 

Hi Raviteja,

You can download the drivers from the below given link.

https://www-secure.symantec.com/connect/downloads/pc-dos-nic-drivers-intel-7132010

Thanks

But the drivers doesnt suit for the Device ID 0087...It satisfies only with 8086. I even tried a lot.. Not working. Error no. 33 unable to bind. and it says some wrong NSID environment

Hi Ravi teja,

Is it a Wireless network card?

No. It is an ethernet. I have given the adapter type, device id and vendor id in the above post

Hi

I had a look at your previous post earlier and when I searched in Intel it showed as Wireless card.
Thats the reason why i asked you that question.
Most of the Device Id's will be a alpah-numeric ID.
Out of the four characters say for example 1st two will be numbers and 2nd two will be alphabets.
For example : 10EB, 10EA .......
If you can confirm me the device ID once again it will be helpful.

Venkatanathan,

I am still on 11.0 and after putting in a call to Symantec, it would seem that my company no longer has a support contract. I was informed that I would not be able to upgrade due to needing a license to do so.. Is this correct? If so, I would need assistance with creating a DVD with my image on it so I can use the DVD to image the machines without the use of my ghost cast server.

Intel 82577LM Gigabit Network Connection
Vendor ID: 8086
Device ID: 10EA

Hi Ravi,

Below is the link for you to download the WINPE drivers for Intel 82577.

https://www-secure.symantec.com/connect/downloads/nic-drivers-intel-82577-82578-792010

Below mentioned document will help you in How to add drivers in WINPE:

http://service1.symantec.com/support/on-technology.nsf/854fa02b4f5013678825731a007d06af/e4c1aea6046866e288257444007f9333?OpenDocument

I need the DOS drivers and it worked from the previous link you gave to me. But it is hanging and is unable to establish contact with session and hanging up. Do i need a patch 2269 for Ghost suit 2.5? If so, please send me the patch. Thanks for the help..

Hi Ravi,

If the process is getting hang at the beginning stage of DOS then we need to use WINPE.
If not let me know at what point of the process it hangs.
Lets try WINPE which should fix your issue I believe.

i removed the mouse support from the boot disk per ourcats5 suggestion and verified the DOS based boot disk working on both Dell Latitude E6410 and E6510 laptops using the universal NDIS driver and PXE booting

Ghost Start with my USB key by remove the file "mousse" !

 

Extra, perfect, Tank's

If the CD uses the SATA interface, you will not be able to mount the CD as mscdex.exe and the standard CDROM drivers that are used with PCDOS do not work with SATA.

PCDOS is increasingly useless at handling modern hardware so moving to WinPE is really the best step forward.

I'm trying to capture an image in PC-DOS NETBOOT with the Dell E6400 and I've had no luck at all. I've downloaded drivers from Intel and Dell...nothing. I'm creating a VPartition and everytime I map the system back and click on the VPartition it reboots and gives me the same error over and over again. We use Windows XP and the Ghost version is 11.5.1.2266.