Installation of a new device before login

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

Have you changed Start to Boot (0)?


Gary G. Little
Seagate Technologies, LLC

“Gregory Dardyk” wrote in message
news:xxxxx@ntdev…
> 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
>

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

-----Original Message-----
From: Gary G. Little [mailto:xxxxx@sbcglobal.net]
Sent: Wednesday, March 24, 2004 00:18
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Installation of a new device before login

Have you changed Start to Boot (0)?


Gary G. Little
Seagate Technologies, LLC

“Gregory Dardyk” wrote in message
news:xxxxx@ntdev…
> 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
>


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.