Prev: American E-commerce Increasingly Outside the Legal Positions
Next: How to get device key (hardware key) path in kernel mode ?
From: Pavel A. on 30 Aug 2010 19:07
This problem most likely has a reasonable solution, but unfortunately you're
looking in a wrong place.
The serial port driver won't change, WDF design won't change.
Playing word games - FO or not FO - won't help.
The reasonabe solution is balanced somewhere in the middle, between user's
ideal and what you are ready to provide.
--pa


"Asaf Shelly" <MSMediaForum(a)Shelly.co.il> wrote in message
news:C56AEEAB-8600-4263-8279-86EDA44C5667(a)microsoft.com...
> Serial solved this by allow only one device access at a time, even though
> (if
> I remember correctly) it will allow a write operation while read is still
> blocking.
>
> Asaf
>
>
> "Maxim S. Shatskih" wrote:
>
>> > The problem I am seeing today is more of a design concept problem. I
>> > don't
>> > see a reason why a single application could make my driver not respond
>> > to any
>> > other application.
>>
>> So what? just kill the app and go on.
>>
>> OS-provided serial.sys has no such protection.
>>
>> --
>> Maxim S. Shatskih
>> Windows DDK MVP
>> maxim(a)storagecraft.com
>> http://www.storagecraft.com
>>
>> .
>>
First  |  Prev  | 
Pages: 1 2 3 4 5 6 7 8 9 10
Prev: American E-commerce Increasingly Outside the Legal Positions
Next: How to get device key (hardware key) path in kernel mode ?