"ShadowTek" <FAKE@EMAIL.ADDRESS> wrote in message
news:Xns9B0EE75761psistormyamatocscom@85.214.90.23 6...
> "V Green" <vanceg@nowhere.net> wrote in
> news:#qaajN5CJHA.4340@TK2MSFTNGP02.phx.gbl:
>
> > I believe that I have seen code to disable/enable devices
> > that show up in Device Manager. If disabling/enabling
> > the port/cable revives the device then you could go this
> > route rather than rebooting the entire system. Try Google.
> >
> > Also, it isn't necessary to ping things to find out whether
> > or not the modem has hung. Simply issuing an AT command
> > and looking for the OK response (after enabling verbose mode,
> > etc.) will keep things local. No OK, no comm.
> >
> > For testing purposes, you can probably initiate a "hung"
> > state by disconnecting the RJ-45 cable from the modem while
> > it's in use. Or by pulling the USB cable from the computer
> > while off-hook.
> >
> > If that works, you have all the necessary tools to write your
> > own custom solution, which it sounds like you will need to
> > do, given the description of your situation.
>
> It happened again. I tried disabling the modem, but there was no change. I
> also tried disabling the serial to USB adapter, but that also did nothing.
> And, once again, I could not soft reboot, so I can't figure out any other
> way to automatically deal with the problem.

Time for different / newer hardware, sounds like.