#Usb secure problems serial#
#Usb secure problems driver#
#Usb secure problems software#

If CRT was notified of a surprise remove, what should it do? Going or manually click the disconnect button to terminate the connection Do nothing- let the user either reconnect the com port and keep

Veto the operation (assuming we really can and I'm not misrememberingДЈ. Close the com port and let the operation happen?Дў. What should CRT do when the user attempts to remove the COMДЎ. Remove if it was a safe removal, or, if I recall correctly, veto the When the device is removed (it could close the COM port before If CRT registered for the notification, it could close the COM port Typing, or you could concievably get errors from SCRT if the driverД¬hoose to complete CRT's pending I/O requests w/ errors during Have described, that when you reconnect the device you can keep The behavior you should currently see is either the behavior others Windows does actually provide a way for applications to get notified that device has gone away.Д¬RT doesn't currently register to receive this notification. I have sent email to belkin technical support (as of Friday evening) The SCRT window dissappears correctly, the SCRT process will

#Usb secure problems serial#

In addition, the serial port is locked until a reboot, and while In my testing under Windows XP, this results in a 10 second hang Inter-character timeout correctly, and they don't appear to be In particular, they don't don't handle the I have been testing a Belkin FSU409, and unfortunately, the belkinДrivers are buggy. When you say 'SecureCRT will hang', can you tell me moreДЇor example, after you unplug the device, do SCRT's menu'sДoes the hang happen immediately after you remove the device, I've found that if I unplug the serial adapter while I still have a SecureCRT terminal session open, SecureCRT will hang. I frequently use a Belkin USB to serial adapter to connect to router console ports. My point was just that it is within SecureCRT's abilities to detect that the device is gone and display an appropriate error message, which I'm sure you'll agree is a better response than getting stuck (probably in the windows equivalent of an iowait state) waiting for the device forever.

We already established this much in the first post.

I'd put this in the Don't Do This category.

#Usb secure problems software#

This is why Windows has the Remove Hardware tasktray item - so that software can be gracefully notified of device closure. It is not appopriate to remove hardware when software is still using the device. The fact that it works from some USB-to-Serial devices does not make it supported in general.

#Usb secure problems driver#

The driver should close the instantiation, and this leaves SecureCRT in a pickle - it probably wants to read (or write) more data from the device, but the device is gone. Unplugging the USB cable requires sending a device Close call, since the device is no longer in use. In the USB to serial connection, the mapping is made at the OS driver level to map the USB device to the serial device. So unplugging a cable (although not truely supported by hardware) from an active system is no real problem.Д«ut a USB device when connected to a system has to create and map the device. Serial devices are opened and closed, and by nature, do not just disappear. This is most likely not SecureCRT/CRT's problem.