driver

  • Thread starter Thread starter YULUNYEH
  • Start date Start date
Y

YULUNYEH

I am just beginner with XPE. Anyone has any tools or any suggestion to
packing driver, so it will not become blue-screen to FBA.

Mike
 
Hi, All

I have a similar problem: the driver I need is deployed as an Install
Shield executable package. I got all the files when I just start the
package instalation and grab them from the temporary folder (then I
just cancel the instalation). There are some well known INF, SYS, DLL
and CAT files, as well as some CAB and EXE. Inside one of this CAB is
where I've got the INF and some others.

How do I get to know which files will I really need? Just the ones
mentioned by the "INF" file are enough? What about the others?
Should I pack them also?

Thanks
Francisco
 
I have the same problem. My ZIP contains INF,SYS, DLLs, EXEs you name it. I
copied all of them to one flat directory called "Rep". Then I imported the
INF, saved it.. Added a repository , named it Rep and set the path to
C:/Rep/, then I selected the component tab and set the Repository name to
Rep.

I built the image, I can see the INF and SYS in windows/inf and
windows/system32/drivers. But I don't see all the other files in the final
build image. Do I have to create a CAT file and include that to the component
?.

Please help.
 
Do you mean you see only some files getting copied from the same repository folder to the final image build? That sounds like a
weird behaviour. Do you want to check if the repository is created and contains all the files ? (check it out under the XPe
Repository share on your dev machine)

CAT files are not required under XPe.
 
Francisco,

Unfortunately, it is only the driver developer (or you - doing the reverse engineering) knows what files are for.
In most cases it is recommended to include all the files you've got within the driver package (exception may be help files and such
but even those sometimes may be critical, for instance for printer drivers). You certainly have to add the files to your component
keeping the file structure that is created by the Install wizard of that driver. This may not be the hardest part since you can
always "catch" all the files locations with tools like RegSnap or FileMon.
it is more difficult to catch some custom script actions that may be performed by the Install app. that is where you'd use tools
like FileMon/Regmon/Processor Monitor and such.

When you starting optimizing your image footprint you can remove some files from the component but it will be trial-and-error
process unless you are very familiar with the driver implementation.
 
I thought when you create a Repository (Add Repository) all the files in the
Repository will be included in the final build image. I was wrong. The build
picks up only the files included in the Component -> Add Files. I didn't have
all the other files to the Component-Add Files. The build had only 2 files
INF and SYS. I added all the other files I required to Component->Add Files,
I set the path to %24% now I got all the files in the final build.
 
Back
Top