> The .NET framework runtime, like other libraries you have, won't run unless
> some other application called it. (Maybe the IIS on behalf of a web
[quoted text clipped - 3 lines]
>
> So most likely you have to find out what the buggy application is.
Lau Lei, thanks. The only application using this is ATI (my Radeon
video card). I guess I'll just uninstall it and see what happens.
As to the virus suggestion, that really is funny. My HDD was just
low-level formatted and this is, for all intents and purposes, a virgin
install in which I have almost _nothing_ but the OS installed.
And ATI. Which is the source of these persistent Net Framework errors.
Next step: Uninstall Net Framework and see what happens . . .
Angel
Lau Lei Cheong - 21 Jul 2005 02:44 GMT
If you really have identified that ATI driver/package that'll use .NET
framework, I'll highly recommand you NOT to uninstall it.
Display card control applets (I think not likely the driver itself, .NET is
not a good enough platform for device driver programming) are sometimes
essential for your system to run correctly. If you just uninstall the .NET
framework, it'll ;ikely to case fatal exception. (Better hope that's not a
blue screen)
Search for the card manufactorer's web site to see if they've release an
update.
<byte.this@usa.net>
???????:1121897860.102365.234180@f14g2000cwb.googlegroups.com...
>> The .NET framework runtime, like other libraries you have, won't run
>> unless
[quoted text clipped - 19 lines]
>
> Angel
Scott M. - 21 Jul 2005 21:42 GMT
When you did your HDD re-format, did you run FDISK /mbr first? If not, you
could have a virus residing in your Master Boot Record that a format
wouldn't touch.
>> The .NET framework runtime, like other libraries you have, won't run
>> unless
[quoted text clipped - 19 lines]
>
> Angel