MXjack.dll implanted

[Metspitzer]

I am using a P2P program called Winmx. It has an add on program
called Mxmonitor. When I launch Mxmonitor, it has a log that shows
"MXjack.dll implanted" I have yet to work out why Mxmonitor quits
working, but I suspect if I could implant Mxjack.dll it might start
working again.

Would you just click on mxjack.dll again to launch it?

 

[Paul]

I am using a P2P program called Winmx. It has an add on program
called Mxmonitor. When I launch Mxmonitor, it has a log that shows
"MXjack.dll implanted" I have yet to work out why Mxmonitor quits
working, but I suspect if I could implant Mxjack.dll it might start
working again.

Would you just click on mxjack.dll again to launch it?

I expect a few of the suggestions here, violate good
security practices. Still...

http://forum.winmxworld.com/index.php?topic=5769.0

*******

The system utility regsvr32 is used for registering DLLs.
But my guess is, the program has been doing this for itself.
At least, unless some security improvement in WinXP, is
stopping the program from working properly. In which case,
the developer should issue a patch.

http://www.microsoft.com/resources/.../xp/all/proddocs/en-us/regsvr32.mspx?mfr=true

I don't really understand the "registering thing" and what it
is for. It could be for allowing a DLL to run as part of
the system, rather than just as a part of an application.

One of the links off this page, mentions registering "COM DLLs",
so maybe it's a particular flavor of DLL that needs registration ?

http://en.wikipedia.org/wiki/Regsvr32

http://en.wikipedia.org/wiki/Component_Object_Model

"COM programmers build their software using COM-aware
components. Different component types are identified by
class IDs (CLSIDs), which are Globally Unique
Identifiers (GUIDs)."

That could be what regsvr32 sets up (writes a registry key),
but without an explanation in plain English, I guess we'll
never know.

Paul

 

[Metspitzer]

I expect a few of the suggestions here, violate good
security practices. Still...

http://forum.winmxworld.com/index.php?topic=5769.0

*******

The system utility regsvr32 is used for registering DLLs.
But my guess is, the program has been doing this for itself.
At least, unless some security improvement in WinXP, is
stopping the program from working properly. In which case,
the developer should issue a patch.

http://www.microsoft.com/resources/.../xp/all/proddocs/en-us/regsvr32.mspx?mfr=true

I don't really understand the "registering thing" and what it
is for. It could be for allowing a DLL to run as part of
the system, rather than just as a part of an application.

One of the links off this page, mentions registering "COM DLLs",
so maybe it's a particular flavor of DLL that needs registration ?

http://en.wikipedia.org/wiki/Regsvr32

http://en.wikipedia.org/wiki/Component_Object_Model

"COM programmers build their software using COM-aware
components. Different component types are identified by
class IDs (CLSIDs), which are Globally Unique
Identifiers (GUIDs)."

That could be what regsvr32 sets up (writes a registry key),
but without an explanation in plain English, I guess we'll
never know.

Paul

If I reboot the computer and load the two programs fresh, It works for
a very short time, then quits. There has been a time in recent
history that clearing and changing the log settings gets it going
again for a while.

Maybe I need to stand on one leg and spin counterclockwise. That
seems to work as good as anything.