unsigned two part INF multi-port installs under XP

NTDEV
1

We have a two part INF install that we use to install our multi-port
serial boards. One INF is for the board or bus driver and the other part
is for the Ports.

We make use of cocpyinf to help streamline the installs under XP and 2000,
but we have been having problems with the install stopping as it installs
each child serial port, generally to warn about it not being a signed
driver. We intend to have this driver signed soon but in the mean time
our customers will find being bothered about each child serial port
install by the Unsigned Driver Nag screen a less than good user
experience.

Is there any good way around this?

Any insight would be great.

sincerely
Al
xxxxx@golden.net

2

Copyinf itself really does end up generating this unsigned driver popup;
what’s worse, the popup indicates that its because of an “Unknown package”
rather than specifying the name of the driver being installed as is normally
the case.

However, I’m not convinced this is the cause of your problem - if you are
seeing an ‘unsigned driver’ popup that NAMES your serial port driver, then
that is just life; you will get this popup for each INSTANCE of a device
that is being installed with an unsigned driver; thus until you get your
whole package signed, you are going to see n+m+1 of these popups (where n is
the number of serial ports and m is the number of inf files copied by
copyinf).

/simgr

-----Original Message-----
From: Allan Smith [mailto:xxxxx@connecttech.com]
Sent: Tuesday, April 30, 2002 3:16 PM
To: NT Developers Interest List
Subject: [ntdev] unsigned two part INF multi-port installs under XP

We have a two part INF install that we use to install our multi-port
serial boards. One INF is for the board or bus driver and the other part
is for the Ports.

We make use of cocpyinf to help streamline the installs under XP and 2000,
but we have been having problems with the install stopping as it installs
each child serial port, generally to warn about it not being a signed
driver. We intend to have this driver signed soon but in the mean time
our customers will find being bothered about each child serial port
install by the Unsigned Driver Nag screen a less than good user
experience.

Is there any good way around this?

Any insight would be great.

sincerely
Al
xxxxx@golden.net

You are currently subscribed to ntdev as: xxxxx@stratus.com
To unsubscribe send a blank email to %%email.unsub%%