You definitely need to get the latest NDIS2 driver for that card (new as of last week):

http://downloadcenter.intel.com/Detail_Desc.aspx?ProductID=749&DwnldID=4239

Execute the prodos.exe to extract it and add it according to these instructions:

http://service1.symantec.com/SUPPORT/on-technology.nsf/docid/2000011211551725

Also, add these command line switches in the Parameters line in the boot wizard:

-FNI -NOIDE

This should take care of that.

Thank you,

Randy

so i got the driver added it- do i need to go into advanced when adding e1000.dos?

also where do i add fni-noide?

now i'm going to get the pc where i need it and create the image.... thanks randell, i guesse i didnt have the fni-noide added or i was using the wrong driver.

i added the switch the the bootini and the config.sys

wasnt sure which one did it

The switch is typically added in the Parameters line on the page that specifies the location of Ghost.exe. This prompts the boot wizard to add that switch after the ghost.exe entry in the Autoexec.bat file.

If you are using Ghost Solution Suite 2.5 then you can also make use of WinPE. If you are at Ghost Solution Suite 2.0 then you can use this document to create a WinPE boot package:

Title: 'How to build a Windows PE [Vista] CD/DVD that contains Ghost32.exe and then join a client machine to a Ghost Cast Server session to create or restore an image file.'
Document ID: 2007120608081560
> Web URL: http://service1.symantec.com/SUPPORT/on-technology...

WinPE offers greater supportability for newer hardware such as SATA.

so i created the winpe boot disk and it loads into ghost but when i try and connect to the ghost server it says it can not connect and tells me to make suremy server is accepting clients, then with the same server session open i boot with the disk i created using the above drivers and it connects just fine. is there any way to add the drivers and the autoexec switch to the winpe disk?

You will need to update the NIC driver. Make sure that you get the Vista driver and use this document to import the driver:

Title: 'How to add drivers to DeployAnywhere or WinPE.'
Document ID: 2008050916132860
> Web URL: http://service1.symantec.com/SUPPORT/on-technology.nsf/docid/2008050916132860?Open&seg=ent

Then after importing create a new boot disk. Let me know how that goes.

i'll add them and let you know how it goes. the only wierd thing i think is that nornmally when the nic driver doesnt load the unicast option is greyed out, this time it was there just would not connect.

when you say add the vista driver as oppossed to the dos drive i am assuming that is because the boot disk boots into a windows env as oppossed to a dos env?

the only driver i found on the site was an installer package and i cant figure out where it is extrating the files to. can i just drop the installer package in the boot disk?
http://downloadcenter.intel.com/confirm.aspx?httpDown=http://downloadmirror.intel.com/12200/a08/PROVISTAX64_v14_0.exe&agr=&ProductID=3003&DwnldId=12200&strOSs=&OSFullName=&lang=eng

Randall,

The instructions you provided worked perfectly.

Thank you very much!

thx dude for this information
this rweally works
thx a lot

Randall,

My copy of ghost boot wizard splits up the ghost.exe file across the two disks.  This makes it diffucult for me to create the ghost boot CD since  the ghost.exe that is located on my machine is larger than 1.44mb.

This also prompts me "Please insert the disk with the 2nd segment etc etc" over and over again with the second disk inserted.

How do I make Ghost Boot Wizard not split up the executable?

across two floppy disks?  You can't keep it from splitting it up.  The executeable fills one disk and you need the other for drivers etc...

The entire ghost executable is usually located on the second floppy the process creates(at least in my experience).  I don't know why it's splitting it up into mutliple files.  If I didn't format the old floppies to make this new boot disk I would have the whole ghost.exe

hindsight is 20/20

What I am saying is that the ghost.exe executeable file is 2.2MB in size.  BIgger than a standard floppy.  Time to updgrade to CD boot or USB boot.

Yes, the executable is larger than a single floppy. JPomper, you said you were having difficulty making a boot CD becuas eof how Ghost splits files writimng to a floppy... how exactly are you trying to make a boot CD? The boot wizard will allow you to either make CDs directly (GSS 2.5) or make an *.ISO that you can burn to CD. This would be the method for creating a boot CD that you should be using.

Randall,

**EDIT**

Okay I r dumb.  There is a way to make an image right out of Ghost 11 and wouldn't you know as soon as I saw that iso radio button and tried out the image everything works just fine.

I can't believe I've never seen that.

Randall - I followed your advice and downloaded the driver from Intel but when I loaded it in the boot wizard I'm receving "failed to import" driver message. Please advise.

If you are getting that error, make sure you have ran all three LiveUpdates. The version on the Ghost Explorer utility will read 11.5.0.2165 after all those updates are applied.

Randall - I ran the updates but I'm still receving the same error. Here's a list of the following files listed in the directory.

e1000.dos
e1000odi.com
ipxodi.com
lsl.com
net.cfg
oemsetup.inf
protocol.ini

Am I missing anything?

Open up the boot wizard and modify the template that you added. Make sure the that this is what you see:

Filename: e1000.do
Driver name: e1000$

The driver name box requires that specific syntax. Alternately, try adding the driver again and making sure you are adding it as an NDIS2 driver, and that the syntax matches the above.

Thank you,

Randy

Randall - Disregard my last message after tinkering around with a few different configurations I got it to work.  Thanks for you help.