Ghost problem with Dell Optiplex 745

Updated: 21 May 2010 | 10 comments

IN2FORD

0 0 Votes

We just received several Optiplex 745 PC's. We are attempting to use a Dell Optiplex 620 Boot cd so that we can perform a Peer to Peer function. As it begins the boot using PC DOS, it says "failure to load driver" andthen begins the Ghost program and the Peer to Peer option is grayed out so that we cannot select it. I am assuming something is up with the NIC driver. Any ideas? Both PC's show that they have the Broadcom Extreme 57xx card and driver.

IN2FORD

Barry

discussion Filed Under:

Endpoint Management, Ghost Solution Suite

Comments RSS Feed

Comments

Jun

2007

0 Votes 0

FPSTech

You need to load a different Broadcom netXtreme 57xx NDIS driver into your boot wizard create a new boot diskette.

I have the driver you need, but I don't recall where I found it, and I can't seem for locate it on Dell's site or Broadcom's.

Send me a message if you want me to email it to you. It isn't very large.

Jun

2007

0 Votes 0

David.P@TAMU

Just go to dells site and look under drivers and plug in your machines service tag to get to the specfic downloads for your machine.

Jun

2007

0 Votes 0

FPSTech

They changed the site to only show you the drivers for specific Operating Systems and DOS isn't an option.

Jun

2007

0 Votes 0

IN2FORD

We actually went to Dell's website and downloaded the appropriate driver for the service tag number and it did not help. We are stumped! Any other ideas?

Barry

Jun

2007

0 Votes 0

David.P@TAMU

The package for the nic driver contains the DOS one as well. So just pick XP or whatever and DL it. When you double click on the package you DL from dell it decompresses in to c:\dell\drivers\*PACKAGENAME*\

look in there for a DOS\NDIS folder. I have about 450 of those machines (optiplex 745) and I get the driver from dells site just like I described.

Is your CD boot a "MultiCard Template" does it try to detect the nic adapter in the config.sys? OR is it a straight load of b57.dos in config.sys.

If you are using the detect.sys in the config.sys then there should be a file named comp.dat in the root of the CD boot drive and it will have the pci-identifier strings for the broadcom nics. It doesnt have the string for your new card. You can cut & paste a new line where you see the broadcom string and modify the identifier string.

The start of my file looks something like this:

0004
\net\card0\$
\net\card1\$
\net\card2\$
\net\card3\$
0023 : Number of devices

everything after this line is PCI-Identifier strings etc...

That first line is the number of different drivers I am working with. If you add a new line you need to increment that last line indicating the "number of devices". That is basically a line counter for everything that follows.

You can get the pci-identifier string by looking at your device manager you will see something like this:

PCI\VEN_14E4&DEV_167A&SUBSYS_01DA1028&REV_02

what follows "VEN_" is the first part of the identifier string and what follows "DEV_" is the second part. In fact, your string may look exactly like the one above because I got it from a 745.

Message Edited by David.Poprik on 06-29-200701:50 PM

Jun

2007

0 Votes 0

IN2FORD

Thanks David. We will give it a try and report back in!

Barry

Jun

2007

0 Votes 0

David.P@TAMU

Check that last reply above again I added more about multicard templates in case that is what you are using.

On second thought you probably dont have a multicard template because the error is more like "Failed to find adapter" and the boot halts right there.

Message Edited by David.Poprik on 06-29-200701:57 PM

Jul

2007

0 Votes 0

IN2FORD

Well I got the TCP/IP Peer to Peer functioning. Once I made changes in the protman file in the USB boot device things worked great. I had to define the the NIC card in that file to use which was B57$. Below is what I have that works:

Code:

[Protman]

drivername=PROTMAN$

[pktdrv]

drivername=PKTDRV$

[pktdriver]

drivername=PKTDRV$

bindings=nic

intvec=0x060

chainvec=0x66

[nic]

drivername = B57$

; Linespeed can be set to 10 or 100

LineSpeed =100

This all worked once I downloaded the NDIS2 driver from Dell and selected the DOS driver when I created the boot device.

Barry

Jul

2007

0 Votes 0

Jared Seymour

I'm having similar problems can you take a look at my autoexec.bat, config.sys, and protocol.ini files. I used the files downloded from the dell website under dos/ndis2. The error im getting is in reference to the nic card. "Interrupt vector for packet drivers not specifed in protocol.ini Broadcom ethernet" etc. Please please please any help would be great. Everything else works fine just the nic problem so I can't multicast.

autoexec.bat>>>>>>>>>>>>>>>>>>

SET TZ=GHO+08:00
prompt $p$g
MOUSE.COM

:OPT8

REM Opti745
MSCDEX.EXE /D:EXTCD001 /L:D
set cdrom=D:
path=%RAMD%\;%CDROM%\;a:\
\net\netbind.com
pause
D:
cd \ghost
GHOST.EXE
GOTO END

Config.sys>>>>>>>>>>>>>>>>>>>>

[OPT8]
REM Opti745
device=himem.sys /testmem:off
device=extcd.sys /D:EXTCD001
devicehigh=ramdrive.sys /e 32767
lastdrive=z
files=100
buffers=20
dos=high,umb
stacks=9,256
pause
DEVICE=\net\Opt8\protman.dos /I:\net\Opt8
DEVICE=\net\Opt8\dis_pkt.dos
DEVICE=\net\Opt8\B57.DOS

Protocol.ini file>>>>>>>>>>>>>

; Protocol.ini section for the Broadcom Ethernet NDIS2
[B57]
DriverName = "B57$"
;

;[B57_n]
;    DriverName = "B57n$"
;    BusNum =
;    DevNum =
;    PortNum =
;    FuncNum =
;    LineSpeed =
;    Duplex =
;    NodeAddress =
;    FixCheckSumOff

Message Edited by Jared Seymour on 07-24-200701:01 PM

Nov

2009

1 Vote +1

jcoz

Refer to this

Refer to this site:

http://service1.symantec.com/SUPPORT/on-technology...

To have the nic card you added to the boot wizard in the MultiCard Template, you must add the PCI tag to the mcassist.cfg file. It will be in the C:\Windows\All Users\Application Data\Symantec\Ghost\Template
folder under whatever you named it when you added it. Open up the file and add the tag:

PCI-TAG = VEN_ID DEV_ID : name

as in

PCI-TAG 14E4 4318 : Intel 82567$

Different physical NICs of the same kind (IE your Broadcom NetXtreme) may have different Device IDs, depending on when and where they were manufactured. Now the NIC should show up in the template and load correctly if 1) you have the correct NIC and 2) it has the correct tag

Ghost problem with Dell Optiplex 745

Comments

Refer to this

Would you like to reply?

Links

Technical Support

Symantec.com

Store

Community Stats