Article View: borland.public.cppbuilder.nativeapi
Article #538Re: Detecting virtual comports
From: Anton
Date: Mon, 28 Jan 2008 22:08
Date: Mon, 28 Jan 2008 22:08
58 lines
2817 bytes
2817 bytes
Thank you all for your tips. I discovered the problem is caused by the software. I've downloaded other software and the serial ports are detected immediately even when I unplug the dongle. But that's just a solution for me, cause in fact I make the program for other, unknown people and when they don't use the correct software they may have the same problems and blame it to my program. So the idea to start a thread to detect the comm-ports does not seem so bad to me. I'll think about it. Thanks and regards, Anton "Oliver Rutsch" <orutsch@sympatec.com> schreef in bericht news:479d85db$1@newsgroups.borland.com... > Hi Anton, > >> >> I installed a bluetooth dongle and became 9 serial blue tooth ports, some >> are only for reading, others just for writing. >> I'm not quite sure how everyhing works, the menuitmes are in Chinese and >> that's a little diificult for me. >> >> But in contrast with a 'normal' usb to serial plug, those ports dont's >> disappear after the dongle is unplugged >> They are visible in the hardware-view and in the windows register. >> >> So the software thinks the ports are present, tries to open them and >> maybe that's the reason it takes such a long time. >> > > I also have a COM-port detecting function and I discovered this kind of > problem on some Laptops with virtual Bluetooth ports. I know that nobody > wants to disable these virtual ports just to start our software. > So the only way to solve this was to start a own thread for every port and > to kill the thread (the hard way) if it took too long to respond. > Not very nice but it works reliable. > > Bye, > > -- > Dipl. Ing. Oliver Rutsch > EMail: orutsch@sympatec.com > Sympatec GmbH
Technical Details
Message-ID:
<479e5273@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news.glorb.com!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mailReferences:
<4799cc68$1@newsgroups.borland.com> <njkjp3d5feaailo8p568elmqhntg8br1ku@4ax.com> <4799e374$1@newsgroups.borland.com> <vegkp3hhb89k52eol1c49492gc46k3iedv@4ax.com> <479b0c39@newsgroups.borland.com> <479d85db$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 10cc67,1645444b8ff69f0e X-Google-Attributes: gid10cc67,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit From: "Anton" <acvoosten@zeelandnet.nl> Newsgroups: borland.public.cppbuilder.nativeapi References: <4799cc68$1@newsgroups.borland.com> <njkjp3d5feaailo8p568elmqhntg8br1ku@4ax.com> <4799e374$1@newsgroups.borland.com> <vegkp3hhb89k52eol1c49492gc46k3iedv@4ax.com> <479b0c39@newsgroups.borland.com> <479d85db$1@newsgroups.borland.com> Subject: Re: Detecting virtual comports Date: Mon, 28 Jan 2008 23:08:56 +0100 Lines: 60 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-RFC2646: Format=Flowed; Response NNTP-Posting-Host: 86.87.46.231 Message-ID: <479e5273@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1201558131 86.87.46.231 (28 Jan 2008 14:08:51 -0700) Path: arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news.glorb.com!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail