structure of ati drivers and inf file.

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

black_13

In posting made buy Slobodan Brcin (Dec 24 2003, 6:27)

He stated that:

....ATI separated their driver to few dll's so you can leave out even
opengl
or some other irrelevant feature for your product.

When you determine minimum required sys/dll files (for NVIDIA only two
files), and create inf file.

My question is this what files (dll/sys) are needed? Can this be
determined
by the INF file supplied by ATI. Also are were you (Slobodan)
suggesting that a '
new INF file need to be made in that post?
Then he (Slobodan) stated "let PnP do the rest. " what does that mean.


Thanks
 
I was checking on a post I made a week ago that got no replies, and
noticed this one, so, here is something to get you started.

Many previous posts in this news groups have suggested that you can
determine what files are actually required by installing the driver on
a running system and monitoring the results.

Monitoring methods include:
a) Sys Internals FileMon, Regmon programs
b) C:\Windows\SetupAPI.log
c) Any log or uninstall info generated by the program.
(Varies, look for folders containing the manufacturers name,
such as C:\ATIxxx, or C:\Program Files\XXX, or C:\Windows\Temp\
or in C:\Documents and Settings\Username\LocalSettings\Temp\.)

Or, you can install the full driver, and start deleting files until it
stops working.

These processes can be quite tedious, and require a lot of testing to
determine that all of the features that you need are still working.

As for PNP doing the rest, i think that this means something like this:
(Correct me if I'm wrong here)
1) Copy the inf file to C:\Windows\Inf
2) Copy the driver (.sys) file to C:\Windows\System32\Drivers.
3) reboot system - PNP init automatically starts driver.

Or you can use the device manager or devcon.exe to manually install the
driver by browsing for the inf file.

Usually you can learn a lot about this type of topic by using Google
groups to search the newsgroup archives, as these topics occur
repeatedly.

1. Goto www.google.com
2. Click on Groups
3. locate the group of interest.
4. Use the 'search this group' box to search only this group

Good luck!!
SteveSATeyeDASHimagingDOTcom
 
Im glad you wrote back this give me an opportunity
to write back what I found out and give things
to those how have help me out.

First it looks the the ATI drivers that come in the
install file 5-5-edg_xp-2k_dd_cp_wdm.exe expect to be
"installed" on a machine where the windows install is
on the C: drive. In my previous experiments the development
environment on the "C:" drive and the target was on "D:".
When I attempted to install inf file in directory
5-5-edg_xp-2k_dd_cp_wdm\Driver\2KXP_INF\CX_22513.inf
using hardware wizard there was invariable an error
about a missing section in the inf file.

The first thing I did was to change how devel system
was layed out. The development drive was left unchaged
on the "C:" drive, but I formated the second drive and
installed mandrake linux but with a one fat partion and
grub as the boot loader. Grub give me the freedom on
what to boot. When I boot into the developent machine I
I see the target drive as D. But when i use grub to boot
the new XPE install it is the "C:" drive.

As far as componetizing the ATI drives I have given
up but opted for easier approach I "componetize" the
all the files from the section:
..\5-5-edg_xp-2k_dd_cp_wdm\Driver\2KXP_INF
..\5-5-edg_xp-2k_dd_cp_wdm\Driver\2KXP_INF\B_23265
But by componetize I mean i just copy files on the target
drive to the directory C:\2KXP_IN, I make not attempt
to install anything using the fba pnp process.
(I guess that is what happens with a drive component that
has an inf file).

After the FBA process completes I can execute the command
devcon install C:\2KXP_INF\CX_22513.inf "PCI\VEN_1002&DEV_4C66"
to install the ATI 9000 MOBILITY DRIVERS.

Also one the things i was missing was install the
class installers for display adapters.
(thanks Heidi Linda or is Linda Heidi heh!)

The next step I am currently struggling with is
getting a working fba resource/command that will run the above
devcon command automatically.
I keep getting
R: Error 1004: Invalid resource: "Run Cmd Shell"

Thanks to Heidi Linda
and Brad Combs
 
Hi Black,

Yes I have stated those things.
If you analyze each file from Dependency Walker you will see dll's that this file is using and based on that it is easy to tell if
that dll is executing in user mode or in kernel space.
After analysis you will determine that only few files are executing in kernel space and those are drivers rest of files are used for
providing visual support for control panel and tray think that they though you will need on regular computer.
Now for those services and dll to install and start you need much more support in your XPe image.

For installing driver on 50-60 MB XPe image you usually do not have all those things and PnP during the driver installation will
refuse to complete install.

Only thing that you can do is to use text editor and create your inf file from original one that will not reference any of files
that are not executing in kernel space. For that you need to know what each section in inf file does and then you can remove all
extras safely.

So if you have custom inf file and dll,sys files if you place them in pre FBA image in infs, system32 and drivers folders
respectively, they will be recognized and installed by XPe itself during the FBA (PnP) phase.

Regards,
Slobodan
 
so what you saying is not componetize the drivers but instead to place
them in the winnt/inf, winnt/drivers winnt/system32 ? and the FBA pnp
stage will do the rest.
(just as long inf file will run correctly)
also thanks again slobodan
black_13
 
Back
Top