Re: Why wont this work ?

On Wed, 08 Mar 2006 21:58:53 GMT, "Martin Spencer-Ford"
<tpwukdashzeroone@xxxxxxxxxxxx> wrote:


"J French" <erewhon@xxxxxxxxxx> wrote in message
news:440ed641.624401702@xxxxxxxxxxxxxxxxxxxxxxx
On Wed, 08 Mar 2006 09:12:09 GMT, "Martin Spencer-Ford"
<tpwukdashzeroone@xxxxxxxxxxxx> wrote:

<snip>

BHO = Browser Helper Object, marvelous idea, but now heavily abused.

Are you writing some sort of 'system cleaner' ?

Yeap, more of a personal tool than a commercial offering, all of the other
BHO tools i have found just dont seem to offer very much information, they
just say things like "BHO - path\to\the\suspect.dll" - so my effort
reveals
more about the dll, and hopefully will try and reveal what functions the
dll
uses/provides.

I think it is fairly safe to say that Maarten and myself do not like
helping unredeemable idiots,

Charming!

Apologies - I was having a bad day

Mostly, for my part, I attempt to show a viable solution

The only solution offered was by Rob Kennedy, Maarten jumped in on the
thread with the order of presidence when using shellexecute without giving
the action to be carried out. Your solution was to offer calling loadlibrary
and then using the DllRegisterService directly which according to delphi is
a no no, and Rob then says that is correct and that I should use either the
Delphi IDE or RegSvr32 which brings us back in a full circle ....

Delphi is simply 'wrong' about a number of things.
If you look up its advice on INI files and the use of native Filing
such as FileOpen() you'll see what I mean.
Then for a laugh, drill into the code for THandleStream
- it is quite an eye opener

RegSvr32 is just a wrapper, you wanted some feedback from it, and I
told you the established method
- it is a sneaky trick used by VB programmers
- VBers tend to be rather good at using APIs

Unless sarcasm is required

Sarcasm is not required, just as insults are not needed either,

I agree - yet again, apologies

just because
somebody does not understand a programming language at a level that you do,
does not make that person an idiot,

True, we all have to learn
- but I seriously recommend that you pay careful attention to what
people say
- just because the Help Files say something, it does not invalidate
something that is a fundamental part of the design of AX in Windows,
and has nothing to do with Delphi

after all I wasn't the one who needed to
look-up what a BHO was, just settle for the fact that other people have
different talents from that you possess and that I possess, and that we are
not all the same and we all have to start somewhere, if you can't adjust to
that mentality, then I would suggest you shouldn't offer help on Usenet

Put it like this, you asked a question, I gave you a solution that I
/know/ is correct for AX OCXes and DLLs
- I also did a bit of checking to see at what stage an OCX or AX DLL
is 'locked' and therefore unmoveable or deleteable.

You came back saying that I was wrong
- Maarten told you not to believe everything that you read in the Help
files

Incidentally AX EXEs should be self registering on run, I've just done
a test and it looks as if DllRegisterServer does not work on EXEs
- I got a spectacular AV

Admittedly, I should not fly off the handle, but it is pretty annoying
being told that my information is wrong.

As you get more into Delphi, and Windows, you'll find that quite a lot
of things are misleading and it is wise to check multiple sources of
information.

Also, rather than using ShellExecute you might get some joy from
CreateProcess and checking the Exit Code of the Process
- it is possible that RegSvr32 returns something
- failing that, if your plug-ins are EXEs, then try running them
manually with /register and /Unregister in the Command line, then do
the same checking the Exit Code

You could also glean extra information doing the same with RegMon
installed

I've not looked into Browser Plugins, but I expect that they offer a
standard interface, well, they would have to, so you might get quite a
lot of information from that.

You also might get a clue what is installing the blighters using
FileMon

Frankly, if you are trying to control malware, then I think you have
quite a task on your hands - people who write it tend to be quite
sneaky.


.

Relevant Pages

  • Re: Why wont this work ?
    ... Yeap, more of a personal tool than a commercial offering, all of the other ... BHO tools i have found just dont seem to offer very much information, ... more about the dll, and hopefully will try and reveal what functions the dll ...
    (alt.comp.lang.borland-delphi)
  • Re: Using VB6 dll in Delphi app.
    ... to make a *windows standard* .dll with VB6. ... The trouble occurs when we try to use it in a Delphi app. ...
    (microsoft.public.vb.general.discussion)
  • Re: New Delphi roadmap is coming: NO UNICODE PLEASE!
    ... Avoids DLL hell, because it ... The app is deployed and the user is getting an error. ... instances where upgrading .NET broke things that were working. ... Coming from Delphi, this isn't any big deal of course. ...
    (borland.public.delphi.non-technical)
  • Re: DLL with string params callable via D4 and VB
    ... > I have a DLL written in D6 that uses ShortStrings as parameters. ... I can't get beyond Delphi to ... > Is there any guidance you could give in regards to passing string ... written in order to be used by EXCEL 97 VBA. ...
    (borland.public.delphi.language.objectpascal)
  • Re: Use of delegate
    ... Delphi application which I wrote. ... VB.NET relies on that Chainlink DLL, ... > Peter Huang ... > Private Sub Button2_Click(ByVal sender As System.Object, ...
    (microsoft.public.dotnet.languages.vb)