Free Republic
Browse · Search
General/Chat
Topics · Post Article

To: Hardastarboard
I’m seriously puzzled how this could have gotten messed up if the executable hadn’t been changed for essentially 5 years.

Simply because it is a system file does not mean that it does not depend upon others for its operation, or that MS will not change it and/or others somehow in a future configuration.

I had a similar problem some years ago when a few particular pieces of software would no longer run when there was no problem previously. Turned out that MS had updated a particular dll file for "greater efficiency", however the update broke other (non-MS) programs that needed a particular function in that file to operate. Not surprised that something similar appears to have occurred again.

77 posted on 01/18/2014 8:19:16 PM PST by Utilizer (Bacon A'kbar! - In world today are only peaceful people, and the mooslimbs trying to kill them-)
[ Post Reply | Private Reply | To 76 | View Replies ]


To: Utilizer

Got it. That explanation makes sense.


81 posted on 01/19/2014 5:13:09 AM PST by Hardastarboard (The question of our age is whether a majority of Americans can and will vote us all into slavery.)
[ Post Reply | Private Reply | To 77 | View Replies ]

Free Republic
Browse · Search
General/Chat
Topics · Post Article


FreeRepublic, LLC, PO BOX 9771, FRESNO, CA 93794
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson