[ghost] Network card turning off in ghost

[mdking]

Hi all,

 

I am currently having a problem ghosting a particular model of laptop.

 

The laptop is a HP 6730s with a Marvell Yukon network driver.

 

 

I have changed the hard drive mode from ACHI to IDE

 

 

The problem is as follows:

 

Press f12 to boot from NIC, then select ghost boot (As normal). Then windows loads files etc, then the network card turns itself off!

 

The laptop proceeds to boot into ghost etc. However i can seem to get the network card to stay on.

 

I have tried to create a new boot image on the ghost wizard (Downloaded the correct driver) Still doesn’t work.

 

However i must admit my knowledge on ghost is limited.

 

Has anyone else had this problem?

 

Any ideas would be greatly appreciated

 

Many thanks

Matt

Edited July 7, 2009 by ZeroHour

[Batman]

My first instinct says it sounds like you might have the wrong Marvell Yukon driver.

 

Also, some of the 6730s when they first came out needed a bios update for their ethernet to work in Windows XP, possibly something like that but I doubt it.

 

To eliminate the hardware, if you have another laptop the same model, take the hard drive out and try ghosting it in the other laptop. If that doesn't work and you're desperate to get the thing working, put the drive in a known good desktop that has sata, image the hard drive and then put it back in the laptop before you run up Windows. I've had to do this once or twice when I was in a hurry and the drivers were not working for me.

 

Hope this helps. Oh, you might need a torx screwdriver

[mdking]

Hi batman,

 

Thanks for your reply. The HP6730 has the lastest bios installed, i have also unboxed another 6730 to see if it was just the laptop and it still doesnt work.

 

 

I haved looked on the Marvell Yukon site for the correct drivers, and i cant find one that works!

 

This is how i have been addeding then to ghost boot wizard i hope this is correct:

 

The Driver on the laptop is an XP driver

 

I am downloading this driver for the Symantec ghost boot wizard. http://www.marvell.com/drivers/driverDisplay.do?driverId=101 - Windows Vista

 

The download is saved on the server desktop.

 

Load up Symantec boot wizard

 

Type Windows PE (default)

 

Edit

 

select winpe

 

Click edit

 

Add New Driver

 

Browse to VISTA driver on desktop

 

Give the file a friendly name (I have put in Marvell_Yukon_Driver) Or does it have to be something else?

 

Tick the OS (Vista)

 

Click ok

 

then it installs the driver

 

Then i try it on the laptop and the network card still turns off after loading the settings

 

 

regards matt

[mac_shinobi]

If that doesn't work and you're desperate to get the thing working, put the drive in a known good desktop that has sata, image the hard drive and then put it back in the laptop before you run up Windows. I've had to do this once or twice when I was in a hurry and the drivers were not working for me.

 

1. Won't HAL Cause any issues because your then installing or imaging xp on different hardware or how are you getting around that issue ?

 

Also for a second there I was thinking that the interfaces between desktop and laptops for hard drives were different but realized that this is only the case for IDE hard drives lol .... and I haven't had my first cuppa coffee doh !

[linkazoid]

For the 6730s' you have to change a line in the Ghost Driver.

 

FIX (see readme)

FIX = 1

 

If you need me to send you the iso boot cd, let me know.

 

Michael

[mdking]

For the 6730s' you have to change a line in the Ghost Driver.

 

FIX (see readme)

FIX = 1

 

If you need me to send you the iso boot cd, let me know.

 

Michael

 

Thanks alot Michael for the repley.

 

 

Im not to hot on Ghost.

 

How would i go about doing this?

[linkazoid]

Open Ghost Boot Wizard - Select Network Boot Package - Find the Driver (Marvell Youkon) i think.

 

Click modify.

 

Change the text that i put in my previous post. The create a new cd.

 

If you want me to send you mine, then let me know.

 

Michael

[mdking]

Open Ghost Boot Wizard - Select Network Boot Package - Find the Driver (Marvell Youkon) i think.

 

Click modify.

 

Change the text that i put in my previous post. The create a new cd.

 

If you want me to send you mine, then let me know.

 

Michael

 

Thanks alot,

 

However i dont normally create cd's for ghost. I normaly boot from the network and it loads the sttings via ip etc.

 

Would the above still work?

[linkazoid]

yes....

 

Should do....

[mdking]

yes....

 

Should do....

 

 

Sorry one last question

 

I have clicked on modify, in the paramaiters do i just copy and paste this into the box?

 

 

"FIX (see readme)

FIX = 1

"

 

Sorry for all the questions

 

matt

[linkazoid]

do you not have anything already in the parameters box?

 

Mine is full of text - you should only have to change the FIX number to 1.

 

Are you using the ndis2 driver?

 

Michael

[mdking]

do you not have anything already in the parameters box?

 

Mine is full of text - you should only have to change the FIX number to 1.

 

Are you using the ndis2 driver?

 

Michael

 

 

Just to make sure i have downloaded the NDIS2 driver from the marvell site,

 

And now there is text in the box, i have changed the FIX number to 1

 

 

But now it wants me to select a target for boot package.

 

Can i just close this?

 

Also, does the 6730 have to have the ndis driver aswell or just the normal XP driver?

Edited July 8, 2009 by mdking

[mdking]

Thanks to Michael this has now been sorted.

 

Created a boot cd for the Marvell Yukon driver and boot into ghost from that.

 

Still haven't managed to sort out how to boot from network, but at least we have found away!

 

Thanks all

matt

[whitenight639]

Ive had the same problem with 15 of our new Toshiba satelite pros, i added the right drivers to the WinPE boot CD with no luck and the same problem booting from PXE as this loads a WinPE image too,

 

I found that adding the NDIS2 drivers for the network card to the PC-DOS fixed my problem but it means I have to boot all 15 from a CD instead of the network, not really a big problem.

 

I wonder what FOG will be like with different NICs.

 

Think when i get in to work monday i will change the network boot image to PC dos instead of WinPE as i have an issue with some client machines not contacting the ghost session as the techie before me has installed alot of different add in NICs, which is a pain in the arse as from a room of 30 pcs only about 24 will ghost, the others have different NICs.