From: Maxim S. Shatskih on
> Because it is wrong to ask the user to close an application with penalty of
> entire system not responding.

Serial is an exclusive device by its very design, so, such things are OK.

--
Maxim S. Shatskih
Windows DDK MVP
maxim(a)storagecraft.com
http://www.storagecraft.com

From: Maxim S. Shatskih on
> I *can* imagine asking the user to reboot.
> Users know that Windows likes reboots ;)

There is nothing about the entire system, only about 1 app (or service).

--
Maxim S. Shatskih
Windows DDK MVP
maxim(a)storagecraft.com
http://www.storagecraft.com

From: Asaf Shelly on
>
> I *can* imagine asking the user to reboot.
> Users know that Windows likes reboots ;)
>
> --pa

I have to admit that I just restarted my machine because of the compiler
issue.

If I get a single call asking me to come see why "my driver isn't working",
I'll have to go over the configuration and then the user's code etc. A good
day's work and I can respond. Imagine buying Microsoft webcam and it will
stall because your mobile phone service is also using WinUSB.. Everytime you
have a call your camera will miss frames.

A device designed for handling File Objects is expecting to handle multiple
users otherwise what's the point in FOs?

Asaf
From: Asaf Shelly on

> > Because it is wrong to ask the user to close an application with penalty of
> > entire system not responding.
>
> Serial is an exclusive device by its very design, so, such things are OK.
>

I am allowing general file-system targets including COM, LPT, Pipes, etc.
My user does not care how I implement my 'engine'. Just as you don't care
that IRDA is over a serial port and USB is over PCI...
From: Maxim S. Shatskih on
> A device designed for handling File Objects is expecting to handle multiple
> users

....and serial port is expecting to handle 1 user only.

--
Maxim S. Shatskih
Windows DDK MVP
maxim(a)storagecraft.com
http://www.storagecraft.com