If you have RCS NewsBuilder and you find that Microsoft Dot Net 3.x permanently breaks it, I have a solution.
Once you install Dot Net 3.0 and/or 3.5 on Windows XP, permanent changes are made that prevent NB from running on that PC again without reinstalling Windows. No amount or combination of un/re-installing Dot Net (all of them) and/or un/re-installing NB will fix the problem.
I went through this twice and there is now a nice engineer-head-sized hole in the wall near each of those computers.
The solution is Aaron Stebner's .NET Framework Cleanup Tool: http://blogs.msdn.com/astebner/pages/8904493.aspx.
Use it as follows:
1) Uninstall each version of Dot Net in reverse order; that being 3.5, 3.0, 2.1, 2.0, etc, all the way down to zilch. Ignore any errors such as with the "1.1 Fix". This will all take a while; so bring a hamburger and a martini. Amazingly - It's not necessary to reboot at any point, unless you find a program is running that uses Dot Net. In my case, no reboots were needed through any of this entire process on any of the machines I did it to.
2) Run the cleanup tool. Choose to cleanup "All Versions" of Dot Net. When it's done, click exit.
3) Run the Dot Net 2.0-SP1 installer that comes with your NB. RCS tech support keeps a copy of it on our NewsGen server.
That's it. Try your NB now; it should run. As I said above, you don't even need to reboot unless some other program was using Dot Net.
Warning: Some programs may need other versions of Dot Net. You should (should) be able to safely reinstall 1.x & 2.x, but 3.x will just break NB again. If you find that one or more pieces of software need Dot Net 3.x, you're stuck. Then you have to decide which software is more important, or drop in an extra PC next to the first one. =-)
Good luck!
Once you install Dot Net 3.0 and/or 3.5 on Windows XP, permanent changes are made that prevent NB from running on that PC again without reinstalling Windows. No amount or combination of un/re-installing Dot Net (all of them) and/or un/re-installing NB will fix the problem.
I went through this twice and there is now a nice engineer-head-sized hole in the wall near each of those computers.
The solution is Aaron Stebner's .NET Framework Cleanup Tool: http://blogs.msdn.com/astebner/pages/8904493.aspx.
Use it as follows:
1) Uninstall each version of Dot Net in reverse order; that being 3.5, 3.0, 2.1, 2.0, etc, all the way down to zilch. Ignore any errors such as with the "1.1 Fix". This will all take a while; so bring a hamburger and a martini. Amazingly - It's not necessary to reboot at any point, unless you find a program is running that uses Dot Net. In my case, no reboots were needed through any of this entire process on any of the machines I did it to.
2) Run the cleanup tool. Choose to cleanup "All Versions" of Dot Net. When it's done, click exit.
3) Run the Dot Net 2.0-SP1 installer that comes with your NB. RCS tech support keeps a copy of it on our NewsGen server.
That's it. Try your NB now; it should run. As I said above, you don't even need to reboot unless some other program was using Dot Net.
Warning: Some programs may need other versions of Dot Net. You should (should) be able to safely reinstall 1.x & 2.x, but 3.x will just break NB again. If you find that one or more pieces of software need Dot Net 3.x, you're stuck. Then you have to decide which software is more important, or drop in an extra PC next to the first one. =-)
Good luck!