| For FF9 and TB9, it's the same file, in the root folder of
| both programs: msvcm80.dll. DAGS shows linkage to MS Visual
| Studio 2005.
Interesting. That's the VC++ 8 managed runtime.
There's another one called mfcm80.dll. I think those are
both installed with the VC8 runtime, as one of several
files, in case anyone wants to write C++-CLI software.
(I don't think anyone actually does. Writing managed
C++ defeats the purpose.)
In other words, it means that they installed the VC++8
runtime, which is not surprising as most people writing
C++ software on Windows use Visual Studio, and VS
software always requires a runtime. As long as no other
..Net files are in the program it doesn't use .Net. I'll have
to add a note about that to the utility.
| > Ahhh. That's a pain in the neck. See here:
| >
| >
http://www.jsware.net/jsware/scripts.php5#ie7prob
| >
| > The download there is a small script that changes a setting
| > to stop that behavior. IE asks whether you want to keep
| > letting a long script run, but then it doesn't listen to your
| > answer. It just asks over and over!
|
| I'll try that. However, I wonder if it'll still eventually
| lock-up; I just won't see the script nags?
|
No, it's just that it takes awhile to process so many files,
and IE has a default time limit. In other words, it's not
locked up. It's just busy. I've had that problem in the past
with HTA scripts that do extensive operations. That's how
I know about the Registry setting. If IE did lock up you
could use Task Manager to kill it, but in this case it's just
that IE normally expects scripts that run for a fraction of
a second, so it just assumes there's a problem. That's not
so bad. But then Microsoft messed up by programming it
so that IE ignores your response to the message window.
So a slightly helpful feature is instead a hair-pulling bug.
I'm glad you asked about all this. Now that I've written the
utility I can see it being very useful when cleaning up other
people's machines -- as a quick way to see whether .Net can
be removed.
I just uploaded another update. It's not really significant,
but it did recognize an oddball file in Open Office 3 (even
though OO doesn't need .Net) that the last version didn't
pick up.
Technical explanation, for anyone who's curious:
I wrote the original version on the basis of information I'd
found that the .Net header in a PE file starts 8 bytes into
the .text section. It turned out that was wrong. Apparently
..Net software written in Visual Studio is like that, so 95+ %
of .Net files will be like that, but I later found a couple of MS
files that have the table later in the .text section. Then I
decided that maybe I shouldn't even assume the .Net header
is in the .text section at all. And wouldn'cha know it....
Turns out the OO people wrote such a file.

It may be the only such file in existence for all I know, but
the latest version of the utility was worth doing just in case.
It's more "robust", as the geeks like to say. Now, if it finds
..Net header info. in a file, it makes no assumptions about
where in the file that header will be located.