←  AutoPatcher Addon & Extras Module Depot

AutoPatcher Forum

»

.NET Framework Addon Pack

ViroMan's Photo ViroMan 03 Mar 2012

ohh yes that is the much older version of Autopatcher. You really should not get that one.
Quote

DesertJerry's Photo DesertJerry 05 Mar 2012

.Net Framework 4.0.3 updates posted by Microsoft (32 and 64 bit)

NDP40-KB2600211-x86.exe

NDP40-KB2600211-x86-x64.exe
Quote

ViroMan's Photo ViroMan 07 Mar 2012

Older .NET signed. Will not add in new updates. Click click is nearing finish with his scripts and will add the needed updates.
Quote

dkdk_it's Photo dkdk_it 12 Mar 2012

View Postdanieldecarli, on 03 March 2012 - 03:41 PM, said:

Thanks guys.
I was just wondering for a download with everything included because I saw there is an "AutoPatcher_WinXP_Aug07_x86_ENU_Core.exe" file for upgrading XPs with SP3s. Anyways, I got it. Thanks for sharing it.

Amazing! Posted Image
Have you that file?!? It's antique! (TheBlazingAngel was the ENU releaser in 2007 August).
Quote

Killjoy's Photo Killjoy 28 Mar 2012

View PostKilljoy, on 30 October 2011 - 11:26 PM, said:

Yo to all! Is there any way to create separate .NET Addon pack? I mean x86 and x64.
I don't need (for example) x64 updates yet I'm using Windows XP SP3.

Afterall that complete pack is almost 700MB. I've deleted x64 updates, but after every "update check" that thing downloads x64 updates again.

In APUP updater we have Win 7 SP1 x86 separated from x64 updates. Why "developers" of APUP can't create separate pack for .NET pack???


P.S. Microsoft Update Center reports these updates as available. They are not present in the current update pack.


View PostViroMan, on 31 October 2011 - 12:46 AM, said:

Domenico is working on separating the X86 and X64 for a few things. Im not sure when they are due.

View Postdkdk_it, on 31 October 2011 - 04:08 PM, said:


Yep. I'm working on .Net and Commons release... I've not many time but I hope to finish in a couple of week.


Any progres on that separating .NET on x86 updates and x64 updates???
Right now, total size of .NET Update Pack is 1.03GB.

I've updated system through MS update.
After MS Update (Microsoft Update), these updates in APUP are still shown as available for installation.

Posted Image
Quote

ViroMan's Photo ViroMan 30 Mar 2012

Click Click has a version to separate the scripts already done. Problem is(at least I think its a problem anyways) the way its designed... it will delete some of your downloads the first time you run it. If you run the x86 update it will delete the x64 files you downloaded. That can be good if your an x86 only system. That can be bad if you want to keep the x64 files. You have to redownload those files. I think the way he has done it is acceptable to many people but not all. I am trying to come up with a work around to make it acceptable to all. The good thing... Everything is so much better displayed. You only end up with 3 directories and the files sorted by architecture.

For those of you using APUP2 you can point it to releases2.list in the options area and try out the new scripts.

Warning... The releases2.list is NOT current in everything else. It is only a testing area for downloads. There are old/new things in there. IF you want to download a test item you may but, switch the list back to releases.list afterwards.
Also since its the testing area... IF you download something, its at your own risk. Don't be there unless your willing to take the risk of having extra stuff in your modules area and thus not being official.

PS im not bagging on you Click Click. You did good work and I can speak for everyone in saying thanks for your hard work.
Edited by ViroMan, 30 March 2012 - 07:27 PM.
Quote

click-click's Photo click-click 30 Mar 2012

I have no problems with that. I did what I thought was best being limited to the way the scripts work. The plus side of it is that it will save disk space for those users selecting either x86 or x64. The negative side of it is that those users requiring both x86 and x64 will need to partially re-download some files. If the user wants both, I recommend he runs APUP twice, selecting X64 on the first pass and then x86 on the 2nd pass. This will require the least amount of files that need to be re-downloaded which will be approximately 270MB.
Quote

