WinXPTalk.com

MJ · Guest

Hello,
We are having a problem loading a driver for a digital I/O board. Driver is
located in C:\Windows\system32\drivers. Handle to driver retrieved via
CreateFile call with device name.

In Configuration 1,
XPe with Custom Shell and EWF, booted off a CompactFlash in the Primary
master IDE slot. Driver loads with no problem

In Configuration 2,
XPe with Custom Shell and EWF, booted off a CompactFlash in the Primary
master IDE slot. Second CompactFlash card (with random files or with nothing
on it) loaded in either Secondary IDE slot. Primary Master boots as C:
drive. Secondary boots as D: drive.
Driver will not load.

In Configuration 3,
XPe with full Windows Explorer User Interface (no EWF), booted off a
CompactFlash in the Primary Maaster IDE slot. Second COmpactFlash card
loaded in either Secondard IDE slot. Driver loads with no problem.

In all configurations, I checked in our code and the path is correct, the
system directory is C:\windows\system32...everything looks ok. Why does
having the second card in Configuration 2 cause my code to be unable to load
the driver? Any help is appreciated

Thanks!
MJ

Andy Allred [MS] · Guest

Check the setupapi.log (in .\windows) and the fbalog.txt (in.\windows\fba)
for hints as to why your driver is failing.

-andy
--
Embedded team blog: http://blogs.msdn.com/embedded/

This posting is provided "AS IS" with no warranties, and confers no rights.

"MJ" <MJ@discussions.microsoft.com> wrote in message
news:F244C980-E92D-4974-A3D1-8978FFB189DD@microsoft.com...

MJ · Guest

Andy,
The driver isn't failing to load when I run first boot agent. It fails when
I insert a second CompactFlash card. And since I'm using EWF, I couldn't
look at any logs anyway. Is it possible that having the second CF makes
windows think the driver is elsewhere?

"Andy Allred [MS]" wrote:

Slobodan Brcin (eMVP) · Guest

Hi MJ,

If you can copy setupapi.log to unprotected partition and then move it to other computer or use notepad then regardless of EWF you
can see data.
Also you can commit EWF and get your data saved. There are many reasons why reinstalation of driver during the PnP can fail and they
are written in setupapi.log.

Regards,
Slobodan

"MJ" <MJ@discussions.microsoft.com> wrote in message news:DECF8D9E-DEF2-4B76-A5C6-C23D79EE07BD@microsoft.com...

MJ · Guest

Slobodan,
The only extra stuff that shows up in my SetupAPI.log is the installation of
the extra compactflash.

-MJ

"Slobodan Brcin (eMVP)" wrote:

MJ · Guest

Problem Fixed.

I tried sealing the image with all of the compactflash in the slots. Now,
no matter how many of the total CF I have inserted, the Digital I/O board
driver loads fine every time. Does this make sense to anyone??

"Slobodan Brcin (eMVP)" wrote:

Slobodan Brcin (eMVP) · Guest

Hi MJ,

This does not make sense, you are right and I also analyzed your problem.

Only thing that I can think of is following:

1. Your system boot.
2. PnP find second CF.
3. Your IO driver is delayed or not loaded due to PnP timing deviation.
4. Your apliacation try to open driver that is still not ready.

Have you tried to go to console and wait a bit and then start your program?
What is result returned by CreateFile?
Have you tried puting device manager and looking if your driver started?

Only difference that I see in what you described is that PnP is making some delay. You can do easy test to verify this by:
After booting computer and having that problem with your driver when new disk is found. Just comming EWF and reboot computer and see
if your driver start working.

Also do you have some delay in your aplication to that will wait for PnP activity to setle down before opening driver? You should
have this.

Regards,
Slobodan

"MJ" <MJ@discussions.microsoft.com> wrote in message news:D02DDA7A-F4A2-4573-B590-C74BDBAC4F61@microsoft.com...

	WinXPTalk.com Forum Index -> Embedded System	All times are GMT
Page 1 of 1