I recently had the occasion to run a program to detect duplicated JPEGS that I had on my PC. I have rerun this duplicate file finder program on all sorts of files since & find some duplicated in several categories. When it comes to DLL file there are more from Ulead products than everything else put together.
For instance the file OLEAUT32.DLL is found at the following locations each file is said to be to be 528288 bytes
C :\Program Files\Ulead Systems\Ulead DVD MovieFactory 4.0\Ulead DMF Launcher 2.0\
C:\Program Files\Ulead Systems\Ulead DVD MovieFactory 4.0\Ulead DVD DiskRecorder 2.1\
C:\Program Files\Ulead Systems\Ulead DVD MovieFactory 4.0\Ulead DVD MovieFactory 4.0\
That example only has 3 files listed while others have many more listed.
Do I really need all of these cluttering up my machine? Can I safely delete them?
Are These Ulead DLL file all really duplicat & do I need
-
htchien
- Advisor
- Posts: 2013
- Joined: Sat Dec 11, 2004 12:10 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- Location: Taipei, Taiwan
- Contact:
Yes, you need them to be placed in those folders to keep the programs working.
No you should not delete them.
Best regards,
H.T.
No you should not delete them.
Best regards,
H.T.
Ted (H.T.)
[color=red]The message is provided AS IS with no warranties and confers no rights. For official tech support please contact Corel Tech Support.[/color]
[url=http://www.youtube.com/htchien]My YouTube channel[/url]
[color=red]The message is provided AS IS with no warranties and confers no rights. For official tech support please contact Corel Tech Support.[/color]
[url=http://www.youtube.com/htchien]My YouTube channel[/url]
-
J_fike
As H.T. stated, don't delete them. If a program installs a dll in it's own directory path, it is used, and needs to be there.
That said, some applications use system dll's that will usually be found (in a windows PC) in a windows OS path. That's fine, if the dll doesn't change or, if it does, remains compatible. But if the owner of the dll changes it and it becomes non-compatible, then that's the applications problem.
With the low price of storage (hard drives) it usually doesn't pay to worry about deleting identical dll's. Also, you can't depend on the file size to absolutely determine that the files are identical. A good checksm program can do that, but I don't think the hassle is worth the effort.
That said, some applications use system dll's that will usually be found (in a windows PC) in a windows OS path. That's fine, if the dll doesn't change or, if it does, remains compatible. But if the owner of the dll changes it and it becomes non-compatible, then that's the applications problem.
With the low price of storage (hard drives) it usually doesn't pay to worry about deleting identical dll's. Also, you can't depend on the file size to absolutely determine that the files are identical. A good checksm program can do that, but I don't think the hassle is worth the effort.