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.
wowza.. after readin like a million different replies on how to do this... - Jamie your steps had me whisk right on thru ,y set up and off to imaging my GX270s in not time flat... thanks a million....
Just as i tweaked my 7.5 and got it working My CO. got in 8.0 hehe... gonna install it and see if switch is still needed.. or if it was corrected in this version...
I am able to boot to that, but the problem that I have now, is that it takes about 8 reboots before it will actually authenticate to the server and give me access to the network resource. I am having the same problem with other non-sx270 systems also. I have emailed symantec about this, but suprise suprise, I have not heard anything back
Craig_Martinsen
122 Posts
0
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
speedstep
9 Legend
•
47K Posts
0
September 21st, 2003 15:00
Just Ghost an Image File to a Hard drive and then unplug the cdrom temporarily while the drive to drive ghost happens.
Then put back.
Voila Done.
Craig_Martinsen
122 Posts
0
September 21st, 2003 16:00
SpeedStep,
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.
Craig
astanoi
1 Message
0
September 22nd, 2003 18:00
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?
Thanks.
Craig_Martinsen
122 Posts
0
September 22nd, 2003 23:00
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.
Craig
jkd740
7 Posts
0
September 24th, 2003 15:00
Solution:
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
- Jamie
DonkeyDerby
3 Posts
0
October 1st, 2003 13:00
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.
GHOST.EXE -fni
--DD--
Sam pollard
7 Posts
0
October 3rd, 2003 09:00
Cheers the FNI Switch worked a treat.
Thanks Again
Sam Pollard
gras01
1 Message
0
October 31st, 2003 09:00
This is a known problem with Dell GX270's. Once ur bootdisk is made open it up and edit the Autoexec.Bat file.
On the line were Ghost.exe or ghost appears, do a space and then type -fni. Save the file and then boot with the disk. Ghost should load.
Cheers
BaileyJohn
5 Posts
0
October 31st, 2003 17:00
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.
http://service1.symantec.com/SUPPORT/ghost.nsf/8477deaaaafc102288256b1e00704619/04696d164d79d33c88256c4800758e95?OpenDocument&prod=Symantec%20Ghost&ver=7.5&src=ent&pcode=symghost&dtype=corp&svy=&prev=&miniver=symghost_75
Johnny
jkd740
7 Posts
0
November 21st, 2003 18:00
marroyo
7 Posts
0
November 21st, 2003 18:00
marroyo
7 Posts
0
November 24th, 2003 10:00
Just as i tweaked my 7.5 and got it working My CO. got in 8.0 hehe... gonna install it and see if switch is still needed.. or if it was corrected in this version...
chadswartz
1 Message
0
January 10th, 2005 18:00