a test for the com1 port

**loninappleton** · 06-20-2009, 07:39 PM

I recently connected a device to the com1 port on the motherboard and it didn't register as installed.

The test I have used previously was to give a dial command using Hyper Terminal from the Windows OS. Hyper Terminal also would not perform a dial out.

Is there a way to confirm that the com1 port or physical hardware is dead?

PoIIux · 06-20-2009, 07:54 PM

What device are you trying to connect to the COM port?

When you use Hyper Terminal, remember to set the correct paramters: Bits per second, Data bits, etc. Safest to set it on Default.

If you still don't get output on hyperterminal, try using this:

http://www.aggsoft.com/com-port-stre...t/download.htm

to test your com port.

If you could check your device on a different COM port, or different PC it would be great.

Also remember to check Device Manager for !, ? or Xs

**loninappleton** · 06-20-2009, 08:36 PM

Quote:

Originally Posted by PoIIux

What device are you trying to connect to the COM port?

When you use Hyper Terminal, remember to set the correct paramters: Bits per second, Data bits, etc. Safest to set it on Default.

The device is an old US Robotics 56k fax modem.

The device was correctly recognized using Hyperterminal on my other machine.

I checked Device Manager and could not find the USR on the faulty machine.

Thanks for the program tip. There was nothing in help on this from the OS.

If you still don't get output on hyperterminal, try using this:

http://www.aggsoft.com/com-port-stre...t/download.htm

to test your com port.

If you could check your device on a different COM port, or different PC it would be great.

Also remember to check Device Manager for !, ? or Xs

PoIIux · 06-20-2009, 09:03 PM

Is the COM1 port on the faulty machine by any chance disabled (under Device Manager, Ports, COM1, Properties).

Are you positive it's actually COM1 and not COM2 or COM3...?

**loninappleton** · 06-20-2009, 10:02 PM

Quote:

Originally Posted by PoIIux

Is the COM1 port on the faulty machine by any chance disabled (under Device Manager, Ports, COM1, Properties).

Are you positive it's actually COM1 and not COM2 or COM3...?

That program you mentioned works fine on my other motherboard. I have yet to install it on the faulty one.

I don't know how anything could get disabled. Will have a look.

**johnwill** · 06-21-2009, 08:46 AM

Try this serial port utility: http://www.download32.com/free-seria...tor-i9378.html

**loninappleton** · 06-22-2009, 12:20 PM

The latest in this is that the program first mentioned up there called
Com Port Stress Test gave a like result on both machines. I should be noted that I had nothing connected to either com1 port.

I recall there was some way to do a loop back with a piece of wire inserted into
two pin sockets on the motherboard DIN but I have not done that nor know how to.

Do not try this at home.

**johnwill** · 06-23-2009, 11:06 AM

Jumper pings 2 & 3 and you have a simple loopback if you configure the COM port for no handshake.

06-20-2009, 07:39 PM	#1 (permalink)
loninappleton TSF Enthusiast Join Date: Apr 2005 Posts: 748 OS: Win2k, XP	a test for the com1 port I recently connected a device to the com1 port on the motherboard and it didn't register as installed. The test I have used previously was to give a dial command using Hyper Terminal from the Windows OS. Hyper Terminal also would not perform a dial out. Is there a way to confirm that the com1 port or physical hardware is dead?

06-20-2009, 07:54 PM	#2 (permalink)
PoIIux Registered User Join Date: Jun 2009 Posts: 27 OS: XP SP3	Re: a test for the com1 port What device are you trying to connect to the COM port? When you use Hyper Terminal, remember to set the correct paramters: Bits per second, Data bits, etc. Safest to set it on Default. If you still don't get output on hyperterminal, try using this: http://www.aggsoft.com/com-port-stre...t/download.htm to test your com port. If you could check your device on a different COM port, or different PC it would be great. Also remember to check Device Manager for !, ? or Xs Last edited by PoIIux; 06-20-2009 at 07:56 PM.

06-20-2009, 09:03 PM	#4 (permalink)
PoIIux Registered User Join Date: Jun 2009 Posts: 27 OS: XP SP3	Re: a test for the com1 port Is the COM1 port on the faulty machine by any chance disabled (under Device Manager, Ports, COM1, Properties). Are you positive it's actually COM1 and not COM2 or COM3...?

06-21-2009, 08:46 AM	#6 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 41,899 OS: Windows 7, XP-Pro, Vista, Linux Blog Entries: 1	Re: a test for the com1 port Try this serial port utility: http://www.download32.com/free-seria...tor-i9378.html __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience

06-22-2009, 12:20 PM	#7 (permalink)
loninappleton TSF Enthusiast Join Date: Apr 2005 Posts: 748 OS: Win2k, XP	Re: a test for the com1 port The latest in this is that the program first mentioned up there called Com Port Stress Test gave a like result on both machines. I should be noted that I had nothing connected to either com1 port. I recall there was some way to do a loop back with a piece of wire inserted into two pin sockets on the motherboard DIN but I have not done that nor know how to. Do not try this at home.

06-23-2009, 11:06 AM	#8 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 41,899 OS: Windows 7, XP-Pro, Vista, Linux Blog Entries: 1	Re: a test for the com1 port Jumper pings 2 & 3 and you have a simple loopback if you configure the COM port for no handshake. __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience