Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Tecra A11 fails DeployAnywhere, INF file is correct

Updated: 22 May 2010 | 10 comments
logik's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Hi all,

I've been using GSS 2.5/2188 for some time now and have run into a problem running DeployAnywhere on a Toshiba Tecra A11.

I've obtained the latest PROSET drivers (15.1) and incorporated them into the Driver Database. I have also included them in
my PXE boot image.

When i run DeployAnywhere, it passes the first check (Evaulate Deploy Anywhere), copies the files over and then fails on
'Deploy Anywhere'.

I've manually run a DeployAnywhere in the WinPE with the following results;

X:\GHOST>ghdplyaw32 /target=c:\windows /ddb=c:\ddb
Using Driver Database = C:\ddb
Target OS = XP
Target = C:\WINDOWS
Retargeting...
A cancel has been requested.

Missing drivers detected:

Device type  : Network Device
PCI ID       : PCI\VEN_8086&DEV_10EA&SUBSYS_00011179&REV_06
Description : Device Description Unavailable

Error

But if we check C:\DDB (where DeployAnywhere put the required files);

            path = "microPE - PRO1000 15.1\\Win32\\NDIS5x\\e1k5132.inf",
            devices = {
                0x8086 = {
                    0x10de = (0x10de8086 0x10de8086),
                    0x10df = (0x10df8086 0x10df8086),
                    0x10ea = (0x11179),
                    0x10eb = (0x11179),
                    0x10ef = (),
                    0x10f0 = ()
                }
            },
            os = ("XP" "VISTA")

Why is DeployAnywhere failing to see files it has already copied?

James

Discussion Filed Under:

Comments

pashyn's picture
24
Mar
2010
0 Votes 0
Login to vote

run debug

Hi,

run debug using this command
ghdplyaw32 /target=c:\windows /ddb=c:\ddb /debug

and attach log file here

logik's picture
24
Mar
2010
0 Votes 0
Login to vote

I've included ghDplyAw32.txt

I've included ghDplyAw32.txt from the same session (left the laptop on after my last post)

AttachmentSize
ghDplyAw32.txt 473.12 KB
pashyn's picture
24
Mar
2010
0 Votes 0
Login to vote

From your debug file i can

From your debug file i can see these errors

* 2010-03-24T09:03:29.9744765Z Main Thread(1676)     Context: RESULT_CLASS : RESULT
e7d1000e
1: C:/ddb/pcidevs.txt
Error FILEACCESS_ERROR_CANT_OPEN_1_DOESNT_EXIST (E7D1000E): Unable to open 'C:/ddb/pcidevs.txt'. It does not exist.


and

* 2010-03-24T09:03:29.9745108Z Main Thread(1676)     Context: GEM : INFO
Event: EVENT_DRIVER_MEDIA_REQUIRED: The following driver media is required: %1.
+ "3"
   "PCI\VEN_8086&DEV_10EA&SUBSYS_00011179&REV_06"
   "Device Description Unavailable"



Try to copy attached
pcidevs.txt to C:/ddb/   if it helps

AttachmentSize
pcidevs.txt 841.04 KB
pashyn's picture
24
Mar
2010
0 Votes 0
Login to vote

if that dont help attach

if that dont help attach e1k5132.inf here. I had similar issue with Lenovo drivers that i had to manyally modify.
see my case https://www-secure.symantec.com/connect/forums/deploy-anywhere-fails-lenovo-t410-and-lenovo-w510

logik's picture
24
Mar
2010
0 Votes 0
Login to vote

Hi Pashyn, I copied this file

Hi Pashyn,

I copied this file to c:\ddb and renamed it back to 'pcidevs.txt'.
I re-ran the existing command 'ghdplyaw32 /target=c:\windows /ddb=c:\ddb /debug' and received the following output:

X:\GHOST>ghdplyaw32 /target=c:\windows /ddb=c:\ddb /debug
Using Driver Database = C:\ddb
Target OS = XP
Target = C:\WINDOWS
Retargeting...
A cancel has been requested.

Missing drivers detected:

Device type  : Network Device
PCI ID       : PCI\VEN_8086&DEV_10EA&SUBSYS_00011179&REV_06
Description : Intel

Parameters :
        target = c:\windows
        ddb = c:\ddb
        eval = False
        managedMode = False
        debug = True
        captureSupportInfo =

Error

I've included the ghDplyAw32.txt output i received with it...

James

AttachmentSize
ghDplyAw32.txt 472.84 KB
logik's picture
24
Mar
2010
0 Votes 0
Login to vote

Hi Pashyn, I read the post

Hi Pashyn,

I read the post you mentioned earlier. I've already checked e1k5132.inf and it contains the correct subsystem
code.

I've attached my e1k5132.inf just in case.

James

AttachmentSize
e1k5132.zip 12.73 KB
pashyn's picture
24
Mar
2010
0 Votes 0
Login to vote

ok this is same issue that i had

ok this is same issue that i had!

attach your e1k5132.ini here and i can fix it for you

ok now i see your attchment... wait a sec

pashyn's picture
24
Mar
2010
0 Votes 0
Login to vote

use this edited version.

use this edited version. Overwrite existing ini with this one.

AttachmentSize
e1k5132.zip 13.4 KB
logik's picture
24
Mar
2010
0 Votes 0
Login to vote

This worked; i also bumped

This worked; i also bumped into an issue with the SATA controller - but your INF file did the trick.

pashyn's picture
19
Apr
2010
0 Votes 0
Login to vote

good!

Im glad it worked. Could you mark my message with working driver as a solution?