Driver Validation - Win7 64 bit network driver

hi,

I'm using Ghost 15 on Win7 x64 and it's working pretty well so far.

One problem I have is the following.

I tried to make a recovery disk. I got the messsage that there are 3 64 drivers that can't be used. One of them is for my INTEL network adaptor (it's a PCIE NIC). So I downloaded the correspondig 32 bit friver from Intel and added it to the recoveryDisk.

When I boot from the recovery Disk I cant browse my network because there is no adpator...though I've added the correct driver.

 

As my images are on a NAS it is important for me.

Have you got any ideas?  

 

edit: those are the missing drivers:

 

INTEL Gigabit CT Desktop Adaptor

WAN Miniport (IKEv2)

TAP-WIN32Adapter v9

 

I only addes the Intel driver in 32bit and deleted the 2 others. Are they important for getting connectef wiht a network drive?

 

Message Edited by sponch on 12-06-2009 06:53 AM

Hi Sponch,

 

Welcome to the forum. Yes they are important and should be included on your recovery CD. Are you having problems locating the 32 bit version of the drivers for the other two? Is so perhaps I can help search for them.

 

Also, please see the Ghost 15 user guide starting at page 188 and make sure you are following the steps which are required to have successful network access in the recovery environment.

 

Allen

Message Edited by AllenM on 12-06-2009 10:50 AM

Sponch,

 

Have you tried loading a driver after booting into the Ghost recovery environment?

Hi Brian,

 

To my understanding I don't believe Sponch has the 32 bit version of the other two drivers on the hard drive. If the other two are there, then of course this should work. I would always be inclined to include them on the recovery CD so I would not always have to load them manually each time I boot to the SRD. :smileywink:

 

Allen

Thanky sou both for your help!

IT is  right I don't have the other drivers in 32bit...don't know where to find them.

 

When I start the app drivervalidation.exe in the folder Driver Validation on the SRD I got the following message:

Die folgenden Geräte haben keine Treiber in Symantec Recovery Disk.

Intel(R) Gigabit CT Desktop Adapter
WAN Miniport (IKEv2)
TAP-Win32 Adapter V9

Ausführliche Informationen über diese Geräte finden Sie weiter unten.

Beschreibung    : Intel(R) Gigabit CT Desktop Adapter
Klasse        : Net
Klassen-GUID    : {4d36e972-e325-11ce-bfc1-08002be10318}
Hardwarekennung    : PCI\VEN_8086&DEV_10D3&SUBSYS_A01F8086&REV_00
Hardwarekennung    : PCI\VEN_8086&DEV_10D3&SUBSYS_A01F8086
Hardwarekennung    : PCI\VEN_8086&DEV_10D3&CC_020000
Hardwarekennung    : PCI\VEN_8086&DEV_10D3&CC_0200
Hardwarekennung    : PCI\VEN_8086&DEV_10A7
Hardwarekennung    : PCI\VEN_8086&DEV_10A9
Hardwarekennung    : PCI\VEN_8086&DEV_10A6
Hardwarekennung    : PCI\VEN_8086&DEV_10A7&SUBSYS_10A88086
Hardwarekennung    : PCI\VEN_8086&DEV_10D3
Hardwarekennung    : PCI\VEN_8086&DEV_10D3&SUBSYS_A01F8086
Hardwarekennung    : PCI\VEN_8086&DEV_10C9
Hardwarekennung    : PCI\VEN_8086&DEV_10E6
Hardwarekennung    : PCI\VEN_8086&DEV_10E7
Hardwarekennung    : PCI\VEN_8086&DEV_10C9&SUBSYS_A01C8086
Hardwarekennung    : PCI\VEN_8086&DEV_10C9&SUBSYS_A03C8086
Hardwarekennung    : PCI\VEN_8086&DEV_10E6&SUBSYS_A01F8086
Hardwarekennung    : PCI\VEN_8086&DEV_10E6&SUBSYS_A02F8086
Hardwarekennung    : PCI\VEN_8086&DEV_10E8&SUBSYS_A02C8086
Hardwarekennung    : PCI\VEN_8086&DEV_10E8&SUBSYS_A02B8086
Hardwarekennung    : PCI\VEN_8086&DEV_150A
Hardwarekennung    : PCI\VEN_8086&DEV_10D6&SUBSYS_147A8086
Hardwarekennung    : PCI\VEN_8086&DEV_150D&SUBSYS_A10C8086
Hardwarekennung    : PCI\VEN_8086&DEV_10D3&SUBSYS_3250103C
Hardwarekennung    : PCI\VEN_8086&DEV_10C9&SUBSYS_323F103C
Hardwarekennung    : PCI\VEN_8086&DEV_10E7&SUBSYS_31FF103C
Hardwarekennung    : PCI\VEN_8086&DEV_10A7
Hardwarekennung    : PCI\VEN_8086&DEV_10A9
Hardwarekennung    : PCI\VEN_8086&DEV_10A6
Hardwarekennung    : PCI\VEN_8086&DEV_10A7&SUBSYS_10A88086
Hardwarekennung    : PCI\VEN_8086&DEV_10D3
Hardwarekennung    : PCI\VEN_8086&DEV_10D3&SUBSYS_A01F8086
Hardwarekennung    : PCI\VEN_8086&DEV_10F6
Hardwarekennung    : PCI\VEN_8086&DEV_10C9
Hardwarekennung    : PCI\VEN_8086&DEV_10E6
Hardwarekennung    : PCI\VEN_8086&DEV_10E7
Hardwarekennung    : PCI\VEN_8086&DEV_10C9&SUBSYS_A01C8086
Hardwarekennung    : PCI\VEN_8086&DEV_10C9&SUBSYS_A03C8086
Hardwarekennung    : PCI\VEN_8086&DEV_10E6&SUBSYS_A01F8086
Hardwarekennung    : PCI\VEN_8086&DEV_10E6&SUBSYS_A02F8086
Hardwarekennung    : PCI\VEN_8086&DEV_10E8&SUBSYS_A02C8086
Hardwarekennung    : PCI\VEN_8086&DEV_10E8&SUBSYS_A02B8086
Hardwarekennung    : PCI\VEN_8086&DEV_150D&SUBSYS_A10C8086
Hardwarekennung    : PCI\VEN_8086&DEV_150A
Hardwarekennung    : PCI\VEN_8086&DEV_150C
Kompatible Kennung    : PCI\VEN_8086&DEV_10D3&REV_00
Kompatible Kennung    : PCI\VEN_8086&DEV_10D3
Kompatible Kennung    : PCI\VEN_8086&CC_020000
Kompatible Kennung    : PCI\VEN_8086&CC_0200
Kompatible Kennung    : PCI\VEN_8086
Kompatible Kennung    : PCI\CC_020000
Kompatible Kennung    : PCI\CC_0200
----------------------------------
Beschreibung    : WAN Miniport (IKEv2)
Klasse        : Net
Klassen-GUID    : {4d36e972-e325-11ce-bfc1-08002be10318}
Hardwarekennung    : ms_agilevpnminiport
Hardwarekennung    : MS_AgileVpnMiniport
----------------------------------
Beschreibung    : TAP-Win32 Adapter V9
Klasse        : Net
Klassen-GUID    : {4d36e972-e325-11ce-bfc1-08002be10318}
Hardwarekennung    : tap0901
Hardwarekennung    : tap0901
----------------------------------

 

 

Sponch,

 

Try loading the Intel driver from the recovery environment. The other two drivers might not be needed.

Hi Sponch,

 

Thanks for the update. I won't pretend to understand most of what you pasted but I think I get the gist of it. :smileywink:

 

I think the WAN Miniport is the most important one apart from the Intel which you already included. Let me do some searching and see if I can find the location where you can get the 32 bit version of this driver.

 

Just to make sure, have you followed the steps in the Ghost 15 user guide I referred to and still cannot access the network?

 

I'll update again either way when I've had a chance to search for the other driver.

 

Allen

Brian, how do I manually load the driver?

 

 Allan,I think, I did everything correctly....the problem is, although I have included the driver  the driververifaction says that there is no Intel dirver... which folder should be be copied to in the CD?

Message Edited by sponch on 12-06-2009 11:32 AM

sponch wrote:

Brian, how do I manually load the driver?

 

 


 

Hi Sponch,

 

You can't manually load the driver unless it is located on your hard drive. Have you tried the recovery CD to see if you can access the network? I've seen some instances where WAN Miniport is required and seen others where it works without it. So you need to try the recovery environment first and see if you have network access.

 

If this still does not work for you, please tell me the manufacturer and model of your Motherboard and NIC and I'll see if I can locate the missing driver for you.

 

Thanks

Allen


sponch wrote:

Brian, how do I manually load the driver?

 

 Allan,I think, I did everything correctly....the problem is, although I have included the driver  the driververifaction says that there is no Intel dirver... which folder should be be copied to in the CD?

Message Edited by sponch on 12-06-2009 11:32 AM

 

Hi Sponch,

 

I'm a little confused. I thought you had created a new Custom CD already. You did say you have the 32 bit version of the Intel driver correct? Did you use that to create a new CD?

 

If not, you can load this one from the recovery environment by browsing to the location you stored the 32 bit Intel driver at. You need to point it to the driver file which should end in .sys.

 

Once you verify that this works, you should create a new Custom CD which includes this extra driver so you won't have to load manually every time.

 

Allen

okay..sorry for being a bit confusing..;)

I've created a Custom Recovery CD with the Intel driver. I missunderstood something.

Okay I guess the Intel driver is implemented in the Disk.

So I probably need the wan miniport driver.

My motherboard is a "Asus commando"

 

Message Edited by sponch on 12-06-2009 11:48 AM

sponch wrote:

okay..sorry for being a bit confusing..;)

I've created a Custom Recovery CD with the Intel driver. I missunderstood something.

Okay I guesst the Intel driver is imlemented in the Disk.

So i probably need the wan miniport driver.

My motherboard is a "Asus commando"

 


 

Hi Sponch,

 

No problem. :smileyhappy: I just want to make sure I understand. Can you confirm you tried accessing your network from the recovery environment, following the Ghost 15 user guide starting at page 188? After following the procedures were you able to access the network at all? You really need to look at the Ghost user guide and make sure you configure the recovery environment as specified. For example, did you configure the IP address as indicated in the guide?

 

If this still does not work, also please let me know the exact model number of the Asus Commando MB.

 

Edit: Another thought. When you purchased your computer did it include any CD with it? If so, there is a good chance the missing drivers on right there on the CD. Even though you may have purchased this with a 64 bit OS, there is a good chance that the CD has both 32 and 64 bit drivers on there.

 

Thanks much

Allen

Message Edited by AllenM on 12-06-2009 11:56 AM

sponch wrote:

Brian, how do I manually load the driver?

 


sponch, it is Utilities, Load a Driver, navigate to the .inf

 

You can have the driver on a USB flash drive if that is convenient.

Sponch indicated it is already built into a Custom CD. The .inf is what windows uses to install a driver but it is not the actual driver. Is the recovery CD able to use the .inf file directly? Perhaps it reads the information in the .inf and then searches for the .sys driver?

 

I think Sponch probably needs the WAN Miniport as well but I do want to confirm that the procedures in the user guide were followed before I search for this. :smileywink:

 

Allen


AllenM wrote:

 Perhaps it reads the information in the .inf and then searches for the .sys driver?

 


Allen, yes. I put all the driver files in a folder on the USB flash drive. Navigate to the .inf and Ghost does the rest.

Cool, nice to know Ghost has a bit of intelligence on this. :smileyhappy:

 

Sponch, I done a bit of researching on the ASUS Commando MB. From what I can see you should have a CD which came with your system and good chance it has the 32 bit drivers on there.

 

Go into your Device Manager and find the entry for the WAN Miniport device. NOTE that you might have to select View > Show Hidden Devices to see this. It should then be listed in the network section of the device manager. See who the provider is. It might be Microsoft but my thinking would be that the CD should also have this.

 

The web site for ASUS Commando is:

 http://www.asus.com/product.aspx?P_ID=wWs3CTw57UtxaaHw&content=download

 

They have drivers you can download if they are not on the CD. If you have the CD search for a drivers folder or something along those lines. See if they have seperate folders for 32 and 64 bit, etc.

 

Allen

Message Edited by AllenM on 12-06-2009 12:26 PM