"Arny Krueger" wrote in message
...
"Robert Morein" wrote in message

"Arny Krueger" wrote in message
...
"Robert Morein" wrote in message

"Greg Pasquariello" wrote in
message
. ..


"Robert Morein" wrote in message
:

"Arny Krueger" wrote in message
...

"Robert Morein" wrote in
message

You do understand that when a machine hibernates, it
pretty well breaks all connections with outside I/O
devices, right?

You do understand that this depends upon how the
driver is written, right?

You do understand that this doesn't invalidate the
general truth of the previous statement, right?

You do understand it's not generally true, don't you? --
that it depends on the specific driver interface? You
do understand this, don't you?

Morein, three people (and its not like Sander and I
agree about much!) and a relevant Microsoft document say
otherwise. I know that its against your religion to
admit that you're wrong, but you should really give it
up!

True, but utterly irrelevant to the question.

Not at all. Morein, you made them relevent with your OP and your ongoing
debating-trade inspired complexifying of the situation.

When a
computer restores from hibernation, all standard USB HID
devices work: keyboard and mouse.

True, but this happens for a complex series of reasons. One reason why
this works is because the entities that you control with the keyboard and
mouse are designed to be restartable. If this is a laptop both the
keyboard and mouse are hot-pluggable. The ability to be hot-plugged
extends all the way back into the bowels of the computer. A hot-pluggable
interface does not necessarily make a hot-pluggable function. A
hot-pluggable interface is a necessary, but not a sufficient condition.

So does an external USB drive.

That actually depends on the software that is accessing the USB drive. If
you unplug a USB hard drive while a program is writing to it, the results
can be pretty catastrophic to that program. Or not.

Obviously, there are some devices that work, and
some that don't.

I think the real problem is Morien that you don't understand all of the
things that must be lined up in a row for things to work as you wish.

You finally got around to admitting that you're reading this keyboard with
Cubase. Where is it written in stone that Cubase is written to be totally
interuptable and capable of fully supporting hot-pluggable I/O gear?

That is not an answer, Arny. You don't know the answer.

Some respondents on this thread have asserted "Generally___". This is not
new information; it
is not responsive to the question.

Wrong again Morein. An intelligent person would see that Graham is helping
you to exclude possible causes.

Wrong again. However, I credit Graham with good intent. Obviously, there is
an answer: driver vs. app vs. Windows behavior. No one here appears to know.
There is nothing wrong about not knowing. Now stop this nonsense, because
you're adding nothing.