.NET Framework Addon Pack
click-click
13 Feb 2012
ViroMan, on 13 February 2012 - 04:07 PM, said:
im working on those files you gave me click click... since you didn't send me the other parts I need.... the size and md5 of the files(not the apm files the exes that get downloaded)... I need to download them and get that info myself... it takes time since I have such a damn slow internet.
edit: hmm actually I guess that is my fault for not saying I would need that. sorry.
edit: hmm actually I guess that is my fault for not saying I would need that. sorry.
OK. I'll send them along the next time although you will still need to download the larger zip file. Do you want me to redo .NET and send it again?
Also, I think there is a size limit on what can be attached in this forum. Can the restriction be lifted for my User?
Edited by click-click, 13 February 2012 - 06:14 PM.
ViroMan
13 Feb 2012
the restriction is 2mb per user TOTAL. restrictions can be lifted although, I don't see why you would need such an action... your zip files are unlikely to exceed a few kb's. You don't need to attach the exe's themselves.. just a text file with the size and md5s of the files like the script file currently does. If you include the download location that would be sweet extra although I can get that perfectly fine myself(I have a download manager that I can grep the url from without downloading so I can get the actual download link instead of a dynamic link).
Dot Net Updated... not signed yet.(im still trying to work out why some x86 apms show up in an x64 environment.)
KB958481 and KB958483. I am probably staring right at it and can't see it.
Also click-click I see what you were talking about on KB961118. I decided to leave that in because I believe it belongs in the .net area. That update is only needed because a .net update screws something up. So its a fix you wouldn't need unless you downloaded .net updates.
Edited by ViroMan, 13 February 2012 - 06:25 PM.
Dot Net Updated... not signed yet.(im still trying to work out why some x86 apms show up in an x64 environment.)
KB958481 and KB958483. I am probably staring right at it and can't see it.
Also click-click I see what you were talking about on KB961118. I decided to leave that in because I believe it belongs in the .net area. That update is only needed because a .net update screws something up. So its a fix you wouldn't need unless you downloaded .net updates.
Edited by ViroMan, 13 February 2012 - 06:25 PM.
click-click
14 Feb 2012
I sent you an old file for NDP40-KB2572078-x64.apm. Please update the following line.
WindowsVersion=XP_X86,2K3_X86,VISTA_X86,LHSERVER_X86,SEVEN_X86 with
WindowsVersion=XP_X64,2K3_X64,VISTA_X64,LHSERVER_X64,SEVEN_X64
I'm checking the rest right now. Looks good at first glance. No verification errors downloading.
BTW, are both x86 and x64 exe files supposed to be downloaded for dotNET?
WindowsVersion=XP_X86,2K3_X86,VISTA_X86,LHSERVER_X86,SEVEN_X86 with
WindowsVersion=XP_X64,2K3_X64,VISTA_X64,LHSERVER_X64,SEVEN_X64
I'm checking the rest right now. Looks good at first glance. No verification errors downloading.
BTW, are both x86 and x64 exe files supposed to be downloaded for dotNET?
ViroMan
14 Feb 2012
for right now... yes. The more we separate things the more confusing it can become. I personally would like more separation, its part of the reason for the new scripts, the other part is that it will be much more simple to maintain.
All APM's will be downloaded then you can choose what updates you want. You will be able to chose the OS type and the cpu type(x64/x86) your targeting then go down to the individual files to download. It will also be more customizable as well. Any APM you create that deals with the same update will override the official update.
Edited by ViroMan, 14 February 2012 - 08:50 PM.
All APM's will be downloaded then you can choose what updates you want. You will be able to chose the OS type and the cpu type(x64/x86) your targeting then go down to the individual files to download. It will also be more customizable as well. Any APM you create that deals with the same update will override the official update.
Edited by ViroMan, 14 February 2012 - 08:50 PM.
click-click
14 Feb 2012
The following .apm files are still in the .7z. They have been superseded and should be removed. I mentioned
this in the README.
Windows6.1-KB2478662-x64.apm
Windows6.1-KB2478662-x86.apm
NDP40-KB2478663-x64.apm
NDP40-KB2478663-x86.apm
Other than that, the detection part of APUP is fine on my side.
Also, please review the file directories. Some of the file directories are missing . Example:
NDP20SP2-KB2539631-x64_files includes both x86 and x64 exe files which is confusing.
NDP35SP1-KB982306-x86.apm_files (includes x86)
KB982306.apm_files (includes both x86/x64)
Check C:\WINDOWS\autopatcher.log for details
A decision needs to be made whether to have a single directory or separate directories for x86/x64. Right now it is a mixed bag. I could imagine that some fixes will not even install the way the apm and directories are set up.
Edited by click-click, 14 February 2012 - 11:09 PM.
this in the README.
Windows6.1-KB2478662-x64.apm
Windows6.1-KB2478662-x86.apm
NDP40-KB2478663-x64.apm
NDP40-KB2478663-x86.apm
Other than that, the detection part of APUP is fine on my side.
Also, please review the file directories. Some of the file directories are missing . Example:
NDP20SP2-KB2539631-x64_files includes both x86 and x64 exe files which is confusing.
NDP35SP1-KB982306-x86.apm_files (includes x86)
KB982306.apm_files (includes both x86/x64)
Check C:\WINDOWS\autopatcher.log for details
A decision needs to be made whether to have a single directory or separate directories for x86/x64. Right now it is a mixed bag. I could imagine that some fixes will not even install the way the apm and directories are set up.
Edited by click-click, 14 February 2012 - 11:09 PM.
Whatacrock
15 Feb 2012
A heads up for the dotnet hotfixes for February
KB2633870 dotnet 4 security update
KB2633880 dotnet SP2 security update
KB2633870 dotnet 4 security update
KB2633880 dotnet SP2 security update
ViroMan
15 Feb 2012
Quote
The following .apm files are still in the .7z. They have been superseded and should be removed. I mentioned
this in the README.
Windows6.1-KB2478662-x64.apm
Windows6.1-KB2478662-x86.apm (Done sorry... they were removed from the scripts but, the files themselves remained)
NDP40-KB2478663-x64.apm
NDP40-KB2478663-x86.apm (Same as above)
this in the README.
Windows6.1-KB2478662-x64.apm
Windows6.1-KB2478662-x86.apm (Done sorry... they were removed from the scripts but, the files themselves remained)
NDP40-KB2478663-x64.apm
NDP40-KB2478663-x86.apm (Same as above)
Quote
A decision needs to be made whether to have a single directory or separate directories for x86/x64. Right now it is a mixed bag. I could imagine that some fixes will not even install the way the apm and directories are set up.
I already have a decision, for the new AutoPatcher, it will create a new directory for each OS you download updates for. Any download that effects more then one OS will be NTFS hard linked to the other directories. Its basically a link that makes the OS think the file is stored there even though its not. I already have other projects that use that link ability so it won't be too hard to put it in here. The problem is that windows is supposedly going to a new format soon so I wonder if it will keep that ability.
Anyways I put them both in the same directory in this case because I figured it was pointless to create more directories then was needed. They should not interfere with each other being in the same directory. If you think so... can you explain why?
Quote
A heads up for the dotnet hotfixes for February
KB2633870 dotnet 4 security update
KB2633880 dotnet SP2 security update
KB2633870 dotnet 4 security update
KB2633880 dotnet SP2 security update
Edited by ViroMan, 15 February 2012 - 06:59 PM.
ViroMan
15 Feb 2012
Done and signed... I gave up on trying to figure out why some x86 updates show in x64.
Whatacrock
17 Feb 2012
Ran apup version 1 & 2 and found the following error
***Starting Detection Routine Phase***
Missing file C:\APUP\modules\Components\__dotnet\NDP30SP2-KB982524-x64.apm_files\NDP30SP2-KB982524-x64.exe
Item Microsoft .NET Framework 3.5 SP1 and .NET Framework 2.0 SP2 Update for Windows 2003 and Windows XP for x64-based Systems is missing or its parts are not completely downloaded. Adding whole download for this item to the queue.
--Adding http://download.micr...82524-x64.exe--
And sections from version 2
Missing file C:\APUP\modules\Components\__dotnet\NDP30SP2-KB982524-x64.apm_files\NDP30SP2-KB982524-x64.exe
Item Microsoft .NET Framework 3.5 SP1 and .NET Framework 2.0 SP2 Update for Windows 2003 and Windows XP for x64-based Systems is missing or its parts are not completely downloaded. Adding whole download for this item to the queue.
--Adding http://download.micr...82524-x64.exe--
++Added To Download Queue: NDP30SP2-KB982524-x86x64exe
Just a heads up.
***Starting Detection Routine Phase***
Missing file C:\APUP\modules\Components\__dotnet\NDP30SP2-KB982524-x64.apm_files\NDP30SP2-KB982524-x64.exe
Item Microsoft .NET Framework 3.5 SP1 and .NET Framework 2.0 SP2 Update for Windows 2003 and Windows XP for x64-based Systems is missing or its parts are not completely downloaded. Adding whole download for this item to the queue.
--Adding http://download.micr...82524-x64.exe--
And sections from version 2
Missing file C:\APUP\modules\Components\__dotnet\NDP30SP2-KB982524-x64.apm_files\NDP30SP2-KB982524-x64.exe
Item Microsoft .NET Framework 3.5 SP1 and .NET Framework 2.0 SP2 Update for Windows 2003 and Windows XP for x64-based Systems is missing or its parts are not completely downloaded. Adding whole download for this item to the queue.
--Adding http://download.micr...82524-x64.exe--
++Added To Download Queue: NDP30SP2-KB982524-x86x64exe
Just a heads up.
JRosenfeld
17 Feb 2012
On a clean new apup v1, just netframework checked, get one or more failed validation.
Apup.log gives
Download Error: D:\Apup1\modules\Components\__dotnet\NDP20SP2-KB2539631-x64.apm_files\NDP20SP2-KB2539631-x86.exe
File size does NOT match. Expecting 5167464, but found 2956648!!!
Apup.log is attached (zipped)
Edited by ViroMan, 17 February 2012 - 06:15 PM.
Apup.log gives
Download Error: D:\Apup1\modules\Components\__dotnet\NDP20SP2-KB2539631-x64.apm_files\NDP20SP2-KB2539631-x86.exe
File size does NOT match. Expecting 5167464, but found 2956648!!!
Apup.log is attached (zipped)
Spoiler
Attached Files
-
apuplog.zip (4.27K)
downloads: 1
Edited by ViroMan, 17 February 2012 - 06:15 PM.
ViroMan
17 Feb 2012
examining log now.
Can you attach your AutoPatcher log so we can see everything wrong.
Edit:
Well poop. Looks like some of those problems are due to downloading the files into the wrong directory and the others are due to not using Module dir command
Edit2: incorporated Click-Click's changes now looking into fixing errors.
Edited by ViroMan, 17 February 2012 - 07:18 PM.
Can you attach your AutoPatcher log so we can see everything wrong.
Edit:
Well poop. Looks like some of those problems are due to downloading the files into the wrong directory and the others are due to not using Module dir command
Edit2: incorporated Click-Click's changes now looking into fixing errors.
Edited by ViroMan, 17 February 2012 - 07:18 PM.
ricecake
17 Feb 2012
Whatacrock, on 17 February 2012 - 01:00 PM, said:
Ran apup version 1 & 2 and found the following error
***Starting Detection Routine Phase***
Missing file C:\APUP\modules\Components\__dotnet\NDP30SP2-KB982524-x64.apm_files\NDP30SP2-KB982524-x64.exe
Item Microsoft .NET Framework 3.5 SP1 and .NET Framework 2.0 SP2 Update for Windows 2003 and Windows XP for x64-based Systems is missing or its parts are not completely downloaded. Adding whole download for this item to the queue.
--Adding http://download.micr...82524-x64.exe--
***Starting Detection Routine Phase***
Missing file C:\APUP\modules\Components\__dotnet\NDP30SP2-KB982524-x64.apm_files\NDP30SP2-KB982524-x64.exe
Item Microsoft .NET Framework 3.5 SP1 and .NET Framework 2.0 SP2 Update for Windows 2003 and Windows XP for x64-based Systems is missing or its parts are not completely downloaded. Adding whole download for this item to the queue.
--Adding http://download.micr...82524-x64.exe--
First, I've been using AP for a couple months now to update a system I have that is not on the internet, and it has worked great! Thanks for all your hard work!
Anyway, I had this error as well. I found that in modules\Components\__dotnet\NDP30SP2-KB982524-x64.apm_files, the file in there was named "NDP30SP2-KB982524-x86x64exe". I removed the "x86" and add a dot before "exe", and reran apup, and this message no longer appears in the log.
I also downloaded the file directly from the URL given in the log and verified that it is binary identical to the misnamed one in the above mentioned folder.
Hopefully this allows you to fix the script easily!
Edited by ricecake, 17 February 2012 - 08:13 PM.
ViroMan
17 Feb 2012
Thanks ricecake. I already noticed that too, I have now made the changes so that AP no longer creates an interesting log file for .NET files. I will sign an upload to server shortly.
Edit: Uploaded and signed.
Edited by ViroMan, 17 February 2012 - 09:01 PM.
Edit: Uploaded and signed.
Edited by ViroMan, 17 February 2012 - 09:01 PM.
Whatacrock
18 Feb 2012
Had a run of APUP2 today and received errors. Here are the extrracts from my logfile.
Hope this helps out, the dotnet stills shows false in the release info, therefore autopatcher is unofficial/unsupported version.
Edited by ViroMan, 18 February 2012 - 01:02 PM.
Spoiler
Hope this helps out, the dotnet stills shows false in the release info, therefore autopatcher is unofficial/unsupported version.
Edited by ViroMan, 18 February 2012 - 01:02 PM.
ViroMan
18 Feb 2012
Well I just checked... it should be fine.
Your log shows that it detected changes in the .NET and downloaded the changes. I don't see anything wrong with that we did have to modify a few things. If you run it again and it keeps downloading updates... that is a problem.
Edited by ViroMan, 18 February 2012 - 11:30 AM.
Spoiler
Your log shows that it detected changes in the .NET and downloaded the changes. I don't see anything wrong with that we did have to modify a few things. If you run it again and it keeps downloading updates... that is a problem.
Edited by ViroMan, 18 February 2012 - 11:30 AM.
Whatacrock
18 Feb 2012
Ran it again and only needed to download 9 files this time, previously was 34 files.
Attached latest log file.
Attached latest log file.
ViroMan
18 Feb 2012
hmm I can't answer for the windows7 downloads... We only modified one as far as I can remember right now, well recently anyways.
The .Net one... "missing NDP30SP2-KB982524-x64.exe" is interesting... I will look into it after I get some sleep. Don't want to go messing around with it while nodding my head.
Aside from that... wow you selected that many scripts? You must have a good connection to endure that many downloads.
The .Net one... "missing NDP30SP2-KB982524-x64.exe" is interesting... I will look into it after I get some sleep. Don't want to go messing around with it while nodding my head.
Aside from that... wow you selected that many scripts? You must have a good connection to endure that many downloads.
Black Ghost
18 Feb 2012
Is there a way to have .Net to be separated into two sections 32 bit and 64 bit in the next version? This would help people like me that are on a slower connection with a cap. Thanks.
