Video Screencast Help

Output error - ghosterr.txt.... help

Created: 10 Jun 2008 • Updated: 21 May 2010 | 6 comments

I am using GhostCast Version to restore an image on a HP 5750 desktop. I am restoring the image to the local drive connected to the 2003 server with ghostcast server running.

The ghost program appeared to be working until it got about 63% completed, and then it came up with a file name? (546) message saying "Output error file to the following location: a:/ghosterr.txt". The computer I am trying to create an image of does not have a diskette drive "a" installed. If I try to change the location to a different drive letter, I get an error message saying "Cannot open Ghosterr.text - insert diskette (434)".

Is there a way to make changes to this output file using Ghost Explorer? I have Explorer V.

I create and restore images weekly and have never gotten this error before. Normally image Lenovo laptops and a few HP 4400's. All running XP SP2 volume licensing.

Discussion Filed Under:

Comments 6 CommentsJump to latest comment

Morgan Mackeson-Ellis's picture
Add the /afile=<errorfile> switch to ghost at the cmd prompt to specify a valid location for the error file to be stored.
>ghost -afile=d:\testerr.txt
Take a look at the error file to see if it can shed any light on the situation for you. Post it to this thread and I'll try to see what is happening.
lil big man's picture


I managed to figure this one out. I used the Ghost cast server to designate where to save. In the options menu, in the area marked troubleshooting, I changed the location for the log file. It seemed to work and the image was restored to my client machine.


But, I am now getting the A:ghosterror.txt message on a new HP4600 Winxp SP2 machine I am creating an image for. I can not get to begin the process, before getting the error massage. My previous trick stated above didn't work for me this time around. Can you help out with this one? Also, I wasn't sure where to locate the error file, so please speak slowly and in very plain english. :-)



lil big man's picture

BTW... Normally when restoring images, I just insert the boot cd into client machine, select the appropriate settings, and then hit proceed with image restoration. I don't get any more technical then that. Same process for creating an image to save and deploy to many machines of same make and model.

Morgan Mackeson-Ellis's picture

OK, so when you boot up with the cd and ghost loads up, either press ctrl+c or use the gui to quit out of ghost and back to the command prompt. It is at the command prompt where you can specify command line arguments for ghost. You will need some writable media attached to set as the destination for the error file, you can save it to another disk, usb floppy/flash or a network location if you have mapped a network drive.

Make sure your writable media is attached before you start the machine. Boot up, quit out of ghost and then type gost.exe -afile=<drive letter of writable media>:\myErrorFile.txt

ie. ghost.exe -afile=d:\errorFile.txt

If you are in DOS then you'll need a FAT file system to save to as NTFS will not be given a drive letter in DOS.


I find building a PC-DOS bootable USB flash drive is easiest for this scenario that way you can include other GSS tools that may come in handy such as gdisk.exe and omnifs.exe.


Once you have an error file you may be able to diagnose the problem yourself or you can post it here.




lil big man's picture

Hi Morgan,

I will try this and report back. Now, do I need a specific type of PC-Dos boot disk? There are so many variations out there, it is kind of confusing. Is it easier to use a floppy (I have an external USB floppy) or a flash drive? And once created, will I be able to re-use it on other imaging jobs? I feel like such a noob. Sheesh. 

Morgan Mackeson-Ellis's picture

Flash device is ideal for creating a 'drive mapping boot package' because you can add all the nic drivers you need in a 'multicard template', this will allow you to use it on most, if not all, of your machines even with different nics. The disadvantage of the usb flash drive is that some machines (mostly dated ones) will not boot from usb flash device. Either 'Drive Mapping BP' or 'Network BP' created from Ghost Boot Wizard should be sufficient for your scenario.


USB flash devices are writable so you will not have this error file saving problem, instead the error file will be written to the directory on the flash device that you have run ghost.exe from.