How do DLL files work ?
22 April 2007, 09:21 AM
#1
Scooby Regular
Thread Starter
Join Date: Oct 2002
Location: ex UK [SE], now Sunshine State [QLD,AUS]
Posts: 565
Likes: 0
Received 1 Like
on
1 Post
How do DLL files work ?
Basically I notice that I have 2 identical DLL files in different directories.
shimgvw.dll - same size, same date.
Would having 2 files instead of 1 cause any conflicts ?
Can I just delete them, or will that corrupt anything ?
How do I find out which application uses them ?
Thx.
shimgvw.dll - same size, same date.
Would having 2 files instead of 1 cause any conflicts ?
Can I just delete them, or will that corrupt anything ?
How do I find out which application uses them ?
Thx.
22 April 2007, 09:48 AM
#3
Scooby Regular
Join Date: Jan 2001
Posts: 9,781
Likes: 0
Received 0 Likes
on
0 Posts
This is the windows picture and fax viewer. It should be in system32. I can't think why it would be anywhere else, except a service pack folder.
Still, it won't do any harm as it's a COM DLL and can only be registered in one place.
Still, it won't do any harm as it's a COM DLL and can only be registered in one place.
22 April 2007, 09:54 AM
#4
Scooby Regular
Thread Starter
Join Date: Oct 2002
Location: ex UK [SE], now Sunshine State [QLD,AUS]
Posts: 565
Likes: 0
Received 1 Like
on
1 Post
they are in.....
c:/windows/system32
c:/windows/servicepackfiles/i386
....but i'm having problems with codec, with 100% cpu usage.
so I might delete them.
c:/windows/system32
c:/windows/servicepackfiles/i386
....but i'm having problems with codec, with 100% cpu usage.
so I might delete them.
22 April 2007, 09:59 AM
#5
Scooby Regular
Join Date: Sep 1999
Location: Swindon, Wiltshire Xbox Gamertag: Gutgouger
Posts: 6,956
Likes: 0
Received 0 Likes
on
0 Posts
Having two isn't unusal, (and I expect they are identical - from the latest servicepack). Only one can be registered...
22 April 2007, 10:33 AM
#6
Scooby Regular
Join Date: Sep 2001
Location: A powerslide near you
Posts: 10,261
Likes: 0
Received 0 Likes
on
0 Posts
Check which is registered. Unregister it (backup registry, keep copies of dll files to re-register if it ***** something up too).
However, I agree with Iain above, I suspect the codec is where the problem lies, not the dlls. Or maybe a later version of the DLL is available?
However, I agree with Iain above, I suspect the codec is where the problem lies, not the dlls. Or maybe a later version of the DLL is available?
Thread
Thread Starter
Forum
Replies
Last Post