When booting from the GX260 ghost boot disk it finds the network card goes through logging itself onto the client computer mapping the G drive and then when trying to run ghost.exe it just hangs. If i try going through the ghost wizard and load in the ndis2 drivers it asks for an oemsetup.inf file which we dont have or know wher to get .
So we have just used the e1000.dos driver that we have .
When using the boot disk it then it comes up with NDIS2 Environement paremeters are invalid after starting PC dos.
We have tried copying the gx270 e1000.dos file onto the gx260 ghost boot disk but it still does not boot it just hangs at the same point .
When checking in manage in computer managemnt and shard folders it does not say the file is in use so it looks as though it is not actually loading the file.
Anyway the only way we can think of getting around this is to install another network card to make an image.
It does not appear that Dell users are knowledgeable in the workings of Ghost Corporate Edition. What you are dealing with seems specific to the Ghost application and I'm thinking you might get more help by talking to Symantec. A telephone call may help the best, but here is a link that allows you to send your post to them for review and comment (step 2):
I agree with you that doing a simple ghost image should not be complicated. Sam is an IT Admin who is imaging systems on a network and I'm sure he wants to do it as advertised rather than run from machine to machine.
I am having the exact same problem. Ghost used to work before just fine on the Optiplex 260, but since they switched to the 270 model it just hangs. I tried both geting to the ghost image on the server, on an attached HDD or on the cd-rom. The problem is not the network boot floppy. The ghost application just hangs - never starts up. Any idea what might have changed between the Optiplex 260 and 270 model? Anything funny in the bios? I have looked around but am not able to find anything. Did anyone manage to run Ghost on one of the new Optiplex 270's?
If you go to the link in my post at the top of this thread and put GX270 in the search window (step 1), there appears to be a lot of discussion going on relative to this issue. Apparently there is a patch for Ghost 7.5 that corrects this issue, but Symantec does not want to publish a link to it. They are requesting that users call Enterprise Technical support at 800-927-4017 to make arrangements to acquire the patch.
1. Download PRODOS2.EXE from Intel http://downloadfinder.intel.com/scripts-df/Product_Search.asp?Prod_nm=PRODOS2.EXE 2. Extract to an empty directory. 3. Run Ghost Boot Wizard (Network Boot Disk) and choose the Intel Pro1000 template and click the MODIFY button on the left. 4. Click BROWSE and find the folder that you extracted the ProDos drivers to. 5. Select the E1000.dos driver and click OPEN. 6. Click OK. 7. Click NEXT. 8. Use PC-DOS or MS-DOS (Your preference ... PC DOS is already selected in most cases unless you want to grab the files from a bootable 98 disk.) 9. Click Next. 10. IMPORTANT!!! In the parameters field type "-fni" without quotes. (Disables IDE Direct Access on new Intel Chipset) 11. Click NEXT. 12. DHCP if you have the server running somewhere or modify for static entries. 13.The rest is history .. format / create floppy / .etc
Thanks for the pointer Jamie as it helped me with the same problem. However, the -fni switch should not be inserted how you describe. You should create the disk as above (without the -fni parameter as this only modifies protocol.ini). Once created, edit the Autoexec.bat file and put the -fni after the Ghost.exe i.e.
I Ran into a support article at symantec's sight addressing imaging dificulties that apply to the intel pro 1000 adapters. They provide an updated driver solution see link below Ghost version 7.5.
Craig_Martinsen
122 Posts
639
0
Posted September 21st, 2003 02:00
Sam,
It does not appear that Dell users are knowledgeable in the workings of Ghost Corporate Edition. What you are dealing with seems specific to the Ghost application and I'm thinking you might get more help by talking to Symantec. A telephone call may help the best, but here is a link that allows you to send your post to them for review and comment (step 2):
http://servicenews.symantec.com/cgi-bin/browse.cgi?group=symantec.support.network.ghost75.general&product=symghost&mini_version=symghost_75&tpre=ep
Craig