Ghost Solution Suite

I'm using trialware GSS 2.0 and cannot create a usable boot cd. using the wizard, I've tried several combinations of Broadcom 57x drivers, PC-DOS vs. MS-DOS, domain vs. workgroup. I have an old floppy that works just fine on my test PC (WXp). I've even tried to create a CD virtually identical to the floppy, using the old driver file and the MS-DOS files from the floppy. I've executed both the floppy and the CD [1] line at a time and everything loads/executes the same until I get to: "NET.EXE USE W: \\<servername>\<share>" In both cases, I'm using the same server and share name. When I boot from the CD, this line returns;

 

 "ERROR 53: The machine id specified in the network path cannot be located."

 

I've struggled with this for 3 days and tried everything I can think of. My trialware time is running out, and if I can't make [1] simple boot CD, I can't see my company buying the product. I have many PCs with various NICs and no floppies. I was hoping to have a CD at each PC to do regular imaging, but I can't get a single CD made.

Hope you can help.

 

 

regards,

Gluke

 

Not quite a soloution but a small request.

 

I have Ghost Sol Server 1.1 and some new Dell PC's we have bought have SATA DVD and Hard Drives.

After extensive talks with Dell support and Symantec Support just saying they cannot help..!

It maybe that a V2 Bootable CD may work as it supports SATA drives. 

 

But before we upgrade.....

Can you send me a Ghost Boot CD with the Broadcom network drivers on and I can test it.

Many thanks.

The universal driver yields the same "error 53" as before. All lines in config.sys and autoexec.bat complete normally until it gets to "net.exe use...." line.

   I'm ready to end my evaluation of Symantec product if I can't get this tiny issue resolved. I can't evaluate the rest of the suite's functions if i can't even make a simple boot CD that work.

 

Help me if you can.

 

thanx,

Glen

 

Stupid question I am sure, but file/print sharing is not blocked in your windows firewall on the server is it?   Can you ping/map the server while the client is in windows?  Is DNS/WINS configured properly in DHCP if you use DHCP.  Sounds like either name resolution or the server is blocking the connection.  Can you map anything else with that machine?  Have you tried \\IP\Share ?

 

 

You can replace the drivers the console makes the CD with.  Go to the website of the manufacturer of the PC and get the latest driver for that product.  On your ghost server browse to: 

 

 

In there are all the templates and config files for drivers.  Find the approproate one, in yoru case should be: Broadcom BCM57xx and put the latest b57.dos from the manufacturer in there. 

 

For anyone else interested the mcassist.cfg file has the PCI Identifier strings that it expects to find to identify a card with.  If you get new hardware and its ID string is not in the file, just add it and the console should be able to start discovering that NIC after you manually set the first one.  In other words, only get one registered in the console and set its template then let the rest connect to the console and it will auto set their nic templates.

 

Just ignore this garbage at the top of the file:

 

# This file is used by the Ghost Boot Wizard.
# You should not attempt to edit this file yourself

 

Don't attempt to edit this file unless you want it to work properly it should read :(

   I've tried \\IP\SHARE and get the same error. I have an old MS-DOS Ghost boot floppy that works just fine so I don't think it's anything on the server side where the share is. I've even burned the files on the old floppy to a disk and it works OK as well. This floppy only includes one NIC driver. I've even used the wizard to create a bootable CD utilizing the old NIC driver from the floppy and I still get the same error. All things point to something that happens when executing from the wizard.

   I have many different PCs, with various NICs and hardware variations, and have already tried with no luck to find DOS drivers for many of them. I don't see any other solution that will work well for us without the universal driver. Thanks again for everyone's help. Any idea what to do next ?

 

 

thanx,

Glen

 

Hi Glen,

 

It is difficult to understand what's going on. I just created a drive mapping boot disk CD from Ghost Boot Wizard using universal driver and used it with two different machines with BC57 driver. A dell 745 and an IBM x206. Both worked fine and I could map the shares.

 

The only way I could get error 53 was if I give a share name with the computer name that does not exist at all. Which means in your case it cannot find the machine.

 

In your old floppy, is there an lmhost file? This file is used to map names to IP addresses. In case if it cannot resolve the name using netbios, it can use the IP address from lmhost to find the machine. In an environment where you cannot resolve the machine name, not having a static map using lmhost file will give you error 53.

 

If there is a file, could you copy that to the CD and try?

 

If this is not the case, could you send the autoexec.bat and config.sys files plus a directory listing (with dir a:\ /s) to me? Please use the forum messages to send me a private message and I will get back to you.

 

Krish

 

Problem solved. I had an incomplete MS-DOS client install, so I had an empty LMHOST file on the CD. Thanks to everyone who helped out.

 

regards,

Glen