Hi guys

I have built xpe image with USB webcam (Video Blaster webcam 5 from
Creative), I beleive I have installed all the components, image was
built without any error including clean dependency check.

During the FBA PNP instalation, I received the dialog to set light
frequencu (50/60 Hz)and after hitting the OK I received the message
"error occured while trying to run "PD100pin.dll RUN DLL32 EP252"
(PD100pin.dll is one of creative files). After that the FBA continue
normally and rebooted.

What is the meaning of this message?

When I check the camera driver in the control panel (Video Blaster
Webcam 5)I see the message "Windows can not load the device driver for
this hardware. The device driver may be corupted or missing (code 39)"

All the other drivers were loaded and running properly (including the
USB drivers). I checked the driver files (details) and found that all
files that exist on the xp pro exist also in the xpe driver.


Any idea what is "code 39"? Is it possible that there is a problem
related to USB 1 or USB 2 compatability?

The device drivers works fine for XP Pro, and I wonder if this problem
is related to the specific PC104 H/W I'm using. How can I check or
verify it?


Yogiv

Hi Yogiv,

Why did you created same new thread?
Have you read Konstantins response? Give us answer there so we can help you further.

Regards,
Slobodan

"Yogiv" <yossi> wrote in message news:04f3
[..]

Yogiv,

You seems to create another thread with the same problem.. have you check the prelies from the first one?

Anyway here is copy/paste...

> I have built xpe image with USB webcam (Video Blaster webcam 5 from
> Creative), I beleive I have installed all the components, I have built
> the image without any error including the dependency check.

Hope that you componentize the driver properly.

> During the FBA PNP instalation, I received the dialog to set light
> frequencu (50/60 Hz)and after hitting the OK I received the message
> "error occured while trying to run "PD100pin.dll RUN DLL32 EP252" (one
> of creative files). After that the FBA continue normally and
> rebooted.(pd100pin.dll one of Creative files)

Did you check the dependecies of PD100pin.dll? And all other driver package files?
Use Dependency Walker to do the check.

Btw, check FBALog.txt and SetupApi.log for more descriptive error descriptions.

> What is the meaning of this message?

It failed on rundll32 execution.

> When I check the driver (Video Blaster Webcam 5)I see the message
> "Windows can not load the device driver for this hardware. The device
> driver may be corupted or missing (code 39)"
>
> All the other drivers were loaded and running properly (including the
> USB drivers).
>
> Any idea what is "code 39"?

Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)
Reasons for this error include a driver that is not present; a binary file that is corrupt; a file I/O problem, or a driver that
references an entry point in another binary file that could not be loaded.
http://www.microsoft.com/resources/d...k_dec_lgsc.asp


> Is it possible that there is a problem related to USB 1 or USB 2 compatability?

It may or may not. Dependency check should be done first.
Make sure to have this QFE installed:
http://www.microsoft.com/downloads/d...displaylang=en

> The device drivers works fine for XP Pro, and I wonder if this problem
> is related to the specific PC104 H/W I'm using. How canI check or verify it?

It may be some software component missing dependencies. As a test option you have XPProEmulation.slx image that can be found on
www.xpefiles.com (Development Utilities/Main).

KM

KM

You are right I posted the same problem again by mistake.

I was not familiar with the dependency walker, its a great tool! when
I ean it for the first time, I was confused with all the warnings and
didn't realize what should I do since almost any file that I checked
results with some or warning such as

"Warning: At least one module has an unresolved import due to a
missing export function in a delay-load dependent module"

and some of them with missing file error message

I found that the file "pd100vid.sys" is missing the "usbcamd.sys"
file. I don't understand why the dependency check didn't identified
it on the host system.

I just copied the file from my host systems to target's
system32/driver folder and it seems to solve the driver problem. I
will add it to the configuration file in the next time I'll build the
image.

What is the best way to resolve such problems on the host system
before gettin the target machine? Is there any posiblity to adjust the
dependedncy check to identify missing files in all leveles?

KM, I appriciate very mush your help


Yogiv


"KM" <konstmor> wrote in message news:3080
[..]

Hi Yogiv,

> What is the best way to resolve such problems on the host system
> before gettin the target machine? Is there any posiblity to adjust the
> dependedncy check to identify missing files in all leveles?

That file is probably in Windows\System32\drivers folder on your development computer.
This is the reason why Dependency Walker found it.

You can look at all files that Walker reported and see if they are missing in your target image, or simply as you did just run
Walker on target device.

Regards,
Slobodan

"Yogiv" <yossi> wrote in message news:da20
[..]

Yogiv,

As Slobodan already mentioned, you are better off running Dependency Walker on your target. But in case it requires some additional
efforts (e.g., satisfying the tool dependencies in a pretty small image, etc.) you may just want to change the directory search
settings in the tool options ("Confugare Module Search Order" menu option).

Also, always use Profiling of the Dependency Walker tool. It will show you all (most) of the dymanic dependencies of the app being
analyzed.

KM
[..]