Whatacrock's Photo Whatacrock 31 Mar 2012

Firstly I would like to thank you click-click for a humungous effort with sorting out the dotnet directory...much easier to read now..
Secondly ran apup2 with release2 .list and on the x64 run I received the one or more files failed verification. Here is the excerpt from the logfile area where I believe the error is


Detection error for file C:\APUP\modules\Components\__dotnet\KB982168-NDP30SP2-x64.apm
MD5 Hashes do NOT match. Expecting 1D1607EADA138133A45D7E47757C2B31, but found BC1BEB87C4F635F91221717CFFB46970!!!
MD5 Hash (8375E5B2C57DC88E293DBBE4D1F3A95F) Matches .NET Family x64 KB Definitions
MD5 Hash (4776975494B2F926C04ADBBD15886FCC) Matches .NET Family x64 KB Definitions
Item .NET Family x64 KB Definitions is missing or its parts are not completely downloaded. Adding whole download for this item to the queue.
--Adding DownloadFrom=http://www.autopatcher.com/releases/dotnet/windows_dotnet_x64_20120306.7z--

Also found this one at the end of the logfile

***Processing Cleanup Routines***

Download Of File .NET Family x86 KB DefinitionsFailed. Skiping AfterDownload Action.
Extracting. Command: "C:\APUP\apup_bin\7za.exe" x "C:\APUP\temp_bin\windows_dotnet.7z" -o"C:\APUP\modules\Components\__dotnet" -y

*** ! FINISHED ! ***

***Processing Cleanup Routines***

Download Of File .NET Family x86 KB DefinitionsFailed. Skiping AfterDownload Action.
Extracting. Command: "C:\APUP\apup_bin\7za.exe" x "C:\APUP\temp_bin\windows_dotnet.7z" -o"C:\APUP\modules\Components\__dotnet" -y

*** ! FINISHED ! ***
Hope this helps
Posted Image
Quote

ViroMan's Photo ViroMan 31 Mar 2012

try running the script from apup v1

copy this into a batch file and run it...
apup.exe /log /LISTFILE:http://www.autopatcher.com/releases2.list

That will let apup run the second list. Your problem might be due the version of apup2 that doesn't like dos commands. Run the same set of downloads and see if you get different results. Well of course the logs will be slightly different.

I will check the script later... im working on the VC++ script right now.

Ohh hey... small note... Don't run the two that have "_WBatch". I am experimenting with that version. I am trying to implement a batch file that will ask you if you want to keep the data rather then delete it.
Edited by ViroMan, 31 March 2012 - 03:47 AM.
Quote

Whatacrock's Photo Whatacrock 31 Mar 2012

Ran the script through apupv1 and still get errors .
Logfile attached
Spoiler
Quote

ViroMan's Photo ViroMan 31 Mar 2012

Ok... So I looked it over and looks like there was a small copy & paste error in the script. No biggy... just deleted the extra "DownloadFrom=" in the url link to do the downloading. That aught to fix that problem.
Quote

Whatacrock's Photo Whatacrock 31 Mar 2012

Download error is now fixed
Thanks
Quote

ViroMan's Photo ViroMan 31 Mar 2012

Anything else to say about it? Everything show up pretty blue and official?
Quote

Whatacrock's Photo Whatacrock 31 Mar 2012

Everything for x86 in pretty blue..my autopatcher states unofficial and upon checking the release list the x64 release states false.If I download the x86 then it states false,reverse it and download the x64 then ap states x86 is false.
here is the log when I check both x86 and x64

Spoiler

Edited by Whatacrock, 31 March 2012 - 06:03 AM.
Quote

ViroMan's Photo ViroMan 31 Mar 2012

