Home > Archive > Visual Basic > April 2006 > MSCOMM , how many Com ports will it support?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
MSCOMM , how many Com ports will it support?
|
|
| Mike Scirocco 2006-04-22, 6:56 pm |
| I'm using the MSCOMM on a serial port. I was just told that MSCOMM will
only support up to 8 Com ports. Is this correct? So far I haven't been
able to find anything about this in the help file or with Google.
TIA,
Mike
| |
| J French 2006-04-25, 6:57 pm |
| On Sat, 22 Apr 2006 16:30:20 -0700, Mike Scirocco <mscir@yahoo.com>
wrote:
>I'm using the MSCOMM on a serial port. I was just told that MSCOMM will
>only support up to 8 Com ports. Is this correct? So far I haven't been
>able to find anything about this in the help file or with Google.
There is a known hack
Do a Google Groups search for :
VB MSCOMM CONTROL PATCH PORTS
The thread you want is titled : 16+ comm ports
16+ comm ports
.... MS EULA -- Chris Hanscom - Microsoft MVP (VB) http://www ...
Microsoft would consider
a Free patch to allow ... Thanks all, matt A MSComm control will only
address 16 ...
microsoft.public.vb.controls - Oct 18 2004, 8:23 pm by Veign
I would also recommend hacking the GUID and the internal name of the
control.
| |
| Mike Scirocco 2006-04-25, 6:57 pm |
| J French wrote:
> On Sat, 22 Apr 2006 16:30:20 -0700, Mike Scirocco <mscir@yahoo.com>
> wrote:
>
>
>
>
> There is a known hack
> Do a Google Groups search for :
> VB MSCOMM CONTROL PATCH PORTS
> The thread you want is titled : 16+ comm ports
> 16+ comm ports
> ... MS EULA -- Chris Hanscom - Microsoft MVP (VB) http://www ...
> Microsoft would consider
> a Free patch to allow ... Thanks all, matt A MSComm control will only
> address 16 ...
> microsoft.public.vb.controls - Oct 18 2004, 8:23 pm by Veign
>
> I would also recommend hacking the GUID and the internal name of the
> control.
I'm interested in using your suggestion to hack the GUID and internal
name, I'm guessing this is to make the control unique so there won't be
conflicts between the hacked version and unhacked versions?
Would you recommend how I would go about hacking these two items, and
maybe even suggest values? I don't have any experience modifying these
types of files.
Thank You,
Mike Scirocco
| |
| J French 2006-04-25, 6:57 pm |
| On Sun, 23 Apr 2006 08:53:14 -0700, Mike Scirocco <mscir@yahoo.com>
wrote:
<snip>
>
>I'm interested in using your suggestion to hack the GUID and internal
>name, I'm guessing this is to make the control unique so there won't be
>conflicts between the hacked version and unhacked versions?
>
>Would you recommend how I would go about hacking these two items, and
>maybe even suggest values? I don't have any experience modifying these
>types of files.
Not right now - I'm a few sheets to the wind
- but it should be pretty easy
| |
| Mike Scirocco 2006-04-25, 6:57 pm |
| J French wrote:
> On Sun, 23 Apr 2006 08:53:14 -0700, Mike Scirocco <mscir@yahoo.com>
> wrote:
> <snip>
>
>
>
> Not right now - I'm a few sheets to the wind
>
> - but it should be pretty easy
Hahaha, well if you feel like doing it later I'd appreciate hearing
anything you'd suggest.
Also, would it be possible to use the control without doing a windows
installation of it, if I placed it in the same folder as the exe?
Thanks,
Mike
| |
| J French 2006-04-25, 6:57 pm |
| On Sun, 23 Apr 2006 10:33:49 -0700, Mike Scirocco <mscir@yahoo.com>
wrote:
>J French wrote:
>
[color=darkred]
[color=darkred]
[color=darkred]
>Hahaha, well if you feel like doing it later I'd appreciate hearing
>anything you'd suggest.
>Also, would it be possible to use the control without doing a windows
>installation of it, if I placed it in the same folder as the exe?
Not normally
It would need to be registered for normal usage
- although I know of a re-linker that bundles OCXes into the EXE so
that they don't need registering
Hmm... there is a guy here called Olaf Schmidt who has a method of
using OCXes without registering them
| |
|
| J French wrote:
> On Sun, 23 Apr 2006 10:33:49 -0700, Mike Scirocco <mscir@yahoo.com>
> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Not normally
>
> It would need to be registered for normal usage
> - although I know of a re-linker that bundles OCXes into the EXE so
> that they don't need registering
>
> Hmm... there is a guy here called Olaf Schmidt who has a method of
> using OCXes without registering them
If I change the filename, GUID and internal name I guess there's no need
for that anyway. I was thinking of changing the filename to Comm_127 and
modifying it to handle 127 ports. If I can figure out how to change the
GUID to something unique, and change the internal name to Comm_127 then
I don't see any problem registering it since it shouldn't conflict with
the standard MSCOMM control at all.
Thanks,
Mike
| |
|
|
| J French 2006-04-25, 6:57 pm |
| On Mon, 24 Apr 2006 01:14:03 -0700, mscir <mscir@yahoo.com> wrote:
<snip>
>If I change the filename, GUID and internal name I guess there's no need
>for that anyway. I was thinking of changing the filename to Comm_127 and
>modifying it to handle 127 ports.
The actual file name does not matter much
- it is the internal file name that needs jiggering
(that should be pretty easy)
I would go the whole hog and make it handle 255
>If I can figure out how to change the
>GUID to something unique, and change the internal name to Comm_127 then
>I don't see any problem registering it since it shouldn't conflict with
>the standard MSCOMM control at all.
You've got it ! I've sent you an Email.
| |
| J French 2006-04-25, 6:57 pm |
| On Mon, 24 Apr 2006 01:52:15 -0700, mscir <mscir@yahoo.com> wrote:
>mscir wrote:
>
>I found VB code to create a unique GUID. How do I use this? Is it stored
> in the control?
>http://www.codeproject.com/useritem...436#xx1286436xx
Not very impressive code - actually a dog pile
- Gawd - that idiot does not know about Mid$() and Remove
Yes - it is stored in the OCX - 16 bytes of supposedly unique garbage
Ideally one would find a way of fishing it out programatically
But it turns up in the VBP file looking like this :-
Object={648A5603-2C6E-101B-82B6-000000000014}#1.1#0; MSCOMM32.OCX
32 bytes of hex within the { } brackets
I've not looked into this stuff much (as I despise it) but it should
be pretty easy to figure out
| |
| Mike Scirocco 2006-04-25, 6:57 pm |
| J French wrote:
> On Mon, 24 Apr 2006 01:52:15 -0700, mscir <mscir@yahoo.com> wrote:
<snip>
> But it turns up in the VBP file looking like this :-
> {648A5603-2C6E-101B-82B6-000000000014}
Nice trick that!
| |
|
| Here goes:
First you copy the file MSCOMM32.OCX to a safe place.
1. Obtain a HEX editor.
2. Open de file MSCOMM32.OCX
3. Find the string "3D 10 00"
4. There should be only one. This string is unique.
5. Change the string to "3D FF 00"
6. Save the file.
That's it. Works in XP.
Greetings,
Opa.
"Mike Scirocco" <mscir@yahoo.com> schreef in bericht
news:D8-dnVDNLZhsP9bZRVn-vA@pghconnect.com...
>J French wrote:
>
>
> I'm interested in using your suggestion to hack the GUID and internal
> name, I'm guessing this is to make the control unique so there won't be
> conflicts between the hacked version and unhacked versions?
>
> Would you recommend how I would go about hacking these two items, and
> maybe even suggest values? I don't have any experience modifying these
> types of files.
>
> Thank You,
> Mike Scirocco
>
| |
|
| I forgot to mention that the modification (illegal) is good for FF (Hex)
ports.
Opa.
"Opa" <garbage@bin.com> schreef in bericht
news:444dc96d$0$32790$dbd43001@news.euronet.nl...
> Here goes:
> First you copy the file MSCOMM32.OCX to a safe place.
>
> 1. Obtain a HEX editor.
> 2. Open de file MSCOMM32.OCX
> 3. Find the string "3D 10 00"
> 4. There should be only one. This string is unique.
> 5. Change the string to "3D FF 00"
> 6. Save the file.
>
> That's it. Works in XP.
> Greetings,
> Opa.
>
>
> "Mike Scirocco" <mscir@yahoo.com> schreef in bericht
> news:D8-dnVDNLZhsP9bZRVn-vA@pghconnect.com...
>
>
| |
| barry hu 2006-04-25, 6:57 pm |
|
hi gentlemen, the information posted here are pretty helpful for me, i
just simply confirm, does it mean after do the changes for "3D FF 00",
without doing other that, the mscomm is able to support 256 ports?,
thanks
*** Sent via Developersdex http://www.developersdex.com ***
| |
|
| Yep.
Opa
"barry hu" <barryhu.2000@gmail.com> schreef in bericht
news:ehjYbXEaGHA.4784@TK2MSFTNGP02.phx.gbl...
>
>
> hi gentlemen, the information posted here are pretty helpful for me, i
> just simply confirm, does it mean after do the changes for "3D FF 00",
> without doing other that, the mscomm is able to support 256 ports?,
> thanks
>
> *** Sent via Developersdex http://www.developersdex.com ***
| |
|
|
|
|
|