> Yes, we have.
The problem occurs only when the system sees the device for the first time. Once the device is installed, the driver is always loaded during the boot.
Thanks for the reply,
Gregory
Well, I am not at all qualified to answer this question but my
understanding was that at some point, somehow, someone with admin
privilege must okay the addition of a driver for a new device.
Ok, but this does not happen for disk devices. The disk driver is always loaded immediately when a new disk PDO is reported by the port driver. Finding the reason for the difference between the disk driver and our driver would help us a lot, but we failed to find it till this moment.
Thanks for the reply,
Gregory
-----Original Message-----
From: Robert Newton [mailto:xxxxx@telusplanet.net]
Sent: Wednesday, March 24, 2004 17:59
To: Windows System Software Devs Interest List
Subject: Re[2]: [ntdev] Installation of a new device before login
Yes, we have.
The problem occurs only when the system sees the device for the first time. Once the device is installed, the driver is always loaded during the boot.Thanks for the reply,
Gregory
Well, I am not at all qualified to answer this question but my
understanding was that at some point, somehow, someone with admin
privilege must okay the addition of a driver for a new device.
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@store-age.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
*** IMPORTANT: Do not open attachments from unrecognized senders ***
******************************************************************************************
The contents of this email and any attachments are confidential.
It is intended for the named recipient(s) only.
If you have received this email in error please notify the system manager or the
sender immediately and do not disclose the contents to any one or make copies.
******************************************************************************************
************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************
The drivers for ‘disks’ have already been loaded and qualified. A new disk
is just anther instance. Your device is not in the same category at all.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gregory Dardyk
Sent: Wednesday, March 24, 2004 11:49 AM
To: Windows System Software Devs Interest List
Subject: RE: Re[2]: [ntdev] Installation of a new device before loginOk, but this does not happen for disk devices. The disk
driver is always loaded immediately when a new disk PDO is
reported by the port driver. Finding the reason for the
difference between the disk driver and our driver would help
us a lot, but we failed to find it till this moment.Thanks for the reply,
Gregory-----Original Message-----
From: Robert Newton [mailto:xxxxx@telusplanet.net]
Sent: Wednesday, March 24, 2004 17:59
To: Windows System Software Devs Interest List
Subject: Re[2]: [ntdev] Installation of a new device before login> Yes, we have.
> The problem occurs only when the system sees the device for
the first time. Once the device is installed, the driver is
always loaded during the boot.
>
> Thanks for the reply,
> GregoryWell, I am not at all qualified to answer this question but
my understanding was that at some point, somehow, someone
with admin privilege must okay the addition of a driver for a
new device.
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256You are currently subscribed to ntdev as:
xxxxx@store-age.com To unsubscribe send a blank email to
xxxxx@lists.osr.com*** IMPORTANT: Do not open attachments from unrecognized senders ***
**************************************************************
****************************
The contents of this email and any attachments are confidential.
It is intended for the named recipient(s) only.
If you have received this email in error please notify the
system manager or the sender immediately and do not disclose
the contents to any one or make copies.**************************************************************
******************************************************************************************
**********************
This footnote confirms that this email message has been
scanned by PineApp Mail-SeCure for the presence of malicious
code, vandals & computer viruses.
**************************************************************
**********************
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256You are currently subscribed to ntdev as:
xxxxx@hollistech.com To unsubscribe send a blank email to
xxxxx@lists.osr.com
If you driver has been WHQL certified, and the device is not legacy
(i.e. it has a real bus-enumerated PnP ID), and you have installed the
driver at some prior point by copying your driver files/INF somewhere
and calling SetupCopyOEMInf (while logged in as an administrator),
normally the driver should be installed without the Add New Hardware
wizard popping up.
Are all 3 conditions satisfied (especially that last one… if not, how
would the OS know how to install your driver)?
If you haven’t installed the driver prior to your hardware being plugged
in, the OS would have to install it when it sees the device, but in
order to do this it needs a UI, and needs to know that a logged in user
has permission to install the driver.
Gregory Dardyk wrote:
Hello
We develop a driver for a device that is connected using Fibre Channel. The problem is that if we connect a new device to the SAN when the server is turned off and then turn the server on, the driver for the new device is installed only after a user logs in. The PDO for the device is created by the port driver immediately when it (the port driver) is loaded, but for some reason the PnP Manager does not load the function driver until a user logs in. Once a user is logged in, a “New Hardware Found” window pops up and the function driver is loaded automatically without any problem. The function driver is Windows certified, so this is not the problem. Also, if we reboot the server after the device was installed, the FDO is created during the boot as we expect.
Is there any way to cause the system to load the function driver during the boot and not to wait for login?Thanks in advance,
Gregory
–
…/ray..