Ghost Solution Suite

I'm using a CD to boot up an HP Proliant DL-140 and run Ghost.exe. I then need to install the Console Boot partition in preparation for using the Ghostcast server. The problem is that when installing this partition, ghost.exe on the Proliant requires me to provide a floppy drive upon which to record the error file, ghosterr.txt. Well, I have no floppy (who uses floppies anymore?), so the program throws me out at that point. Is there a way around this issue? I have two racks of these Proliant servers, and I don't want to have to install floppies on each server just so I can run the Ghostcast server.

I'm using GSS 1.1.

Thanks!

-Dan

A bit more information:
If I hit "Cancel" on the dialog box that asks for a floppy drive for the error file, I then get an "Error" dialog box entitled, "Application Error 29005". The text of this box states, "Write sector failure, result = 1, drive = 0, sectors 48196 to 48197. If this problem persists, contact Symantec Technical Support ..."
Thanks again!
-Dan

Hi Dan,

The way to change the location of the error file is to run Ghost.exe with the switch -afile.
For example, if you want to write the error file to d:\path\ghosterr.txt, start ghost with the following command line.
ghost.exe -afile=d:\path\ghosterr.txt

Seeing as your machine doesn't have a floppy drive, you will need specify a destination that is on
1. A FAT/FAT32 partition on the harddisk
2. A FAT/FAT32 formatted USB key if your machine can detect it under DOS.
3. Mapped Network Drive.

Can you then paste the content of the error file into a post so we can see why you are getting this error.

Cheers

Peter

Thanks Peter,
I'll try this and let you know what I find.
It would be nice if the error codes could be sent to the monitor instead of a file. The machine has no partitions yet, so asking it to vector its error file to a different partition sort of violates the rules of logic. Is it possible to create a virtual disk in RAM for this purpose? Anyway, I'll try the USB thing or perhaps find a way to map a network drive, as per your suggestion.
-Dan