🚀 go-pugleaf

There is no documentation in the Windows help regarding DLLHOST.EXE (at
least none that I can find). Nor does there appear to be any help when I use
/? or -? switches. How is this utility used? I understand that basically we
run this software (somehow) and magically a DLL server appears and its
security may be tweaked. Is there a way to do this programmatically perhaps
so we don't have to tinker with the DLL in any extracurricular sense?


"Dan Miser (TeamB)" <dmiser@wi.rr.com> wrote in message
news:97ndl7$3o710@bornews.inprise.com...
> As I mentioned in my last post to you about this subject, a DLL will not
> show up in DCOMCNFG. This is the way MS designed their software. Try
> searching www.mers.com for "surrogate" for some more information.
Searching
> "surrogate miser" will get you even more targetted information.
>
> I don't know of any bugs in SCKTSRVR that prevent the server from cleaning
> up any resources. If you have explicit steps you want to post, I'll take a
> look.
>
> As for the "Class not registered" error, did you remember to deploy and
> register MIDAS.DLL (via regsvr32)?
> --
> Dan Miser
> http://www.distribucon.com
>
> "mpowell" <mike.powell@transcore.com> wrote in message
> news:97mjpg$fob4@bornews.inprise.com...
> >
> > We are experiencing great difficulty connecting under Windows 2000. Let
me
> > explain what it is we're doing. As stated earlier we are using Windows
> 2000
> > and C++Builder 5 Enterprise.
> >
> > We first tried to build a MIDAS DLL server followed by a MIDAS EXE
server.
> >
> > In the DLL case, we had problems registering properly. After registering
> we
> > could not see the server using DCOM Config. We also cannot seem to
connect
> > to the server using DCOM to another (albeit W2K Professional) machine.
> Using
> > TSocketConnection, while this worked, would not clean up after itself so
> we
> > have decided it will not do in its current bug filled state.
> >
> > In the EXE case we seem to register the server just fine both by running
> the
> > application itself and by using the command line argument /REGSERVER.
The
> > application does appear using DCOM Config. However, all attempts to
> connect
> > either remotely or locally have failed in "class not registered".
>
>
>