Naming the serial com port Com1,Com2,...Com4, \\.\Com5, \\.\Com6,..

Article View: borland.public.cppbuilder.nativeapi

Article #9523

Back to borland.public.cppbuilder.nativeapi Previous Next

#9523

From: Cahgerti Ghaviery
Date: Wed, 07 Jul 2004 10:49

5 lines
1057 bytes

I was working on a simple rs232 communication program and learned an
expensive lesson (spending long time to realize) that COM ports after COM4
should be defined as \\.\COM5, \\.\COM6 ... instead of COM5 COM6.

Can some one comment about this issue ?

Technical Details

Message-ID: <40ebd523@newsgroups.borland.com>

Path:

arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!logbridge.uoregon.edu!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail

Show Full Headers

Complete Article Headers

X-Google-Thread: 10cc67,8b20be73baf79a0d,start
X-Google-Attributes: gid10cc67,public
X-Google-Language: ENGLISH,ASCII-7-bit
From: <Cahgerti  Ghaviery>
Newsgroups: borland.public.cppbuilder.nativeapi
Subject: Naming the serial com port Com1,Com2,...Com4, \\.\Com5, \\.\Com6,..
Date: Wed, 7 Jul 2004 20:49:06 +1000
Lines: 7
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
NNTP-Posting-Host: 211.30.68.31
Message-ID: <40ebd523@newsgroups.borland.com>
X-Trace: newsgroups.borland.com 1089197347 211.30.68.31 (7 Jul 2004 03:49:07 -0700)
Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!logbridge.uoregon.edu!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail