Jump to content


.NET Framework Addon Pack


149 replies to this topic

#141 click-click

    AutoPatcher Expert

  • Members
  • PipPipPipPip
  • 293 posts
  • Gender:Male

Posted Yesterday, 12:05 PM

View PostViroMan, on 09 February 2012 - 07:36 PM, said:

bah.. I messed up the 7z file I zipped it into a dir with files in it, instead of a zip with files in it. Try now. I wish I had all the files so I can test the damn things without having to make you guys do the testing.

I'm afraid it's still not right. I'm still getting file verification failed.

#142 click-click

    AutoPatcher Expert

  • Members
  • PipPipPipPip
  • 293 posts
  • Gender:Male

Posted Yesterday, 12:11 PM

View PostViroMan, on 08 February 2012 - 11:45 AM, said:

Click Click, your always on top of this stuff(a compliment), if you ever wanted to help us manage the scripts we would seriously appreciate it. Its hard keeping up with all of this by ourselves. Really, its not hard to modify a script... its hard for me to download all of these updates so I can make the scripts though. (I hate my AT&T DSL it might as well be a 56k modem)

Send me a PM on what needs to be done and I will try and help where I can.

#143 click-click

    AutoPatcher Expert

  • Members
  • PipPipPipPip
  • 293 posts
  • Gender:Male

Posted Yesterday, 03:35 PM

@ViroMan
(DONE) NDP20SP2-KB2478658-x86.apm - replaced by KB2539631 which is missing
You added KB2539631 but forgot to remove KB2478658 which was superseded by the fix you added.

(DONE)NDP35SP1-KB2657424-x86.apm - incorrect title .. (KB2657424_X86 instead of KB2657424_X64)
Still the same as before. The title entry should be:
Title=Security Update for Microsoft .NET Framework 3.5 Service Pack 1 on Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 (KB2657424_X6486)

KB2656356 says it doesn't have an registry detection but, they all do... so I created one that 'should' detect it but im not sure if it works yet.
No. This fix is for Win7 and not XP. There is no registry detection. Look at Windows6.1-KB2518869-x86.apm and you will se what I mean. KB2656356 should be done the same way. This is what the .apm should look like:
Spoiler

DONE)NDP40-KB2656351-x86.apm - bad detection .. (DotNetFramework=3)
Same as before. I think you misunderstood. DotNetFramework=3 is incorrect and should be =4

Also, the reg detection is still incorrect. It should be as follows:
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2656351

I only checked the x86 files. Some of the x64 apms may also be messed up. Getting close to all blue Posted Image

.

Edited by click-click, Yesterday, 03:41 PM.


#144 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPip
  • 326 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted Yesterday, 05:43 PM

check the other thread... I forgot to upload the newer dotnet zip. this could be solved now.

#145 click-click

    AutoPatcher Expert

  • Members
  • PipPipPipPip
  • 293 posts
  • Gender:Male

Posted Yesterday, 06:57 PM

Still getting verification error. Although some of the stuff above is okay now. Some corrections are still missing
I will post seperately.
Spoiler

Edited by click-click, Yesterday, 07:09 PM.


#146 click-click

    AutoPatcher Expert

  • Members
  • PipPipPipPip
  • 293 posts
  • Gender:Male

Posted Yesterday, 07:30 PM

Windows6.1-KB2656356-x86.apm and NDP40-KB2656351-x86.apm are still not correct. Please review my previous post about those two KBs.

Edited by click-click, Yesterday, 07:30 PM.


#147 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPip
  • 326 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted Yesterday, 09:43 PM

Took me long enough but Here we go

Spoiler

At least the files download properly... I will do an AP install now and check back shortly.

Edited by ViroMan, Yesterday, 09:44 PM.


#148 click-click

    AutoPatcher Expert

  • Members
  • PipPipPipPip
  • 293 posts
  • Gender:Male

Posted Today, 02:05 AM

I have just uncovered more problems with dotNET. I will append the apm changes once I'm finished.

#149 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPip
  • 326 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted Today, 02:21 AM

I just went through a few of the files myself. I may have fixed what you have found. Try a new download.

#150 Whatacrock

    Advanced Member

  • Members
  • PipPipPip
  • 54 posts
  • Gender:Male
  • Location:Australia
  • Interests:Cars ,computers, movies

Posted Today, 06:47 AM

Tried rerunning apup2 and we have a go.....NO ERRORS.................WOOOORAHHHH

All we need at the moment for scripts to be signed again to make autopatcher display official/supported version.

Edited by Whatacrock, Today, 06:48 AM.






3 user(s) are reading this topic

0 members, 3 guests, 0 anonymous users