Update4:

Upon finding that MCP2210DLL-UM.dll crashes depend22.exe I located a copy o=
f
the MCP2200 Unmanaged DLL called SimpleIO-UM.dll . The exact date and
package it comes from is not at hand now, but it also crashes depend22.exe =
..
depend22.exe works fine on all dlls I tried it on, including on msvcp90.dll
msvcr90.dll msvcm90.dll which I have on my system in storage. The scary par=
t
is, there seem to be several binary versions of msvc?90.dll which evaluate
to different checksums. I have about 5 sets on my windows system in SXS
storage among other places and each has a different checksum. Either someon=
e
is trying to scare me and succeeding, or the world is upside down. System
compiler libraries from one distribution are supposed to be unique and have
verifyable checksums?! At least in my, somewhat sane, *nix and embedded
world?! Just as a late Halloween trick, assuming you have a Windows version
with side by side storage, mounted safely under some unix directory, using
the command: md5sum `locate -ir 'sxs.*msvcr90\.dll$'` in a *nix shell
yielded 4 copies in SXS, each with a different md5sum . Also ls -l `locate
-ir 'sxs.*msvcr90\.dll$'` yields 3 different file sizes (!), i.e. 2 copies
of 2 sizes and a single copy of a 3rd size. Keep heart pills nearby when
doing this please. Incidentally the md5sums and sizes were, for reference (=
heart
pills near please):

655872 e7d91d008fe76423962b91c43c88e4eb
655872 4d03ca609e68f4c90cf66515218017f8
653120 fa093f6a65507f7c2ae9697ce2a904cc
653120 7538050656fe5d63cb4b80349dd1cfe3
653136 ebe9f2ed58018dd0fc2a7c0d5f4debe0

I don't know what you folks will do or say about this, but I am
making/scripting some dll and exe name<->checksum<->date verifyers/loggers
right now, will be busy for a while. I'll never complain again about Window=
s
being the same old trick over and over again, I promise!



--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.