«

smlunatick wrote:

> Have you considered setting up a scheduled XP "reboot" shortly after
> the wireless adapter disappeared. There are numerous examples of
> scheduling a reboot.

Ah, interesting. I didn't realise you could have something act as a
result of something else. I thought scheduling just mean "at 4am, do
this" or "at x interval, do that".

This is new to me - so, how does it work? Does it watch for an event in
eventvwr, then when it sees "the wireless adaptor has disconnected", it
would then do the "repair" option automatically? Sounds like a solution.

Hmmm, now I think of it, would it be possible to batch up a command that
would ping something every minute, and when the destination was
unreachable, it would do the repair?

All the above still leaves me with the problem that the sequence of
events detailed in repair don't seem to actually disable then re-enable
the wireless adaptor in the same way that acutally clicking "repair" does.

are you saying that any USB adapter you use blue screens and crashes
the system? is this just wireless adapters or other types of
peripherals.

On Thu, 10 Apr 2008 15:42:49 +0100, Jamie Furlong
<> wrote:

>Thanks - yes, I know Prism is no longer, but at least it doesn't bring
>down the whole PC when it disconnects. When any USB adaptor crashes, it
>bluescreens the whole system. So between clicking "repair" and retyping
>a whole document, I know which is less painful. The problem is when it's
>5am and it disconnects...
--

Barb Bowman
MS-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

[honeycrippen12]

Hmm......nice discussion u all have discussed guy........! well u know i have recently bought karaoke wireless microphones by online shopping & really got good response along with good price.


Thanks