AchingBack

Sounds like your user name should be *GhostUserMigraine* !

Quote:

I'm surprised the program didn't re-boot you to Windows *automatically* after it encountered an error state.

Quote:

Ghost, when started from the Windows GUI, is running from a *script* file--so it may have been trying to complete the script, and perhaps do the integrity check--but, even if it was trying to *re-write* the image--unless you have a re-writeable disc--Ghost would not be able to access a one-write optical media and cause any harm--so it was *safe* as far as the image on the disc is concerned.  

For a re-writeable, there would have to be an *erase* command sent--and to be honest--I've never tried Ghost with a re-writeable that has data on it already while running the *automated* image creation from the Windows GUI--so I don't know how Ghost would handle that.  I do know that if you boot Ghost from a floppy or bootable optical media, and use re-writeable media, Ghost has a step where it asks for confirmation that you wish to *erase* the existing data on the disc.

Quote:

Everything that happened after the disc was finalized and ejected, probably was not part of the error log file created by Ghost.  As mentioned above--I would have thought Ghost would have automatically re-booted to Windows at that point--but, apparently it did not, and you were able to the additional things you outline *manually*--but, as far as Ghost's *script*--all those *manual* procedures did not happen!

Quote:

Hmmmm....that's weird--quoting from the User Guide, page 113, regarding the *Backup Wizard* in the Windows GUI:

Quote:

There is *hidden* boot code that Ghost uses to make the optical media bootable when using the Windows Ghost GUI--don't know how that works because it happens *behind the scene*--probably a *boot ".img" file* embedded inside another file--I think I remember that Ghost shows in its log file that it calls a .bin, or .dat or .cab file of some kind when it's creating a bootable optical disc--so the code is not seen by the user.

Quote:

I think you may be dealing with conflicting coding that Symantec did not correctly implement--how can you setup an *automated* process in the Windows GUI to create an image, and then next automatically test the Integrity of an image, if you (a) require a password to access the image, and (b) the coding for writing to optical media includes a *eject* command at the end of the writing!  This can not be *automated* unless Ghost is going to *remember* the password during the script cycle, and has the ability to either not eject after the disc is finalized, or has the ability to *automatically* close the tray for the integrity check to take place!

I saw one posting in the past where there is a DOS command to close the optical drive's tray--but that is not in Ghost's capabilities--apparently!

Quote:

Don't know--you would have to re-try that and let it run to see what it attempts to do!  As mentioned above--if it's a one-write disc, then Ghost can't access it after it's *finalized*, and if it's a re-writeable--well, at least for testing purposes--no harm done if it erases the data--but, you would want to avoid that if you want the image data for the future!

Quote:

That switch will only apply if you use the DOS based Ghost, and not the Windows Ghost GUI.  Having the boot floppy in the floppy drive again only applies if you have booted from a floppy disk to DOS.  (By the way--if you boot from a bootable optical media that creates a *virtual* floppy A:\ drive--the DOS based Ghost will ask if you have your floppy disk in the A:\ drive--which of course you *can't*, because it's a *virtual* drive--but you simply click *OK* or *Continue*--can't remember which right now--and the DOS Ghost program will read and use the boot files in that *virtual* floppy A:\ drive to create a bootable optical media.)

Quote:

You would have to do some experimenting to see what works!  Your last statement above should work fine, except as you have already mentioned--it's not bootable!  

If you eliminate the *password*--that might help.  Or, instead, as you say--do the Integrity check separately.  You can do the Integrity test from the Windows GUI--but, with a password--I suspect you will have to enter that somewhere in the process--the Windows Ghost GUI would not *know* the password unless you have to enter it somewhere.

Report back with what you find out in troubleshooting your issues--it would be of interest!

My 3rd DVD backup (like the first 2) is NOT bootable> .  In setting the options in the Windows GIU for the 3rd DVD, I selected no password and no verify.  (The 1st Ghost was with both password and verify.  The second was with password, but no verify.)

The log for this 3rd session says the arguments were:

-igb -bootcd=\ghost\bootcd.dat -z2 -imgdescfile=\ghost\imgdescp.txt -wizard "-clone,mode=create,src==[long text sting that looks like a disk ID or serial number],dst=@CD[ID:5372562]" -ghwrap

-bootcd is supposed to make this bootable

Is there anything wrong with these arguments?

What else can I try in order to make my Ghost DVD bootable?