Thanks for your reply. Let's see:
"Ronnie Vernon MVP" wrote:
Probably true. This "new" dll I have is old, as in mid-90s. I've used it
since Win95 came with card games. It was on a public ftp, and I think if you
google for it you may find some old sites with it. I'm all but certain it's
"safe", since I've been replacing cards.dll on previous Windows systems with
it many times before successfully, with no problems (I mean, what problems?
cards.dll is only used for the card games... it will either work, or stop
them from working, that's all).
By the way, the cards.dll that ships with WinXP looks exactly the same size
as cards.dll in Win98SE (same byte size, same date), so... don't you think it
is reasonable to think that WinXP is expecting the same format for cards.dll,
and therefore if the swap is made, it should work with the modified cards.dll?
Okay, I understand that. To elaborate on my experience, if I merely copy
over the modified cards.dll to \system32, when I run Freecell it will still
show the old cards, and investigation will reveal that cards.dll has been
reverted to the original copy (and like you said, it "backup"-ed from the
copy in \dllcache).
But that is what I did, and the error I mentioned in my original post shows
Even though BOTH cards.dll in \system32 and \dllcache match, WinXP somehow
knows it's not the original cards.dll.
Of course, restoring the original cards.dll to both folders will allow me to
play the card games again, but with the original old cards. Problem not
When we install new device drives, often dll's get changed (i.e. replaced
with new versions), right? Okay, coming back to my question: *How* do they do
that? Why does "Windows File Protection" not get in the way? Is there any way
I can talk to this protection, to let it know I want to upgrade cards.dll? Or
to paraphrase, how would I "install" the new cards.dll?
Thanks for trying. I really hope somebody knows the answer, after all, don't
dlls get swapped every day when people install stuff.