Open Serial Port Problem [4]

The newest version of Xshell on open port fail now looks like the following ,

Connecting to COM8...
Failed to open COM8.
Xshell:\> Xshell:\> open

Connecting to COM8...
Failed to open COM8.
Xshell:\> Xshell:\> open

Connecting to COM8...
Failed to open COM8.
Xshell:\> Xshell:\>

And there 's some problem on connect to COMx while Putty can while I open a connection to a modem(a gprs modem with standard AT command support ) with the same com port param. XShell session hung after type 1 charactor (I tried to type AT to shake hand with the modem )but Putty works fine.

Bambo, thank you very much for your feedbacks.

We have tested Xshell with Agere Systems AC97 Modem and could not duplicate the problem. Meaning, we could connect to VT services using the COM4 port with standard AT commands.

Also, we have notice that Xshell fails to connect to the COMx ports that are already in use. But, this is a normal operation unless you have set the connection as open.

Could you send us how we can duplicate these problems to support@netsarang.com? We will handle your request with priority.


---
Technical Support

I tested Xshell 3.0 beta to connect to a build-in modem of my laptop at COM3 , and it work well.

Becouse my laptop dosn't have a external serial port, I used a usb to serial switcher to create a serial port.

The attached pictures showed the detail of the usb to serial device.

Xshell 3 still can't work on this serial port (COM8).

I test putty and Xshell 2(build 1512), they both work fine. And I wrote a little code to test the serial port and it work well.

The attachs are the informations of my USB-SERIAL device and the hung status.

If you want more information, ask me :>

And the modem is a GPRS modem looks like a WAVECOM Q2303(2C2) GSM Modem

The detail of the modem is here :
http://www.smssys.net/Pro_Q2303A.asp

The previous post showed the detail on how I meet this problem.

Like always, thank you for your report.

We are working on this issue right now, but it may take awhile to fix this problem.

We will post an update as soon.


---
Technical Support