Solved Installing .Net 1.1 in Windows 7 Pro fails

[A Guy]

Perhaps the difference is SP1? .net 1.1 applications should work with .net 3.5 and above, so ultimately it will be the programs coding. I understand the issue is getting .net 1.1 on your system regardless, and while I see issues with people getting it done on x64, it is supposedly doable. Whether these instructions were pre SP1 I don't know.

How to Install .net framework 1.1 in Windows 7 64-bit? - Microsoft Community

A Guy

 

[Slartybart]

Aaron Stebner is a .NET guru and well respected in the MS community. There's very little risk using the .NET cleanup tool, but it is a fair amount of work / time. If you DO back off .NET, turn off automatic Windows update for the duration of your exercise.

Remember to turn AUTOMATIC UPDATES back on afterwards.​

... Before I try Aaron Stebner's cleanup tool, which looks risky, I will try Process Monitor and other approaches that others in this thread have kindly suggested.

Have you tried turning off DEP and installing 1.1 perpost 18?

Remember to turn DEP back on afterwards.​

If you don't feel comfortable temporarily turning off DEP just to install (test...) .NET 1.x then here's an alternative: Creating an administrative install point for the .NET Framework, a service pack and a hotfix

This seems to be more work than just simply turning off DEP and installing .NET 1.x given that this might not resolve the issue. We won't know until you try it in your environment.

Bill

 

[rcdunbar]

.Net 1.1 now installed, finally

I'm back, and I finally got .Net Framework 1.1 to install under Win 7 Pro, using the well known Procedure that calls for creating a C:\DotNet folder. To recap, previously I had done everything according to the 8-step instructions, but in step 8 - run netfx.msi - the process failed to complete, went through a rollback, and 1.1 was nowhere to be found.

I worked with Process Monitor (ProcMon) for a while; but it created mountains of data that, even with a lot of filtering, I couldn't make sense out of. I installed Visual Studio 2010 (it was on my pre-clean system), hoping it might bring 1.1 along with it. It didn't.

So, to make the "DotNet" process work I deleted all temp files in my user profile, as well as a lot of other Win temp files, rebooted, turned off Norton's anti-virus, and ran netfx.msi from the command prompt as administrator. Bingo, it worked! .Net 1.1 now shows up in CP Programs & Features; and netfx_setupverifier sees and validates it.

This info appeared in a Visual Studio forum thread, for which I am grateful. These additional steps may not be needed on every system; nevertheless I strongly recommend that the ubiquitous "DotNet" procedure be updated to include them.

Thanks for everyone's help, and I hope I've made a contribution.

 

[A Guy]

Glad you got it sorted, confirmed the method works, and added what may be necessary if people have errors. Is your appliacation working after all that?

A Guy

 

[Layback Bear]

Could this been part of the problem? (Norton's anti-virus)

 

[rcdunbar]

Unfortunately my Excel application that utilizes Sterling Trader Pro still doesn't work - it crashes as soon as the DDE links try to update. I'm working with Sterling tech support to try to figure this out. They have no problem running a small Excel test file I created that uses exactly the same linking mechanism as the big file; so it's gotta be some glytch in my system.

.Net 1.1 shows up in CP P&F and in Revo Uninstaller Pro. However, it appears as 0 bytes with no version stated. Is this normal? Could it signal that something isn't quite right with the installation, even though netfx_setupverifier says the installation is OK? .Net 1.1 showed up the same way on my "pre-clean" system as well. I know that 2.0, 3.0, and 3.5 don't show up in CP P&F (or Revo) because they are considered to be part of the OS. But what's the story for 1.1?

 

[Slartybart]

Take a look at Windows features in CP->P&F. I don't have the definitve answer, but it might help to toggle the checkboxes that are .NET related.

Ask Sterling what is ticked on their test machine. Use thier working environment to compare configurations.

 

[UsernameIssues]

~~~
.Net 1.1 shows up in CP P&F and in Revo Uninstaller Pro. However, it appears as 0 bytes with no version stated.
~~~

I can only speak to CP P&F:

After installing .NET 1.1...
...but before installing .NET 1.1's SP1:




After installing .NET 1.1's SP1:

 

[rcdunbar]

Thanks to all who have responded throughout this thread.

Unfortunately, although your help got .Net 1.1 installed under Win 7 Pro, I have been unable to make my Excel trading application work again with Sterling Trader Pro. Even their tech support is stumped. So rather than pursue this apparent dead end I now plan to convert my application from DDE to RTD. RTD is a much newer technology, and Sterling recommends it. Their program provides the installation option of choosing RTD to access the stock market feed instead of DDE, and does not require .Net 1.1 for RTD.

Does Seven Forums have one or more tutorials on RTD? I've found your tutorials to be very useful, and have saved several of them. I'm new to RTD, so I'm looking for instruction and guidance.

Thanks

 

[UsernameIssues]

I did not see any tutorials on RTD on this forum.

You can write one for us in a few months

 

[rcdunbar]

I will gladly contribute a tutorial on Excel RTD, if and when I can ever get the Sterling Excel RTD Add-in to activate in Excel 2010 on my PC. So far everything I've tried, with much help from Sterling tech support, has failed. My machine must be cursed!

I will start a new thread on this issue, since it appears to be unrelated to this thread's original issue (installing .Net 1.1 on Win 7).

Thanks for everyone's help.