FBA Generic Command Problem

  • Thread starter Thread starter black_13
  • Start date Start date
B

black_13

I have created a FBA Generic Command to run a batch script.
The Arguments to the FBA Generic Command are
/c %11%\force_ati.bat
and the FilePath is
%11%\cmd.exe
the contents of the batch file are

devcon install C:\2KXP_INF\CX_22513.inf "PCI\VEN_1002&DEV_4C66"

when manually launch this batch file it works correct and installs the
ati
drivers for the chipset on the board i am using but.
Here is what the fba log reports.

19:24:05 PM - [FBALaunch] C:\WINDOWS\system32\cmd.exe /c
C:\WINDOWS\system32\force_ati.bat (ExitCode: 0x2)
basically it fails to work
what gives?
 
Hi Black

Don't use the %11% variables in the
FBA resources. This variables are good until
the build step.
The FBA can't work with them.
Use the %systemroot% ones....

i.e.:

/c %SYSTEMROOT%\system32\batch.bat

For the file, it's ok to use %11% because this is used
during the build session.

find a batch example under www.xpefiles.com
(Software -> Passwor Unlimit)


--

Martin Grossen, eMVP

AVNET EMG Silica
Franchise Manager Microsoft Embedded Europe

Your competent partner for Microsoft Embedded licencing

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
Basically NVIDIA and ATI drivers are full of additional "garbage" (some people like nice GUI to install drivers and that GUI take 20
MB and resources). Actual drivers are one inf file and1 or 2 dll,sys files.
Unfortunately inf file reference all that nice GUI things that go to control panel tray etc and those things require some huge
support from operating system functionality.

Two approaches:
1. Cut all unnecessary stuff from inf file. And put that inf, dll, sys files in their rightful folders before FBA start. PnP will
detect best match for your hardware and pick inf file and by doing that your drivers will be installed.
2. Add all things necessary for PnP to be able to complete full driver installation.

In both cases you must make sure that your video component copy all files to their destination XPe folders and that you do not use
component generated by regular import in CD since that will prepopulate registry with keys that can prevent PnP from completing the
job.

Anyhow if something do not work look at setupapi.log to see that went wrong in PnP.

Regards,
Slobodan
 
Back
Top