hmm from what I can tell the script calls for those missing files to be deleted each time...strange. And then there is the windows_dotnet.. that is due to trying to download into the same file name. A small mistake there. corrected.

Ok... I commented out the commands to delete the same files over and over again and also corrected the small naming mistake. There still seems to be some things wrong... im looking into it... actually... ill upload the changes I have now... and continue this tomorrow.
Quote

click-click's Photo click-click 31 Mar 2012

View PostWhatacrock, on 31 March 2012 - 05:52 AM, said:

Download error is now fixed
Thanks

The scripts should have worked by not picking both scripts at the same time. Run each .NET in separate passes. First x64 and then x86. I made a mistake using the same name for the apm .7z, but it is a problem only when both x86 and x64 are selected. Separate names for the windows_dotnet.7z is the correct way to fix this. I wiil retest the scripts for selecting both .NETs in one pass.

@Viroman

I don't know why you commented out the deletion of NDP20SP2-KB979909-x86.apm and NDP30SP2-KB982168-x86.apm in the .x86 script. Commenting out the other files will leave them hanging around if someone only wants x86 and visa versa and that will cause an unofficial status. Fixing this for both dotNETs at once, breaks it for the rest. I will look to see if there is a way to make the scripts work better if both .NETs are picked

edit: I just ran a test with what I suggested and 6 x64 apm files do get deleted on the x86 pass. Looks like a catch-22 situation. I need to look at this closer.
Edited by click-click, 31 March 2012 - 01:50 PM.
Quote

click-click's Photo click-click 31 Mar 2012

View PostViroMan, on 31 March 2012 - 06:49 AM, said:

hmm from what I can tell the script calls for those missing files to be deleted each time...strange. And then there is the windows_dotnet.. that is due to trying to download into the same file name. A small mistake there. corrected.

Ok... I commented out the commands to delete the same files over and over again and also corrected the small naming mistake. There still seems to be some things wrong... im looking into it... actually... ill upload the changes I have now... and continue this tomorrow.

I would appreciate it if only one person makes the changes until the final release. Should I continue testing? It's your call.
Edited by click-click, 31 March 2012 - 06:28 PM.
Quote

Whatacrock's Photo Whatacrock 31 Mar 2012

@click-click... I ran apup with release2.list as you prescribed and upon checking ap it would show the opposite release as false ie download x64 first then x86 shows up in red and status is false.Do a run with only x86 checked and then x64 is red and status false.



A question for you ...I browsed the dotnet folder and found it looked much easier to read than having so many folders for each hotfix.
In dotnet spotted 2 apm files which seemed odd.......$$dotnet2.apm and $$dotnet3.apm.... what are they ??
Edited by Whatacrock, 31 March 2012 - 02:02 PM.
Quote

click-click's Photo click-click 31 Mar 2012

Yes, I noticed the holes in my suggestion after I did some additional tests. The problem is that some current dotNET apm files already have the new filename format starting with KBxxxxxxx and are being deleted respectively depending on whether x86 or x64 is being processed. All files without the new filename format are deleted and never appear again. The ones that already have the new filenames will be present after each APUP run. I think I may have a solution that will work for everyone, but I need some time to test and verify.

The $$dotnet2.apm and $$dotnet3.apm are subgroups under the main dotnet 3.5 component. .Net Framework 2.0 SP2 and .Net Framework 3.0 SP2.
Edited by click-click, 31 March 2012 - 06:28 PM.
Quote

Whatacrock's Photo Whatacrock 31 Mar 2012

@click-click... thanks for explaining what those 2 apms were for.
Okay ran apupv1 with release2 list on ap with old school dotnet directory(different OS), proceeded with x64 first and one or more files failed verification.
Download size for x64 is 149.85 Mb
x86 download size is 266.76 and received no errors or failed files(this is good I hope)
Attached logfiles, the first being x64 and second x86

Spoiler

Spoiler

Hope this helps
Quote