Re: Whar are invalid characters in a hardware or compatible id?
- From: "Doron Holan [MS]" <doronh@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 24 Oct 2006 21:54:46 -0700
looking up the document for IRP_MN_QUERY_ID gives you this information, did
you even try to search this out onyour own?
<ddk>
If a driver returns an ID with an illegal character, the system will bug
check. Characters with the following values are illegal in an ID for this
IRP:
Less than 0x20 (' ')
Greater than 0x7F
Equal to 0x2C (',')
</ddk>
d
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Stefan Kuhr" <kustt110@xxxxxx> wrote in message
news:ue1pzL19GHA.4404@xxxxxxxxxxxxxxxxxxxxxxx
Hello everyone,
I need to know an ASCII character that is definitely invalid in a hardware
or compatible ID. Our software has to send the hardware IDs and compatible
IDs of a Windows client via a Webservice interface across the wire.
Somewhere in the remote logic a third party LDAP parser comes into play
which is so buggy that it gets entirely confused by backslashes as they
appear in hardware IDs or compatible IDs. So as a workaround I would like
to replace all backslashes in the hardware IDs I find via setupapi and
cfgmgr32 APIs with a surrogate character so the LDAP parser (hopefully)
will work. When the result is then written into the database behind all
the stuff, we would then dutifully convert all surrogate characters back
into backslashes.
I noticed that devcon uses the asterisk symbol ('*') as a wildcard
character and that it uses the @ symbol to distinguish instance IDs from
hardware or compatible IDs. Can I therefore safely assume that * and @ are
invalid characters in a hardware ID so I can safely use them as my
surrogate character?
Any help appreciated,
--
Stefan Kuhr
"Lesen schadet der Dummheit"
.
- Follow-Ups:
- Re: Whar are invalid characters in a hardware or compatible id?
- From: Stefan Kuhr
- Re: Whar are invalid characters in a hardware or compatible id?
- References:
- Whar are invalid characters in a hardware or compatible id?
- From: Stefan Kuhr
- Whar are invalid characters in a hardware or compatible id?
- Prev by Date: Re: data cd IOCTL_CDROM_RAW_READ
- Next by Date: Re: Vista RC2: KeSetEvent / WaitForSingleObject problem
- Previous by thread: Whar are invalid characters in a hardware or compatible id?
- Next by thread: Re: Whar are invalid characters in a hardware or compatible id?
- Index(es):
Relevant Pages
|