Re: 16+ comm ports

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Jason Hawryluk (IHATESPAM_at_3gcomm.fr)
Date: 10/19/04 

Date: Tue, 19 Oct 2004 09:40:58 +0200

Just a note:

You can load a ocx or dll file with just the location,key,and classid
therefor you would not have to register the modified one, and it could rest
in the application path to protect other installations. Mathew Curland wrote
a book "Power VB". I use this method for all my cutome ocx's and it works.
You also have the early binding benifit..

Good luck...

Jason

"Duane Bozarth" <dp_bozarth@swko.dot.net> a écrit dans le message de
news:4174503A.74465713@swko.dot.net...
> David Youngblood wrote:
> >
> > "Duane Bozarth" <dp_bozarth@swko.dot.net> wrote in message
> > news:41740478.7AF2DD54@swko.dot.net...
> > > > Be careful as Dolphe pointed out that this may be in violation of
some MS
> > > > EULA
> > >
> > > May be, but it's one I wouldn't worry much about...it's just not the
> > > type of thing that costs MS enough to be worth pursuing. The biggest
> > > potential gotcha I'd see would be the one of getting the modified copy
> > > overwritten sometime on a target system.
> >
> > Or just as bad, overwriting someone elses *unmodified* copy. You can
affect over
> > peoples programs by modifing common files. For personnal use, I couldn't
care
> > less, but these modified files should not be distributed.
>
> Depending on the modification, that's certainly true, but I seriously
> doubt it in this case...
>
> > What's next, someone doesn't like the way the treeview control works, so
they
> > modify it to meet their needs and distrribute it?
>
> Certainly, that's a possibility that would potentially be a problem, but
> not the case here. Depending on the actual modification, I'd be far
> more likely to recommend against such a modification.

Relevant Pages