I have a 1394 device, it installs and runs fine on both Win2000 and WinXP.
However, on Windows 2000 the HardwareID value in “HKLM\SYSTEM
\CurrentControlSet\Enum” for the device is NULL and on Windows XP it has
the correct value.
Is this normal or am I missing something in my setup stuff? This might be
causing my problems with “UpdateDriverForPlugAndPlayDevices” on Win2000.
Thanks,
JimA
Do you have dashes, slashes, or other separator characters in the name of
your device in the configuration rom? That has caused me problems in the
past. I don’t remember exactly what characters are bad, I just refrain from
using any one of them, just to make sure.
That may not be the source of the problem you are seeing. It’s just an idea
that popped to my mind.
Mat
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of James Austin
Sent: Tuesday, July 27, 2004 1:26 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Quickie questionon 1394 device installation
I have a 1394 device, it installs and runs fine on both Win2000 and WinXP.
However, on Windows 2000 the HardwareID value in “HKLM\SYSTEM
\CurrentControlSet\Enum” for the device is NULL and on Windows XP it has
the correct value.
Is this normal or am I missing something in my setup stuff? This might be
causing my problems with “UpdateDriverForPlugAndPlayDevices” on Win2000.
Thanks,
JimA
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@encentrus.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
From the DDK (IRP_MN_QUERY_ID topic), here are the rules for illegal
chars in (bus, device, hw, compat) IDs:
Less than 0x20 (’ ‘)
Greater than 0x7F
Equal to 0x2C (’,')
Additionally a driver must conform to the following length restrictions
for IDs:
1 Each hardware ID or compatible ID that a driver returns in this IRP
must be less than MAX_DEVICE_ID_LEN characters long. This constant
currently has a value of 200 as defined in sdk\inc\cfgmgr32.h.
2 If a bus driver supplies globally unique instance IDs for its child
devices (that is, the driver sets DEVICE_CAPABILITIES.UniqueID for the
devices), then the combination of device ID plus instance ID must be
less than (MAX_DEVICE_ID_LEN - 1) characters. The OS requires the
additional character for a path separator.
3 If a bus driver does not supply globally unique instance IDs for its
child devices, then the combination of device ID plus instance ID must
be less than (MAX_DEVICE_ID_LEN - 28). The value of this equation is
currently 172.
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Mathieu Routhier
Sent: Tuesday, July 27, 2004 1:25 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Quickie questionon 1394 device installation
Do you have dashes, slashes, or other separator characters in the name
of
your device in the configuration rom? That has caused me problems in
the
past. I don’t remember exactly what characters are bad, I just refrain
from
using any one of them, just to make sure.
That may not be the source of the problem you are seeing. It’s just an
idea
that popped to my mind.
Mat
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of James Austin
Sent: Tuesday, July 27, 2004 1:26 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Quickie questionon 1394 device installation
I have a 1394 device, it installs and runs fine on both Win2000 and
WinXP.
However, on Windows 2000 the HardwareID value in “HKLM\SYSTEM
\CurrentControlSet\Enum” for the device is NULL and on Windows XP it has
the correct value.
Is this normal or am I missing something in my setup stuff? This might
be
causing my problems with “UpdateDriverForPlugAndPlayDevices” on Win2000.
Thanks,
JimA
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@encentrus.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
I double checked the device ID and see nothing wrong with it. I also
found a mention in the MSDN that under some circumstances the 1394 bus
driver can return nothing for the device ID, need to investigate that
further. But it does work fine under Windows XP.
JimA
“Doron Holan” wrote in news:xxxxx@ntdev:
> From the DDK (IRP_MN_QUERY_ID topic), here are the rules for illegal
> chars in (bus, device, hw, compat) IDs:
>
> Less than 0x20 (’ ‘)
> Greater than 0x7F
> Equal to 0x2C (’,')
>
> Additionally a driver must conform to the following length
> restrictions for IDs:
>
> 1 Each hardware ID or compatible ID that a driver returns in this IRP
> must be less than MAX_DEVICE_ID_LEN characters long. This constant
> currently has a value of 200 as defined in sdk\inc\cfgmgr32.h.
>
> 2 If a bus driver supplies globally unique instance IDs for its child
> devices (that is, the driver sets DEVICE_CAPABILITIES.UniqueID for the
> devices), then the combination of device ID plus instance ID must be
> less than (MAX_DEVICE_ID_LEN - 1) characters. The OS requires the
> additional character for a path separator.
>
> 3 If a bus driver does not supply globally unique instance IDs for
> its child devices, then the combination of device ID plus instance ID
> must be less than (MAX_DEVICE_ID_LEN - 28). The value of this equation
> is currently 172.
>
> d
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Mathieu
> Routhier Sent: Tuesday, July 27, 2004 1:25 PM
> To: Windows System Software Devs Interest List
> Subject: RE: [ntdev] Quickie questionon 1394 device installation
>
> Do you have dashes, slashes, or other separator characters in the name
> of
> your device in the configuration rom? That has caused me problems in
> the
> past. I don’t remember exactly what characters are bad, I just
> refrain from
> using any one of them, just to make sure.
>
> That may not be the source of the problem you are seeing. It’s just
> an idea
> that popped to my mind.
>
> Mat
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of James Austin
> Sent: Tuesday, July 27, 2004 1:26 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Quickie questionon 1394 device installation
>
> I have a 1394 device, it installs and runs fine on both Win2000 and
> WinXP.
>
> However, on Windows 2000 the HardwareID value in “HKLM\SYSTEM
> \CurrentControlSet\Enum” for the device is NULL and on Windows XP it
> has
>
> the correct value.
>
> Is this normal or am I missing something in my setup stuff? This might
> be
> causing my problems with “UpdateDriverForPlugAndPlayDevices” on
> Win2000.
>
> Thanks,
>
> JimA
>
> —