Ghost Solution Suite

GHOST.EXE is stopping to ask about spanning the image across drives. I have used multiple different commands in the GHOST.EXE line to no avail. The image files do not stop at the same size. One could be 35 mbss and the other 500 mbs and it will continue completing the image if some presses OK each time. I would like to have it setup so that there is no user interaction and GHOST.EXE can create the spanned images files automatically with varied sizes. Weird thing is that we have another model PC that runs the same script and it makes one file instead of spans. not sure what is causing this. Network maybe? Any ideas would be welcomed

ghost -clone,mode=dump,src=1,dst=g:\POSI2.GHO -SURE -FX -SPAN -AUTO -Z2  

Version of Ghost?

version is 11.0.1.1533

Are you running Ghost from a DOS boot, and also, can I ask if there is a reason you want to span images?

I am running GHOST from a virtual floppy disk. I DO NOT WANT TO SPAN the image but from some reason GHOST connects and then decides that there is not enough space to create the image file, but if i click OK to SPAN then it will continue in the same drive share that did not have enough space and make another image and then again it will state that there is not enough space and we click OK and repeat until image is done. I just want it to act like it used to and create one image, but for some reason it thinks the drive share is out of space from time to time and no standard to the image file sizes for the spans.

the issue appears to be related to a setting on certain Windows 7 machines. It must have to do with the network in some aspect on the Windows 7 machine.

If you are running from a virtual floppy disk, then presumably you are running DOS as your boot O/S. It is likely that your problems with spanning are due to the network client. If Ghost is unable to determine whether the target drive can handle files > 2Gb then it will use spanning to ensure that a valid image can be created.

For modern hardware, a WinPE boot solution is much more compatible as DOS has no SATA support. You could generate your own WinPE boot solution or upgrade Ghost to 11.5.1.2266 as this version has support for Windows 7 as well as including WinPE and Ghost Boot Wizard to enable drivers to be added to WinPE easily.

Also it needs to be borne in mind that because this process isn't using the normally recommended techniques (console management, GhostCast so it's using Symantec's code), it's entirely dependent on Microsoft's ancient DOS Lan Manager client interoperating with the back-end fileshare - and this has a *lot* of problems, far more than just not being able to work with >2Gb files or long file names.

Thanks for everyone's input. the issue that i was experiencing was that the PCs that could not be able to be ghosted to had CISCO's VPC CLIENT installed. Should have figured that out since it also causes issue with PC Anywhere once installed. At least with remoting out. The DOS VFD setup we have works wonders actually and we probably need to start looking at other options. Thanks again