Leo
Finally got this test done--and on my system there was no problem for Ghost to continue uninterrupted from one Ghost file to the next.
My setup was different from yours because I'm using Ghost 2003 and not enterprise Ghost 8.x. My Ghost Boot Wizard can not create a boot disk that supports CD/DVD and Network support on a single boot disk--it's one or the other--but I noted on your boot files that you had disabled any network support--so essentially your boot disk was for CD/DVD support--which is what I created and used.
As my restore continued, I pondered what else could be causing your experience to be different from mine, and I came up with a couple thoughts:
1. When I create my initial Ghost image file set, I used the default setting of Ghost 2003, using the DOS executable locally, and saving to a second internal HDD. The only *Option* that is selected is *-auto* for automatic naming of spanned files.
The *Option* for spanning (-span) is not selected--that is used, apparently, if you are going to run out of room at your initial location (volume) for an image file set, and you will need to specify an additional location (volume) for additional image files (example--using a Jaz storage device and having to put in a new disk once the first is full).
But, when restoring, if an image set is made with the spanning *Option*, I think you are then forced to specify each new image segment at the end of the previous segment.
Did you have the spanning *Option* selected?
2. File naming: my image set consisted of three files. The first two were approx. 2 GB in size and the final was about 400 MB.
When Ghost 2003 auto names the spanned files, it tacks on a 4 digit sequential number at the end of the file name and uses the DOS 8.3 naming convention. The first file created with Ghost can potentially have a *long file name* when setting up the Ghost procedure--but the spanned files will not--Ghost only retains the first 4 positions of the name and adds its 4 digit number.
Because of this, I always create file names that are a max. of 4 positions--I actually use a two digit month and two digit day as file names. That way the file name is never truncated or over-written by Ghost's naming. So my files today would be named:
0228.gho
02280001.ghs
02280002.ghs
3. You can not use Ghost's built-in ability to access optical data discs with a Ghost image on it, unless Ghost burned that image directly to the optical disc. You will get an error message right from the start saying it's not a valid Ghost image if you have burned the image file set first saved to a HDD and then burned to optical media using a third party burning program at a later time. But, you did not report that error--so this is not the issue--and you're boot files indicate you are loading those DOS optical drive drivers.
You can use that Ghost image, but only if you boot with DOS drivers that assign a DOS drive letter to the optical drive and you access the image file on the optical media via the DOS drive letter of the optical drive.
4. On my DVD, I placed the three image files in the root directory of the data portion of the disc. And *ghost.exe* was also in that same root directory--no sub-directories were used--but, based on your previous posts, it sounds like you did the same--so that's probably not an issue.
5. I used Roxio Easy CD Creator v5.xx--I don't know about v7.xx. But in the Ghost 2003 User Guide, it makes this comment about burning files to an optical drive:
Quote:If you use software to write an image file directly to the CD, you may experience
problems when restoring the image file. Software designed to write directly to a
CD, such as Adaptec Direct CD, uses a different file format. Therefore the copied
files are not recognized by Ghost.
If you are writing directly to a CD using third-party software, use a program that
lays out the format of the disc before it writes it, such as Adaptec E-Z CD Creator.
But, again, it doesn't sound like this is the issue either!
6. As I mentioned above in #1--I create the image file set locally on a second internal HDD--it sounded like you are possibly sending your image file over a network to a central server? Maybe that procedure somehow *breaks* the auto spanning of the files if they are then transferred to optical media and are not on a HDD still--grasping at straws here--don't know why that would be!
So, unless one of those items above is having an influence on your Ghosting, the only other item I can think of is that your optical drive is not *100 %* compatible with Ghost and spanned image files
Home
Pages: 
