Notes from H-Master:

For those who have used some of my internet programs before, you may realise
that the interface as well as some parts of the internet connection may be
different from other programs.  You may also wonder why I have finally decided
to code in 32-bit.  The reasons are simple.  Firstly, the internet control I
use for my other internet programs (CSWSKCTL.VBX) is not fast or stable enough
to develop a port scanner with it.  My next alternative would be the Microsoft
ActiveX(tm) Internet Controls.  However, that was in beta and has expired.
Moreover, I have no wish to purchase the entire package.  Another alternative
would be to use DSSOCK32.OCX or DSSOCK16.OCX.  However, both are commercial
softwares and again, I have no wish to spend money on either.  Thus, I decided
to use MSWINSCK.OCX which comes with VB5.  Since MSWINSCK.OCX is 32-bit,
therefore, I have no choice but to code in 32-bit.  Secondly, as Porter is
32-bit while my other internet programs are 16-bit, the code is therefore
vastly different.  I had to change so much code that in the end, I decided to
redo the entire winsock framework, therefore, leaving me with a program that
hardly resembles my other ones, which share a hefty part of their code.

Porter is my first try at coding internet applications in 32-bit.  Therefore,
there are bound to be errors.  Please be tolerant and report the errors to me,
so that I can fix them for future releases of Porter.  You can find
information on contacting me in PORTER.DOC.

One last note, Porter was made with almost no allowances for server lag.  Thus
on slower servers, Porter may not find all the ports/hosts.  This is actually
quite understandable considering that most other port scanners do not find all
the ports/hosts either.  Even though on faster servers Porter may sometimes
find more ports/hosts at a faster rate, Porter may fail miserably on slower
servers.  Thus, it is advisable to run Porter more than once for each scan so
as to find as much ports/hosts as possible.
