Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrade.
Please accept our apologies in advance for any inconvenience this might cause.

GSS 2.5 and Intel drivers USB 3.0

Created: 21 Feb 2013 • Updated: 21 Feb 2013 | 11 comments

Hello.

I always create a boot usb pendrive from boot wizard and i have edit winpe-512 to include nic drivers without problems. Now i need include usb 3.0 drivers four our news motherboards and i have downloaded from intel usb 3.0 drivers.http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19880&keyword=usb+3.0&lang=eng

 

This file is one exe, but if i uncompress it, i can see a lot of files. I'm finding for a .inf  file and then i select edit winpe-512 -> storage drivers-> add new driver then i select x86 folder and vista, but i get failed to import driver a failed to find any drivers to add.

 

Any one can help me?

thanks.

Operating Systems:

Comments 11 CommentsJump to latest comment

EdT's picture

You need to identify the Vista 32 bit drivers in the selection, as WinPE uses the Vista kernel in this GSS release.

This technote may help:

https://www-secure.symantec.com/connect/articles/d...

 

 

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

jose perez merida's picture

I know that. I he downloaded right drivers. Are valid for win vista 32 and 64, win 7 32 and 64. Inside folder x86 are inf cat and sys files but add drivers option doesn't recognizes 

jose perez merida's picture

I have copied all files .inf, .cat,.sys and dll and exe to one folder but it doesn't works. Then i boot from my usb with ghost client 11.5.1 built from boot wizard and execute command drvload nusb3xhc.inf and shows successfully loaded nusb3xhc.inf

What happen? Why i cannot insert into winpe it?

Thanks.

EdT's picture

Can you check that you are following the procedure in this technote:

http://www.symantec.com/business/support/index?pag...

You need to make sure your drivers are SELECTED after you have ADDED them.

(PS. I can see the posting that you made an hour ago - for some reason it has been caught by the spam engine, but it will be released by the admins when they review it)

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

jose perez merida's picture

I cannot add drivers. I always get  failed to import driver a failed to find any drivers to add. I have followed this steps

  1. Open the Ghost Boot Wizard.
  2. Select Windows PE
  3. Click Edit.
  4. Select the WinPE version that you would like to edit.
    Note: See the notes below for information on the different versions.
    Best Practice: Select the appropriate version that you would like to add drivers to, and click "Copy...". Give the new copyed Windows PE driver database a "Friendly Name". This is the name that you will use when selecting this driver package for use in a boot disk, or from the Ghost Console. Click OK.
  5. Click Edit.
  6. Depending on the type of driver that you would like to add, go to the "Network Drivers" or the "Storage Drivers" section.
    1. Look through the list to see if the driver you need is already supplied.
    2. If it is already supplied, check the box to include that driver.
      Note: If using the WinPE version, Symantec suggests that any drivers that are not needed be disabled so that the space requirement is not exceeded.
    • If the driver you need is not included:
      1. Click Add New Driver
      2. Click Browse and navigate to the root location of the NIC or Storage driver that you would like to add.
      3. Create a "Friendly Name". This is the name that you will use when selecting the driver from Ghost.
      4. Check the Applicable Operating System. For Windows PE drivers, this should be VISTA only.
      5. Click OK.
      6. Check the box for the driver that you have just added.
      7. Click OK

This is the folder with usb 3.0  32bits drivers:

0x0401.ini
0x0404.ini
0x0405.ini
0x0406.ini
0x0407.ini
0x0408.ini
0x0409.ini
0x040a.ini
0x040b.ini
0x040c.ini
0x040d.ini
0x040e.ini
0x0410.ini
0x0411.ini
0x0412.ini
0x0413.ini
0x0414.ini
0x0415.ini
0x0416.ini
0x0419.ini
0x041b.ini
0x041d.ini
0x041e.ini
0x041f.ini
0x0424.ini
0x0804.ini
0x0816.ini
0x0c04.ini
0x2c0a.ini
1025.mst
1028.mst
1029.mst
1030.mst
1031.mst
1032.mst
1033.mst
1034.mst
1035.mst
1036.mst
1037.mst
1038.mst
1040.mst
1041.mst
1042.mst
1043.mst
1044.mst
1045.mst
1046.mst
1049.mst
1051.mst
1053.mst
1054.mst
1055.mst
1060.mst
11274.mst
2052.mst
2070.mst
3076.mst
FUSB3_allOS_2.1.28.1_PV
ISSetup.dll
listado.txt
nusb3co.dll
nusb3drv.msi
nusb3hub.cat
nusb3hub.inf
nusb3hub.sys
nusb3mon.dll
nusb3mon.exe
nusb3utl.exe
nusb3ver.dll
nusb3xhc.cat
nusb3xhc.inf
nusb3xhc.sys
setup.exe
Setup.ini
setup.iss

 

pkaurav's picture

Hi,

Could you please give more details about your case? why you want to include USB 3.0 drivers into WinPE?  Is machine not booting into WinPE without USB 3.0 drivers? Can you share inf file of drivers  that you are adding?

Thanks

Pushpraj Kaurav

jose perez merida's picture

Because my machine has a intel dh61dl motherboard. In frontal panel has two usb 2.0 ports. I connect my usb boot pendrive with ghost in one usb port and external usb hdd and second usb port.

Behind motherboard it has four usb ports 3.0. Keyboard,mouse,and usb audio device are connected . When i boot ghost from usb pendrive and it ends load, it shows "ok", keyboard and mouse doesn't works. I suppose it is problem of usb 3.0.

I don't understand what do you want to say "can you share inf file of drivers that you are adding?".

 

EdT's picture

@pkaurav - USB-3 hardware support is generally provided by specific chipsets for which drivers are required, as bios support tends to be for USB-2 currently. That's the best reason for needing USB-3 drivers in a WinPE boot.

@jose - the reason for posting the contents of any INF files you are using, is that the INF file is an instruction file that tells the operating system how the driver should be loaded. It also contains operating system versions supported and other bits of information that may highlight why a driver is not loading.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

jose perez merida's picture

nusb3xhc.inf

; ========================================================
; Copyright (c) 2010-2011 Renesas Electronics Corporation
; INF file for installing USB 3.0 host controller driver.
; ========================================================

[Version]
 Signature="$Windows NT$"
 Class=USB
 ClassGuid={36FC9E60-C465-11CF-8056-444553540000}
 Provider=%RENESAS%
 DriverVer=10/25/2011,2.1.28.0
 CatalogFile=nusb3xhc.cat

[SourceDisksNames]
 1 = %DISKID%

[SourceDisksFiles]
 nusb3xhc.sys = 1
 nusb3co.dll = 1

[DestinationDirs]
 DefaultDestDir = 12
 NUSB3CO.CopyFiles = 11

[Manufacturer]
 %RENESAS% = RENESAS

[RENESAS]
 %NUSB3XHC.DeviceDesc% = NUSB3XHC, PCI\VEN_1033&DEV_0194&REV_03
 %NUSB3XHC.DeviceDesc% = NUSB3XHC, PCI\VEN_1033&DEV_0194&REV_04

[DefaultInstall]
 CopyINF = nusb3xhc.inf

;---------------------
; NUSB3XHC
;---------------------
[NUSB3XHC.NT]
 CopyFiles = NUSB3XHC.CopyFiles

[NUSB3XHC.CopyFiles]
 nusb3xhc.sys

[NUSB3XHC.NT.HW]
 AddReg = NUSB3XHC.AddReg.HW

[NUSB3XHC.AddReg.HW]
 HKR,"Interrupt Management\MessageSignaledInterruptProperties",MSISupported,0x00010001,1

[NUSB3XHC.NT.Services]
 AddService = nusb3xhc, 0x00000002, NUSB3XHC.AddService, NUSB3XHC.EventLog

[NUSB3XHC.AddService]
 DisplayName    = %NUSB3XHC.SvcDesc%
 ServiceType    = 1                 ; SERVICE_KERNEL_DRIVER
 StartType      = 3                 ; SERVICE_DEMAND_START
 ErrorControl   = 1                 ; SERVICE_ERROR_NORMAL
 ServiceBinary  = %12%\nusb3xhc.sys
 LoadOrderGroup = Base

[NUSB3XHC.EventLog]
 AddReg = NUSB3XHC.EventLog.AddReg

[NUSB3XHC.EventLog.AddReg]
 HKR,,"EventMessageFile",0x00020000,"%11%\iologmsg.dll;%12%\nusb3xhc.sys"
 HKR,,"TypesSupported",0x00010001,7

;--- Coinstaller installation -----

[NUSB3XHC.NT.CoInstallers]
 AddReg = NUSB3CO.AddReg
 CopyFiles = NUSB3CO.CopyFiles

[NUSB3CO.CopyFiles]
 nusb3co2.dll,nusb3co.dll,,0x6000

[NUSB3CO.AddReg]
 HKR,,CoInstallers32,0x00010000,"nusb3co2.dll,Nusb3CoInstaller"

[Strings]
 RENESAS = "Renesas Electronics"
 DISKID = "Renesas Electronics USB 3.0 Device Driver Installation Disk"
 NUSB3XHC.SvcDesc = "Renesas Electronics USB 3.0 Host Controller Driver"
 NUSB3XHC.DeviceDesc = "Renesas Electronics USB 3.0 Host Controller"

 

nusb3hub.inf

; ========================================================
; Copyright (c) 2010-2011 Renesas Electronics Corporation
; INF file for installing USB 3.0 hub driver.
; ========================================================

[Version]
 Signature="$Windows NT$"
 Class=USB
 ClassGuid={36FC9E60-C465-11CF-8056-444553540000}
 Provider=%RENESAS%
 DriverVer=10/25/2011,2.1.28.0
 CatalogFile=nusb3hub.cat

[SourceDisksNames]
 1 = %DISKID%

[SourceDisksFiles]
 nusb3hub.sys = 1

[DestinationDirs]
 DefaultDestDir = 12

[Manufacturer]
 %RENESAS% = RENESAS

[RENESAS]
 %NUSB3\ROOT_HUB30.DeviceDesc% = NUSB3HUB, NUSB3\ROOT_HUB30
 %NUSB3\CLASS_09&SUBCLASS_00&PROT_00.DeviceDesc% = NUSB3HUB, NUSB3\CLASS_09&SUBCLASS_00&PROT_00
 %NUSB3\CLASS_09&SUBCLASS_00&PROT_01.DeviceDesc% = NUSB3HUB, NUSB3\CLASS_09&SUBCLASS_00&PROT_01
 %NUSB3\CLASS_09&SUBCLASS_00&PROT_02.DeviceDesc% = NUSB3HUB, NUSB3\CLASS_09&SUBCLASS_00&PROT_02
 %NUSB3\CLASS_09&SUBCLASS_00&PROT_03.DeviceDesc% = NUSB3HUB, NUSB3\CLASS_09&SUBCLASS_00&PROT_03

[DefaultInstall]
 CopyINF = nusb3hub.inf

;---------------------
; NUSB3HUB
;---------------------
[NUSB3HUB.NT]
 CopyFiles = NUSB3HUB.CopyFiles

[NUSB3HUB.CopyFiles]
 nusb3hub.sys

[NUSB3HUB.NT.Services]
 AddService = nusb3hub, 0x00000002, NUSB3HUB.AddService, NUSB3HUB.EventLog

[NUSB3HUB.AddService]
 DisplayName    = %NUSB3HUB.SvcDesc%
 ServiceType    = 1                 ; SERVICE_KERNEL_DRIVER
 StartType      = 3                 ; SERVICE_DEMAND_START
 ErrorControl   = 1                 ; SERVICE_ERROR_NORMAL
 ServiceBinary  = %12%\nusb3hub.sys
 LoadOrderGroup = Base

[NUSB3HUB.EventLog]
 AddReg = NUSB3HUB.EventLog.AddReg

[NUSB3HUB.EventLog.AddReg]
 HKR,,"EventMessageFile",0x00020000,"%11%\iologmsg.dll;%12%\nusb3hub.sys"
 HKR,,"TypesSupported",0x00010001,7

[Strings]
 RENESAS = "Renesas Electronics"
 DISKID  = "Renesas Electronics USB 3.0 Device Driver Installation Disk"
 NUSB3HUB.SvcDesc = "Renesas Electronics USB 3.0 Hub Driver"

 NUSB3\ROOT_HUB30.DeviceDesc = "Renesas Electronics USB 3.0 Root Hub"
 NUSB3\CLASS_09&SUBCLASS_00&PROT_00.DeviceDesc = "Renesas Electronics USB Hub"
 NUSB3\CLASS_09&SUBCLASS_00&PROT_01.DeviceDesc = "Renesas Electronics USB 2.0 Hub"
 NUSB3\CLASS_09&SUBCLASS_00&PROT_02.DeviceDesc = "Renesas Electronics USB 2.0 Hub"
 NUSB3\CLASS_09&SUBCLASS_00&PROT_03.DeviceDesc = "Renesas Electronics USB 3.0 Hub"

 

MKH's picture

I have not been able to load USB 3 drivers for my Asmedia or Etron controller in either the 256 or 512 boot.wim files that are located in templates using Boot Wizard. These files are the ones Ghost created at setup.

I downloaded AIK for Vista at the Microsoft website and created a new boot.wim file and successfully added the drivers.

When I replaced the boot.wim file in templates and tried to create a boot package Boot Wizard refused to create a package because the boot.wim file are not configured to work with Ghost.

When I created a boot package using the default installation Ghost created of Boot Wizard then replaced the boot.wim file in the sources folder of the boot packages it worked like a charm.

Given my experience I would say there is an issue with the default boot.wim files Ghost created at setup that prevents vaild drivers from being added or removed. 

It would also appear some conditions must be met before Ghost will work with a boot.wim file.

In reading the documentation Symantec published with Ghost I have not found any information on how to create a new boot.wim file. It appears when a new file is created in Boot Wizard its really a copy of one that was already there.

My next step will be to exam the contains and attributes of the boot.wim files Ghost created using a third party editor to compare the structure of the file created by Ghost to one created by AIK and to look for any other information that might be impairing the files use under the circumstances. I will report back soon please use my work around until a solution found.

EdT's picture

This article may help: https://www-secure.symantec.com/connect/articles/readyadventures-winpe

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.