At 19:30 06/11/2002 -0500, Jack wrote: >Ron, > >I'm really not certain how Windows will react, I don't have a Win2000 to try >this with right now. But, if you have such a system it would be easy enough >to try the recommendations that were listed in the help file and try leaving >it set that way with the internal CW feature turned off.
In my case DXB 2003 installed driverX when I first installed. took me ages to find out what had broken suspend/resume (& a few other things ) However under win2k it is real easy to stop driverX and as long as your are not using DXB for CW sending this should not cause problems Do the following Right Click on ' My computer ' and select ' Manage ' Select ' device manager' in the right hand side of the computer management window Left click on view (top menu bar of computer management window) and select ' show hidden devices ' On the right hand side of the ' computer management pane ' (now showing the various devices ) select ' non plug and play drivers ' scroll down and find DriverX Double click DriverX and select the Driver tab * select Stop (Stops the driver for this session) Choose Startup disabled (stops the driver being loaded following next boot ) Close the Computer management window suspend resume should now be working again ( no need for a reboot if you stopped the driver * ) this works fine and means that dirverX can be re-enabled if required. 73 Brendan EI6IZ
