> I created the original image using Ghost 2003 after booting to DOS and runing Ghost.exe.
Thanks; do you happen to recall whether you put the image on a local hard disk, or used a mapped network drive instead?
Unfortunately, the lead developer of the cloning engine was home sick today so I couldn't consult with him on this, because spanning is one of the more gnarly areas of Ghost. I've pulled the Ghost 2003 source code from the archives to get more familiar with how the process worked in the edition you have, but take this with a grain of salt since this is not the code that is my primary responsibility.
Anyway, it turns out that when restoring from a dumpfile, the flag that controls whether Ghost understands spanning comes from the header of the image file rather than from the normal settings. Now, when the .GHO file is written, it assumes that it won't span, and what is supposed to happen when it does end up spanning is that the header is adjusted to indicate that it did end up spanning.
My conjecture, therefore, is that somehow this adjustment to set the "spanned" flag might have gone missing somehow; if this one byte in the image header isn't set right, Ghost won't even try to look for a subsequent span and will instead complain with this error.
In order to be sure, I'd need to have a look at the first section of the first span (i.e., the .GHO file). The way these files are laid out is that the first 512 bytes of every span contains a header that describes what it is. If it's the first span, the next 2048 bytes are another header that describes the contents, and it's this section that contains the "spanned image" marker. So, the first 2560 bytes (0xA00 in hex) are the critical part, and from that I should be able to work out if my theory is right.
I don't think I'll need the raw file data, just a dump; in case you don't have a tool to do this, I've adapted a little VBscript from here http://www.interclasse.com/scripts/dumphexafile.php
- you can get from http://nigel.bree.googlepages.com/hex.txt
and if you save it as a .vbs file it'll dump the relevant part of an image file out into notepad.
You can e-mail me the dump at nigel dot bree at gmail dot com, and hopefully from that we can work out if my conjecture as to the cause is correct.