Article View: borland.public.cppbuilder.nativeapi
Article #8274Re: Port Scans - unsolved
From: Max Blank
Date: Tue, 09 Nov 2004 15:05
Date: Tue, 09 Nov 2004 15:05
58 lines
2310 bytes
2310 bytes
> So psuedo code is:
> CreateFile
> Set baud rate to 9600
> openPort
> try to find device
> if it fails
> close port
--> CreateFile ??? <----------------
> set baud rate to 19200
> try to find device
> if it fails
> close port
What I do is almost exactly what you suggested, except that I perform a
second CreateFile() as shown above. Actually, the following happens:
Scenario 1:
CreateFile for COM8
Set baud rate to 9600
OpenPort
Try to find device -> fails, as expected
Close Port
CreateFile for COM8 => fails !!!
Scenario 2:
CreateFile for COM8
Set baud rate to 19200
OpenPort
Device Found ...
Close Port
The second CreateFile on the same port seems to fail. However, if I stop
the program's execution shortly, and then continue, everything works
fine like this:
Scenario 3:
CreateFile for COM8
Set baud rate to 9600
OpenPort
Try to find device -> fails, as expected
Close Port
CreateFile for COM8 -> succeeds !!
Set baud rate to 19200
OpenPort
Device Found ...
Close Port
That's annoying !
Max
Technical Details
Message-ID:
<4190dcd2$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!proxad.net!213.200.89.82.MISMATCH!tiscali!newsfeed1.ip.tiscali.net!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<418ebc0d@newsgroups.borland.com> <418f380f@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 10cc67,9fcab49b7cf126f6 X-Google-Attributes: gid10cc67,public X-Google-Language: ENGLISH,ASCII-7-bit Date: Tue, 09 Nov 2004 16:05:55 +0100 From: Max Blank <MaxBlank@MaxBlank-Institute.net> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: borland.public.cppbuilder.nativeapi Subject: Re: Port Scans - unsolved References: <418ebc0d@newsgroups.borland.com> <418f380f@newsgroups.borland.com> In-Reply-To: <418f380f@newsgroups.borland.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit NNTP-Posting-Host: 217.186.45.235 Message-ID: <4190dcd2$1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1100012754 217.186.45.235 (9 Nov 2004 07:05:54 -0700) Lines: 59 Path: arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!proxad.net!213.200.89.82.MISMATCH!tiscali!newsfeed1.ip.tiscali.net!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail