Warning about Net Framework

M

ms

Long ago I installed Net 1.1 for a utility that required it. I have come to
dislike and avoid any application written to require Net.

Awhile ago, I uninstalled Net Framework. It left registry entries behind,
and problems. I deleted all registry entries and windows folder entries
relating to it, but it still left some issues. I posted here then and was
advised to go to a MS Net newsgroup, that would require some more work so I
didn't.

Removing Net Framework did speed my shutdown time, from about a normal (?)
15 seconds down to now about 2 seconds, equal to my W98 computers.

But it causes 2 issues after windows is running, a screen "trying to
install" that flashes by, and a fixed screen "Net Framework 1.1
Initialization Error". This screen must be closed.

It certainly re-affirmed my feelings about MS Net Framework.
For you experts, this is no issue, but for the rest of us, I would sure
recommend to avoid anything written with Net Framework, and if it is
already installed, leave it alone.

ms
 
D

Dave Patrick

The error is undoubtedly caused by the registry hacking. You probably will
need to clean install the operating system in order to recover from this.
Then if you still want no dotnet then stay away from anything newer than
early 2002



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
 
Q

Querulous

Then if you still want no dotnet then stay away from anything newer than
early 2002

Not true; I have everything running on 2k that I also have on xp/vista and I
have never installed dotnet. Most of the apps are quite current.

Additionally, I have abandoned VB and Java apps, as well.

If you like dotnet, fine, but you don't really need it, if you are reasonably
resourceful.
 
D

Dave Patrick

Sorry, the qualification of course should have been anything that utilizes
dotnet. Windows 2000 would natively support most VB apps.



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
 
L

Linea Recta

What I still don't understand is why it seems so hard to write uninstall
programs that actually work.
What can be so hard about undoing all changes and/or additions made by
oneself? This would make life much easier for a lot of users! Or can I
conclude the resulting mess is intentional?



--
regards,

|\ /|
| \/ |@rk
\../
\/os
 
D

Dave Patrick

If what was installed is immediately uninstalled then the process is much
simpler as opposed to all of the possible permutations when some items are
installed later on that the original uninstall routine has no knowledge of.


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top