Ghost Solution Suite

Was having this issue with Ghost Suite 1.1, and today downloaded the trial of Ghost Suite 2.0 and I'm having the same issue.

I can create a Network Boot Disk set, which appears to work fine. During the setup of the boot disks I tell it "not" to use DHCP but instead I give it a static IP address.
When I use my new boot disks on a PC, it boots up without a problem into Ghost and tells me it has loaded my driver using the universal driver.
But when I go into Ghostcast and choose an option, i wait 30sec and it comes back telling me "Abort Error 19913: Cannot find DHCP server"

I'm lost as to why I get this especially since I did not choose a DHCP server in the first place.

Hi Joshua,

Yes, it should not look for DHCP in this situation.

In your boot disk, could you see the information in wattcp.cfg file? This is a text file so you can see the contents using type command. It should contain the static IP, subnet mask and Gateway addresses.

Krish

I did double-check that file and it does list the correct IP, Netmask, and Gateway of our network structure here.

As an additional test I loaded up the bootdisks again on a computer;
- it says an extended memory manager has already been loaded so XMS Driver is not installed.
- It tells me my Ethernet address is "MAC address". Is this normal?

I also loaded up the disks to see if I could ping that static IP I gave it. I'm not exactly sure if it's possible to do it this way as I really haven't had a lot of dealings with DOS on a network, but I wasn't able to ping the IP address I put on the bootdisk.


So once again I'm left stumped as to why this won't work.

ok, so after over an hour of trying to find the old PING command and an old IPCONFIG-type command that would work in DOS (no, the one in your windows directory doesn't work. It only works in a Windows enviroment)

I finally found something interesting...... my config file on the Ghost Boot disks... is not copying over to the %dir%\ghost.

So when the program runs the boot disks, pushes the (2) pieces of Ghost together it seems to forget to place the wattcp.cfg in the same directory as the Ghost.exe. Since the config file wasn't there, even when I ran PING I got a message saying no config file and then it switches to attempt a DHCP server.

If I manually copy the wattcp.cfg into the ghost directory and run Ghost...well there we go. It starts to run fine (but then I run into the problem that the trialware won't allow me to test)


SO..... can anyone help identify why the cfg file won't transfer over????

I've exactly the same problem,
if i manually copy the file wattcp.cfg in c:\ghost the multicast session starts correctly,
does anyone known why that file isn't copied?
Is a software's bug?
Thanks a lot

Renato

We have the same problem and old version of NIC drivers works very well...

exactly for Broadcom 57xx interface works driver from 2004

good luck

jaro