Link to home
Start Free TrialLog in
Avatar of Alex Hearl
Alex HearlFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Unable to clone a new machine with Symantec Ghost.

Ok, we have just purchaced four new Dell Dimention 2400's and need to clone them to an existing image held on the server. I have created a bootdisk using the Ghost Boot Wizard, which appears to work, but when I try to boot the new machine with the disk, I get the following message(s):

"Can't find DriverName in PROTOCOL.INI. The driver failed to load"

it then goes on to say:

"NET5733. The protocol manager has reported an incomplete binding. For more information type NET HELP 5733."

then it says:

"The requester service is not started. Is it ok to start it? (Y/N)"

(I assume it IS ok, so I say yes - if this is wrong, please let me know!)

after that it then states:

IBM DOS NET BEUI 3.00
error in loading. Press F1 to continue.

I press F1, and get:

Error 1. An internal error occured.

it then dumps me to the A:\> prompt. and appears to do nothing.

I have tried to do a step-by-step boot to find where it fails, and got this:

IBM Protocol Manager Version 2.1

DEVICEHIGH = A:\NET\B44.DOS Y/N      [I say, "yes"]
Broadcom 440 x 10/100 Integrated Controlloer
DOS NDIS2 Driver v2.44 (030506)
Copyright (C) 2002 - 2003 Broadcom Corporation. All rights reserved.
Can't find DriverName in PROTOCOL.INI

The more astute of you will notice that the machine has an integrated Broadcom 440 10/100 NIC, which I have found out has some problems with Symantec Ghost, but these can be apparently rectified by downlading the updated driver - which I have done.

I am completely stumped - The troubleshooting section in the manual sheds no further light, so I am turning to you.

Please, if anyone can help, I'd be eternally grateful - oh and there's 500 points for you!

(If needed, I can post the file structure of the boot disk and/or the contents of protocol.ini)
ASKER CERTIFIED SOLUTION
Avatar of jsung
jsung

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Alex Hearl

ASKER

I think you may be onto something there, I have litterally just opened the protocol.ini file, and it ends at the equals sign. anyway, here are the files (protocol.ini first.)

[network.setup]
version=0x3100
netcard=NIC,1,NIC
transport=nts$ntst2,NTS$NTST2
transport=ibm$netbeui,IBM$NETBEUI
lana0=NIC,1,ibm$netbeui
lana1=NIC,1,nts$ntst2

[NTS$NTST2]
DefaultDomain=TITAN
BOOTPFLAG=DHCP
DriverName=ntsts$
VCs=16
VCReceiveLarge=6
VCSends=6
RcvWindow=2920
UseMemory=UMB
BINDINGS=NIC
LANABASE=1

[protman]
DriverName=PROTMAN$
PRIORITY=ibm$netbeui

[IBM$NETBEUI]
DriverName=netbeui$
SESSIONS=20
NCBS=20
BINDINGS=NIC
LANABASE=0

[nic]
drivername =


and now the config.sys file:

DEVICEHIGH=A:\HIMEM.SYS
DOS=HIGH,UMB
LASTDRIVE=Z
DEVICEHIGH=A:\NET\PROTMAN.DOS /i:A:\NET
DEVICEHIGH=A:\NET\b44.dos
DEVICEHIGH=A:\NET\NTSTS.DOS
DEVICEHIGH=A:\NET\DLSHELP.SYS


hope this helps (I'll be really annoyed if all I have to do is add B44$, but if it solves the problem, it'll be worth the 500pts!)
Avatar of jsung
jsung

Try it and see if you have any other errors booting up the ghost disk.
Chances are that something else is wrong since the Ghost boot disk creator didn't get it right the first time.  

I don't see any other problems with the protocol.ini file.
Did your Ghost disk creator put those devicehigh statements in the config.sys?  
I assume so. It was a blank formatted disk, and I've added nothing to it. Everything on the disk was created by the Wizard. I'm gonna give your suggestion a try now. will report back soon....