Solved

Unable to clone a new machine with Symantec Ghost.

Posted on 2004-04-28
4
5,840 Views
Last Modified: 2012-05-04
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)
0
Comment
Question by:alex_hearl
  • 2
  • 2
4 Comments
 
LVL 2

Accepted Solution

by:
jsung earned 500 total points
ID: 10943982
Open your protocol.ini file (on your ghost disk under a:\net).
Check if the section below is there:

[nic]
drivername=B44$

If it is there, then there is something else misconfigured.  Please post config.sys and protocol.ini file.
0
 

Author Comment

by:alex_hearl
ID: 10944048
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!)
0
 
LVL 2

Expert Comment

by:jsung
ID: 10945880
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?  
0
 

Author Comment

by:alex_hearl
ID: 10946646
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....
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Switch Uplinking Arista to Force 10 5 39
DNS and NSLOOKUP 21 76
Cisco 3560 switches not seeing VTP V3 12 54
Cisco 5508 WLC software upgrade 2 39
Don’t let your business fall victim to the coming apocalypse – use our Survival Guide for the Fax Apocalypse to identify the risks and signs of zombie fax activities at your business.
I had an issue with InstallShield not being able to use Computer Browser service on Windows Server 2012. Here is the solution I found.
Internet Business Fax to Email Made Easy - With  eFax Corporate (http://www.enterprise.efax.com), you'll receive a dedicated online fax number, which is used the same way as a typical analog fax number. You'll receive secure faxes in your email, f…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

831 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question