Article View: borland.public.cppbuilder.nativeapi
Article #1445Re: How to find modem com port
From: Bruce Larrabee
Date: Mon, 27 Aug 2007 16:59
Date: Mon, 27 Aug 2007 16:59
13 lines
1262 bytes
1262 bytes
Hello Jyrki ---
Well a 'quick and dirty' solution would be to
poll the com ports, say COM1 - COM4 or COM1 - COM6
or whatever, till you find a functioning modem.
I know it's crude so it may or may not be sufficient
for your app...
HTH,
Bruce
Technical Details
Message-ID:
<46d302e9$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news1.google.com!news.glorb.com!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mailReferences:
<46cb33b4$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 10cc67,829c8cbb24c7d098 X-Google-Attributes: gid10cc67,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Date: Mon, 27 Aug 2007 09:59:05 -0700 From: Bruce Larrabee <bruce_l@westbrookent.com> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: borland.public.cppbuilder.nativeapi Subject: Re: How to find modem com port References: <46cb33b4$1@newsgroups.borland.com> In-Reply-To: <46cb33b4$1@newsgroups.borland.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit NNTP-Posting-Host: 208.100.240.177 Message-ID: <46d302e9$1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1188233961 208.100.240.177 (27 Aug 2007 09:59:21 -0700) Lines: 13 Path: arc1-ca.pugleaf.net!g2news2.google.com!news1.google.com!news.glorb.com!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail