Re: 16+ comm ports

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: GrandPa (garbage_at_bin.com)
Date: 10/18/04 

Date: Mon, 18 Oct 2004 17:22:44 +0200

Dear Chris Hanscom
I guess that *** Greer told me that altering the MSCOMM control by hacking
the code made me a criminal. I posted the answer to increase the number of
ports. Thanks for the repost, that makes you a criminal delinquent
too.............., join the crowd.
However if you want to increase the number of ports to 256, change the
number to FF. The reason for the 'hack' is to assign a port number 100 to a
COM port over LAN.
Greetings, Dolphe.

"Veign" <NOSPAMinveign@veign.com> schreef in bericht
news:em4hDOStEHA.3320@TK2MSFTNGP15.phx.gbl...
> MSComm control will only address 16 com ports...There are 3rd party
> controls
> that will get by this restriction.
>
> This is a hack work around in the MSComm control that was posted sometime
> ago. There are problems that could arise from this, like having your
> custom
> component overwritten by someone else's install.
> <hack>
> In the code there is a unique sequence of three bytes, 3d 10 00. Pick a
> hex
> editor and change the value 10 to say 7f. Now you have changed the default
> value of a variable MAX_PORTS to 127. The name of the variable is
> arbitrary.
> Save the changed file and off you go.
> Am I a bad boy now, a criminal code offender? Did a lot of assembly code
> programming and still do at my age of 67. Debugging at assembly level is
> one of the key advantages to get rid of the tremendous overhead in MS
> compilers.
> </hack>
>
> --
> Chris Hanscom - Microsoft MVP (VB)
> http://www.veign.com
> --
>
> "matt a" <matta@discussions.microsoft.com> wrote in message
> news:1EA2893F-5604-4CE7-B06C-C670462BA506@microsoft.com...
>> Duane,
>>
>> Thanks for the reply. We are using a USB to RS232 box that has no such
>> driver. I have indeed used the Black Box kit and we had the same
> restriction.
>>
>> Anyways, Hope *** G see's this post and can help. I will search for the
>> other post in the mean time.
>>
>> matt A
>>
>> "Duane Bozarth" wrote:
>>
>> > matt a wrote:
>> > >
>> > > Morning all,
>> > >
>> > > VB6, sp5 enterprise edition
>> > >
>> > > So, I have a perfectly good working app driving multiple comm ports,
> 12 to
>> > > be precise. There is a requirements to add 20 further devices (1 comm
> port
>> > > each). All of a sudden my app fails above port 16. This suggests to
> me that
>> > > I cannot use more than 16 Comm ports using the standard mscom
> control?? is
>> > > there a workround or am I going to have to use the win32 API? Hope
> not, crap
>> > > at API stuff.
>> >
>> > *** Grier will probably add the definitive response, but seems as
>> > though this question was posed in a slightly different form on this or
>> > another ng just recently where someone had patched the MS control to
>> > allow more ports...a search might find that posting.
>> >
>> > In the moderately distant past I used an addon board for 32 ports which
>> > came with a card-specific VB driver that worked well. Methinks that
>> > was
>> > a Black Box component.
>> >
>
>

Quantcast