I have had a problem with perhaps four different Prism2 wireless cards
where, if another machine joins or leaves the adhoc network, the Prism2 card
wedges and all commands time out; a bit of study suggests that it's
possible the card is expecting to be able to "notify" the OS in some way,
and we're not taking it... but it could be a firmware bug.

Anyone else seen this to confirm or deny?  Most reproducible if the other
machine reboots or power-cycles.

-s