NX6325 Ghosting slow

[plexer]

I don't use the ghost boot disk wizard so can't help there I'm afraid.

 

Ben

[beeswax]

Hi Ben,

 

Thanks for your reply - I did indeed try the drivers from the Broadcom site and the HP site, but to no avail. Are there any others people have used successfully? Are there any considerations I need to take into account when creating the boot disks using the Ghost Boot Disk Wiazrd?

 

Thanks,

Neil

 

 

This is a problem I had with broadcom nics -

 

"What network card are using. You don't have have a Dell with a Broadcom NIC by any chance?

 

I've just been imaging 15 Stone laptops with broadcom nics, and when it came to creating the boot disk the protocol.ini file was incorrect, in that it had a blank space where the drivername should be, i.e.

 

"[protman]

drivername=PROTMAN$

 

[pktdrv]

drivername=PKTDRV$

bindings=nic

intvec=0x60

chainvec=0x66

 

[nic]

drivername = [this space was blank]"

 

it should have had B44$, without the brackets, for the Broadcom 440X 10/100. worked fine after that. I've never had this problem before creating a boot disk."

[plexer]

I believe he is trying to ghost HP NX6325's as per the topic title but I could be wrong. If so it's not a 440X it a 10/100/1000 Broadcom Netlink as I'd allready said.

 

But thanks for your suggestion.

 

Ben

[beeswax]

Forgive me if I'm being ignorant, but it could be that when he creates the ghost boot disk, the drivername in the protocol.ini is blank whatever version of a broadcom nic it is.

[plexer]

Hi beeswax,

 

Yes it could be that lets hope it is as simple as that to solve his problem.

 

Thanks,

 

Ben

[nsherin]

Hi all,

 

Thanks again for the replies - it is indeed the NX6325 that I'm trying to Ghost. My PROTOCOL.INI file looks like this:

 

; Protocol.ini section for the Broadcom Ethernet NDIS2

[b57]

DriverName = "B57$"

 

; BusNum from 0 to 255

; BusNum =

 

; DevNum from 0 to 31

; DevNum =

 

; PortNum or FuncNum from 0 to 7

; PortNum =

; FuncNum =

 

; LinSpeed can be set to 10 or 100

; LineSpeed =

 

; Duplex can be set to half or full. LineSpeed is required when this keyword is used.

; Duplex =

 

; NodeAddress specifies the network address used.

; NodeAddress =

 

 

; FixCheckSumOff turns off the driver's work-around for the TCP/IP stack to recognize

; the 1's complimented version of the checksum.

; FixCheckSumOff

 

 

;

; To add more adapter(up to 4) repeat the below entry, where n can be from 2 to 4.

;

 

;[b57_n]

; DriverName = "B57n$"

; BusNum =

; DevNum =

; PortNum =

; FuncNum =

; LineSpeed =

; Duplex =

; NodeAddress =

; FixCheckSumOff

 

Any ideas or help is much appreciated. The notebook does appear to load the driver without any errors or problems that I can see during the boot process.

 

Thanks,

Neil

[k-strider]

I can send you an Floppy Image.. if you like that works for me on my nx6325s

 

use the image to make a boot CD and put your copy of Ghost.exe on the root of the CD...

[plexer]

k-strider: could you post your protocol.ini to see if there is a problem with nsherin's?

 

Ben

[nsherin]

Thanks for the offers of help guys. I've cracked it - basically, the Broadcom drivers don't like a static IP address. I've no idea why, as an older batch of Dells that I have with Broadcom chipsets were quite happy with static IPs.

 

Ghosting happily now using boot floppies at about 450mb/s - once I'd remembered the -noide switch to pass to Ghost on start up.

[plexer]

Cool another win for the edugeekers

 

Ben

[davecox]

NOTE TO REMEMBER: SATA equals -NOIDE.

 

I wont be forgetting that in a hurry.

[nsherin]

The funny thing is on my home PC, where all the hard drives are S-ATA, I've not had to use the -NOIDE switch - Ghosting speeds are pretty fast. The only problem is that Ghost and other tools such as Partition Magic running off a DOS boot CD take a while to load up. I might see if the -NOIDE switch makes a difference if I get a minute over the weekend.

[plexer]

It depends on how the motherboard and controllers display the sata interface if they emulate a PATA connection then you don't need to do anything however if they are native sata then you need to use the -noide switch.

 

I've just had a similar problem installing Smoothwall Corp Guardian on a Proliant DL140, it's got SATA drives and the smoothie setup asks you if you need scsi or sata support so I said yes and it then told me it couldn't find any controllers. I then decided to say no I didn't need scsi or sata support and it installed fine.

 

Cheers,

 

Ben

[razman10000]

OK I have used the -noide switch and the speed increased but now the imaging stops at 309MB. Is there a reason why or could it be another issue??

[Extrovert]

I cannot even get my HP NX6325 to boot past the first disc. Running Ghost 8.0. I have tried to the b57.dos file but it still will not recognize the NIC and it will not bind. Any ideas? Is there a different file just for the Broadcom Netlink Gigabit card for this HP that will make it so I can network to my Ghost console? Also I put in my discs and I get the error for no binding I don't see where I can put in the command prompt lines because it boots straight to the Ghost set-up. Please any explanation would be great.

[bensysco]

Well this has been a long row to hoe.

Our new HP nx6325s had this issue with Ghost, here's how we fixed it:

 

From Symantec support we got the following fix and it is working great now.

 

Launch ghost using these switches ghost -fnx -noide

 

The full text of the reply below:

Dear Name

 

I’ve been doing some research on your issue with the NX 6325 machines. HP has recorded several instances of problems with this model machine when working with Ghost. As suspected, this is probably an issue with the SATA hard drive in the machine. HP, it seems, has taken away your ability to change the mode that the hard drive operates under. The default mode of the drive, the Native SATA mode, is not recognized properly in DOS and therefore, not recognized properly in Ghost.

 

 

 

I tracked down the product manual, where they show where this toggling should occur. Based on the comments to the document, though, it doesn’t look like the options in the User Manual are present in the BIOS but it’s still worth a look. You can get the manual from here:

 

 

 

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00715299/c00715299.pdf

 

 

 

The information about altering the mode of operation of the hard drive can be found on page 37 of the manual. What I would suggest is to make sure you have the latest BIOS update from HP and then use this manual to see if you can find the option to switch the drive to an alternate mode that is compatible with DOS.

 

 

 

In addition to the BIOS update and hard drive mode change, I also found some documentation suggesting that the following combination of switches worked in some cases:

 

-fnx –noide

 

 

 

We tried both of these switches yesterday but I don’t think we tried them in this combination. Add these to your command line and see how your imaging goes.

 

 

 

Here is some more information about the problems noted on the HP forum with regard to this hard drive:

 

[ http://forums1.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=1066020&prodSeriesId=1849082&admit=-682735245 1181060191635 28353475&prodTypeId=321957 ]http://forums1.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=1066020&prodSeriesId=1849082&admit=-682735245+1181060191635+28353475&prodTypeId=321957

 

 

 

I’m on a call at the moment but will get in touch shortly.

 

 

 

Thanks.

 

 

 

Jarrod

 

 

 

 

 

 

 

 

 

Jarrod name obscured

 

Product Support Analyst

 

Infrastructure Management Solutions

 

Symantec Corporation

[plexer]

I don't know what the -fnx does but we had decided that the -noide switch was for sata drives anyway and that works great for me on my nx6325's

 

Ben