I have the Service Pack installed, but this program is just plain
buggy. I don't even WANT it, but I couldn't get my ATI drivers to
install unless I had it on the system.

I don't mind if the files just sit there; I just don't want them
RUNNING. Not once have I been able to shut down my computer without
having to suffer a 2 minute wait while "NET FRAMEWORK is not
responding."

I have Windows 2000 Professional and am about to commence a reinstall
with new HDD's, so I want to see this modification in action BEFORE I
do the new install, just to see how it's affecting my video (if at
all).

Thanks.

I've been working with .NET since early beta (2000) and have never heard of
the error you describe. Most likely you have a bad installation.


<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I have the Service Pack installed, but this program is just plain
> buggy. I don't even WANT it, but I couldn't get my ATI drivers to
> install unless I had it on the system.
>
> I don't mind if the files just sit there; I just don't want them
> RUNNING. Not once have I been able to shut down my computer without
> having to suffer a 2 minute wait while "NET FRAMEWORK is not
> responding."
>
> I have Windows 2000 Professional and am about to commence a reinstall
> with new HDD's, so I want to see this modification in action BEFORE I
> do the new install, just to see how it's affecting my video (if at
> all).
>
> Thanks.
>

> I don't mind if the files just sit there; I just don't want them
> RUNNING. Not once have I been able to shut down my computer without
> having to suffer a 2 minute wait while "NET FRAMEWORK is not
> responding."
>
NET FRAMEWORK is NOT an application.
Therefore this sentence doesn't makes sense at all.

What about using some tools (such as the TaskManager) to find out which
application is really hanging?
maybe a virus?
something even less heard of?

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
application , or whatever that's written in .NET) If you removed everything
that need it, it'll quietly sit there, and probably never ever get a chance
to be loaded even if you've installed it.

So most likely you have to find out what the buggy application is.

<(E-Mail Removed)>
???????:(E-Mail Removed)...
>I have the Service Pack installed, but this program is just plain
> buggy. I don't even WANT it, but I couldn't get my ATI drivers to
> install unless I had it on the system.
>
> I don't mind if the files just sit there; I just don't want them
> RUNNING. Not once have I been able to shut down my computer without
> having to suffer a 2 minute wait while "NET FRAMEWORK is not
> responding."
>
> I have Windows 2000 Professional and am about to commence a reinstall
> with new HDD's, so I want to see this modification in action BEFORE I
> do the new install, just to see how it's affecting my video (if at
> all).
>
> Thanks.
>

Lau Lei Cheong wrote:
> 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
> application , or whatever that's written in .NET) If you removed everything
> that need it, it'll quietly sit there, and probably never ever get a chance
> to be loaded even if you've installed it.
>
> 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

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.

<(E-Mail Removed)>
???????:(E-Mail Removed)...
> Lau Lei Cheong wrote:
>> 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
>> application , or whatever that's written in .NET) If you removed
>> everything
>> that need it, it'll quietly sit there, and probably never ever get a
>> chance
>> to be loaded even if you've installed it.
>>
>> 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
>

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.


<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Lau Lei Cheong wrote:
>> 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
>> application , or whatever that's written in .NET) If you removed
>> everything
>> that need it, it'll quietly sit there, and probably never ever get a
>> chance
>> to be loaded even if you've installed it.
>>
>> 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
>