hurricane3
SOH-CM-2023
going to get 4.0
OK I'am going to get 4.0 now thanks
OK I'am going to get 4.0 now thanks
XP trouble
- Thread starter aeromed202
- Start date
aeromed202
SOH-CM-2014
More good stuff, thanks everyone.
First, a lone update installed correctly so here's hoping that version 4 is good. Second, I started the MS ball going by saying my updates were not installing which seemed to make them focus on .Net issues. Third, couldn't say about Windows vs Microsoft, are they not inseparable? Fourth, I recall one FS addon that needed a certain Framework, FSINN? Haven't looked at it in years. And last, I am also thinking of installing all .Net versions but only if the current arrangement fails.
First, a lone update installed correctly so here's hoping that version 4 is good. Second, I started the MS ball going by saying my updates were not installing which seemed to make them focus on .Net issues. Third, couldn't say about Windows vs Microsoft, are they not inseparable? Fourth, I recall one FS addon that needed a certain Framework, FSINN? Haven't looked at it in years. And last, I am also thinking of installing all .Net versions but only if the current arrangement fails.
aeromed202,
I used to think that once a PC had migrated from Windows Update to Micro$oft Update, that was it. However, I recently found out that you can move "back" to Windows Update if you click on the "change your settings" link on the Micro$oft Update home page, then clear / deselect the option at the bottom of that screen. I've tested it and it does work.
As I said in an earlier post, M$ appear to have changed their policy on version compatibility with v4, though it seems that many people cannot grasp the difference from their old policy or the way that .NET Framework was different from most other software.
Anyway, if you now have Updates working, I think your remaining concern is just how backward-compatible v4 is when used with other products like FSINN. On that, I'm afraid only time will tell, since most people are unlikely to bother testing such things with only v4 installed (by neglecting to uninstall whichever previous version was required). You could of course do as claudius24 suggested and install all the different versions, but then nobody will ever know whether v4 alone meets all your needs,
hope that helps,
Ro
I used to think that once a PC had migrated from Windows Update to Micro$oft Update, that was it. However, I recently found out that you can move "back" to Windows Update if you click on the "change your settings" link on the Micro$oft Update home page, then clear / deselect the option at the bottom of that screen. I've tested it and it does work.
As I said in an earlier post, M$ appear to have changed their policy on version compatibility with v4, though it seems that many people cannot grasp the difference from their old policy or the way that .NET Framework was different from most other software.
Anyway, if you now have Updates working, I think your remaining concern is just how backward-compatible v4 is when used with other products like FSINN. On that, I'm afraid only time will tell, since most people are unlikely to bother testing such things with only v4 installed (by neglecting to uninstall whichever previous version was required). You could of course do as claudius24 suggested and install all the different versions, but then nobody will ever know whether v4 alone meets all your needs,
hope that helps,
Ro
Editvoicepack needs the .NET framework, and this initially caused me difficulties at the start of my recent rebuild; it is how I found about about .NET 4.0, as this fixed the problems nicely.