Running a driver application

sirish,

Would you mind to explain what you meant by "driver application"?
Is it an installer for a driver or something else?

If you're talking about a driver installer...
There could be many reasons why it runs differently on XPe vs XPP. E.g.:
- the installer checks for the OS version to change the install code path.
- the installer checks for a presence of specific components (Dll, etc.) and that may affect the code path as well.
- some error handling of the installer app may affect its code routes. (keep in mind that it may have happened that your XPe
image doesn't have all the components required by the installer)
- etc.

Too look more carefully at he problem you'd probably need to send out a bit more info (e.g., be specific about what you're trying to
install, FileMon logs, etc.)


--
=========
Regards,
KM

> Hi,
> The driver application run on XPe OS seems to be running differently. I
> mean, different files are being accessed when the same executable is run from
> XP prof and XPe (learnt using FileMon tool). The different behaviour starts
> after half the similer process.
>
> Can some one please describe what could be the reason?
>
> Regards

Sirish,

The exe you are referring to may be checking the state of the driver you mentioned and if installed (load and run) properly it may
execute one code path but if not - another.

Without knowing what that executable does it is going to be hard to guess what's missing from your image.

I left more comments in another thread you created.

--
=========
Regards,
KM

> Hi KM,
> Sorry for the vague description earlier! You are right the new thread posted
> today refers to this question only.
>
> Following are the details.
> It was about Kvaser PCIcan driver on my XPe image. I componentized the
> kvaser s/w provided by importing its INF file.
> The installation should show: CAN h/w (Kvaser) - 1)Kvaser PCIcan 2) Kvaser
> Virtual CAN driver, in the device manager.
> The two (I guess) go in combination and consists of the h/w driver and GUI
> based interactive 'CAN bus monitor/analyzer'.
>
> The problem is even on including the corresponding components of 1&2 while
> building my image, I see only CAN h/w (Kvaser) - 1)Kvaser PCIcan, in the
> device manager.
> When I try to open the corresponding exe file to open the analyser, it gives
> error which says 'Configuration program could not be started. Try to
> reinstall the driver'!
>
> I used 'depends' tool to check if any file is missing but no. I then used
> 'filemon' and 'depends-profile' tools on which I understand though all the
> files are present, the execution procedure is different. Example: After
> executing (file calls and results being) exactly the same way on both
> platforms, a call to 'COMCTL32.DLL' is made on XPe where as a call to
> 'SHLWAPI.DLL' is being made on XP-prof.
>
> The last few similer file calls before they differ are for: ... USER32.DLL,
> GDI32.DLL, WINSPOOL.DRV. Later on their excution is entirely different.
>
> You suggested, the path of installation may vary. Does it apply in my case
> (I mean even when I import from INF file)? Any suggestions what components
> could possibly be missing in my XPe image?
>
> Regards
> Sirish
>
> "KM" wrote:
>

Hi KM,
As mentioned earlier, the driver is being installed but the analysis
tool/application is not getting installed!
I was trying to get some clue setupapi.log, but, there is no referance to
this component at all! I see "#W154 Class installer failed. Error 0xe0000202:
An existing device was found that is a duplicate of the device being manually
" error.
Can you give me any clues please?
Rgds
Sirish

"KM" wrote:

> Sirish,
>
> The exe you are referring to may be checking the state of the driver you mentioned and if installed (load and run) properly it may
> execute one code path but if not - another.
>
> Without knowing what that executable does it is going to be hard to guess what's missing from your image.
>
> I left more comments in another thread you created.
>
> --
> =========
> Regards,
> KM
>
>

>
>
>

I Have got another observation: I do see the analysis toll component during
build process but it doesn't show the component name when showing the
estimated component sizes!
Any guesses?


"KM" wrote:

> Sirish,
>
> The exe you are referring to may be checking the state of the driver you mentioned and if installed (load and run) properly it may
> execute one code path but if not - another.
>
> Without knowing what that executable does it is going to be hard to guess what's missing from your image.
>
> I left more comments in another thread you created.
>
> --
> =========
> Regards,
> KM
>
>

>
>
>

You may want to show us the entire log. (the best would be to attach it here if you used news reader client like OE)

--
=========
Regards,
KM


"sirish" <sirish@discussions.microsoft.com> wrote in message news:65B93E1B-A2F4-40E5-A6AC-5B180C36674A@microsoft.com...

> Hi KM,
> As mentioned earlier, the driver is being installed but the analysis
> tool/application is not getting installed!
> I was trying to get some clue setupapi.log, but, there is no referance to
> this component at all! I see "#W154 Class installer failed. Error 0xe0000202:
> An existing device was found that is a duplicate of the device being manually
> " error.
> Can you give me any clues please?
> Rgds
> Sirish
>
> "KM" wrote:
>

sirish,

Is it possible for you to share the component with us here? I can check the component integrity and let you know if it was properly
created.

Also, are you sure your component includes all the files for the drivers? Did you create a repository and associated it with the
component? Does you pre-FBA image include all the files for the driver located in the corresponding folders (\windows\inf,
\windows\system32, \windows\system32\drivers, etc.).

--
=========
Regards,
KM

>I Have got another observation: I do see the analysis toll component during
> build process but it doesn't show the component name when showing the
> estimated component sizes!
> Any guesses?
>
>
> "KM" wrote:
>