Path Command and Duplicated Files.

1 thumbnail and 1 file attached. Why can't I delete some of these duplicated files as in the olde days the Path command was tied to the Parent (or sub-Parent) Folder. I assume it still is.

This is only a small example of duplicated files. Why can't I delete the entry in \Windows\system\dllcache and \Windows\I386\system32 as there is the same file further up the Path.

There are so many duplicated files just because ( I assume that programmers do not know how the PATH command works), or they are too lazy to set up programs properly.

 

Bump. Bazza

 

Windows\I386 looks like a direct copy from a CD disk to the hard drive. The clue is the CAPITAL letters in the file name NTDLL.DLL. If you own a copy of the media then this is just litter. That takes care of 2 entries. The \cmdcons\system32 entry is a valid windows utility directory. It has several command line programs for troublshooting. It's usually found on Windows 2000 corporate computers. It helps to fix them when the GUI goes kablooey in multi-user environments. Keep that one. That takes care of three. The other 2 are Windows OS. Leave them alone. Windows\System32 and Windows\System32\dllcache are current and backup copies. Leave them alone! That's 5.

 

Thanks for the info, prometheous. :major These 5 were only a small sample of duplicates on my system. Why do we need repetitions in Windows\System32\dllcache when the originals are in Windows\System32?

I realise they are repeated for backup/safety reasons but why does MS do this as most other programs don't bother duplicating entries somewhere else. I will have to check out how the CAPITAL versions got onto my lappy.

I have a program that crashes and points to that DLL. I don't know which DLL is the culprit.:cry They all appear to be the same size. Thanks again. Bazza

===