One day, I was writing a sample driver. In the registry file platform.reg, while making entry for my sample driver, by mistake, I used S8M as prefix and it works fine.
I was surprised. Because I referred the link http://msdn.microsoft.com/en-us/library/aa447463.aspx
Which clearly says that "When you implement the stream interface, you designate the three-letter prefix. It can be any three letters, although you should use a common prefix, if your driver is the same class of device as other drivers".
It means it should not support other type of prefix.But it does. Just by seeing at the logic, I think that is correct way as other name like SM8 or 8SM does not work.
I am thinking whether it is wrong or write. But logically I agree this bug or wrong logic is correct but at the same time, MS should clearify in the same in their msdn part too. I think the time has come when people rely on article to resolve their problem. At this time it is must.
I would like everybody to share their reason to support or not support.
I was surprised. Because I referred the link http://msdn.microsoft.com/en-us/library/aa447463.aspx
Which clearly says that "When you implement the stream interface, you designate the three-letter prefix. It can be any three letters, although you should use a common prefix, if your driver is the same class of device as other drivers".
It means it should not support other type of prefix.But it does. Just by seeing at the logic, I think that is correct way as other name like SM8 or 8SM does not work.
I am thinking whether it is wrong or write. But logically I agree this bug or wrong logic is correct but at the same time, MS should clearify in the same in their msdn part too. I think the time has come when people rely on article to resolve their problem. At this time it is must.
I would like everybody to share their reason to support or not support.
No comments:
Post a Comment
Please add your valuable feedback and suggestion...
Note: Only a member of this blog may post a comment.