How can I find what a DLL does?
#3
http://www.tmpgenc.net/cgi-bin/ebbs/board.cgi and do a search.
"Bug report - The error opening some mpeg a/v files No.8036
mOrg ( Mail ) 2002/06/01 (Sat.) 15:46 ( IP:66.169.88.135 ) [ Edit / Delete / Reply with quotation ]
I don't know if this is the root of everyone's tmpgenc crashes (the common problem with mpeg files), when using windows xp, but I checked to see what was causing the problem and it was a .dll file called mplam6.dll which is part of a Ulead package I had installed.
The file was in C:\Program Files\Common Files\Ulead Systems\Mpeg on my xp machine and after I renamed it to mplam6.dll_ it no longer causes tempgenc to crach.
I hope this helps someone.
mOrg
"
"Bug report - The error opening some mpeg a/v files No.8036
mOrg ( Mail ) 2002/06/01 (Sat.) 15:46 ( IP:66.169.88.135 ) [ Edit / Delete / Reply with quotation ]
I don't know if this is the root of everyone's tmpgenc crashes (the common problem with mpeg files), when using windows xp, but I checked to see what was causing the problem and it was a .dll file called mplam6.dll which is part of a Ulead package I had installed.
The file was in C:\Program Files\Common Files\Ulead Systems\Mpeg on my xp machine and after I renamed it to mplam6.dll_ it no longer causes tempgenc to crach.
I hope this helps someone.
mOrg
"
#5
yeh I did all that, it talks about ulead installing it and I ain't installed that program.
I can rename to get TMPGenc to run, but I'm assuming by renaming it something else that installed it will break, I'm trying to find what that something else is!!
I've also searched the registry with no joy.
cheers,
greg
I can rename to get TMPGenc to run, but I'm assuming by renaming it something else that installed it will break, I'm trying to find what that something else is!!
I've also searched the registry with no joy.
cheers,
greg
#6
OK.
Si is nearly there.
They are just compiled code that exposes various entry points that other applications can call. You can see what those entry points are by using a tool like DumpbinGUI.
If it is a dll that holds one or more COM objects, then the COM object identifiers will be in the registry, otherwise the chances are slimmer that you would see it in the registry. If it is a COM module, it should be obvious from the DumpBin output.
So, click the file in WIndows explorer and right click for properties. Check the version field. That should tell you who wrote the app if they could be bothered to fill in the info. Else, see if the method names from the DumpBin output give you any clues.
EDIT: I think DumpBin will only work if you happen to have the C++ development environment installed. Anyone know of any other PE utils?
[Edited by MrDeference - 7/2/2002 2:10:06 PM]
Si is nearly there.
They are just compiled code that exposes various entry points that other applications can call. You can see what those entry points are by using a tool like DumpbinGUI.
If it is a dll that holds one or more COM objects, then the COM object identifiers will be in the registry, otherwise the chances are slimmer that you would see it in the registry. If it is a COM module, it should be obvious from the DumpBin output.
So, click the file in WIndows explorer and right click for properties. Check the version field. That should tell you who wrote the app if they could be bothered to fill in the info. Else, see if the method names from the DumpBin output give you any clues.
EDIT: I think DumpBin will only work if you happen to have the C++ development environment installed. Anyone know of any other PE utils?
[Edited by MrDeference - 7/2/2002 2:10:06 PM]
Thread
Thread Starter
Forum
Replies
Last Post
Sam Witwicky
Engine Management and ECU Remapping
17
13 November 2015 10:49 AM