Hi,

I was wondering if anyone else has experienced the
following problem (and hopefully know of a solution!):

I am running windows 2000, and frequently connect 1394
cameras to the computer. Normally, when a new camera is
connected to the computer the inf files should be scanned
to find a compatible driver and it should be loaded. At
which point the camera should appear under "Imaging
Devices" in the device manager. This whole process should
take a few seconds.

What I am experiencing is that each time I connect a new
camera the time it takes to appear under "Imaging Devices"
in Device Manager takes longer and longer. The difference
is quite small, but after >100 cameras it takes several
minutes to appear in Device Manager.

I have tried cleaning out all registry entries associated
with the cameras and their driver, but nothing (short of
formatting the hard drive) seems to work.

Any ideas??

Thanks!
Erik

Mr. Maddy,

Thanks for the reply.

100 cameras with different vendor & chip IDs (each 1394
device is required to have a unique vendor & chip ID
combination). Most of the camera's use the same INF file,
there are at most 3 or 4 different INF files used by these
camera's.

Also, if I try going through Device Manager and updating
the driver I can see where it is searching for the driver
and there is a long delay before it begins searching the
INF directory.

Any other ideas?

Erik

Dear Mr. Egsgard:

Maybe you can use the setupapi log to track down the problem?

==

You can find the information about using SetupAPI logging from the DDK
documentation in this section "Using SetupAPI Logging". That log file
(namely setupapi.log) is available in the system root folder. How to set
different logging levels is explained in the DDK documentation. One
suggested level is 0x2000ffff, so what you need to do is to create or set
the following registry variable:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Setup]
"LogLevel"=dword:2000ffff

==

We would be happy to assist you further if you wish to open a support
incident.

Regards,

Dan Maddy

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