355 replies to this topic

[click-click]

Thanks. I see it now. Get some sleep. Almost 3am in LA?

[ViroMan]

2:57am right now. yep. Im tired but, not tired. lol. Mentally want to sleep but, body don't want to.

Edited by ViroMan, 19 April 2012 - 09:58 AM.

[click-click]

There's one small size issue causing AP to be Unofficial. Ugggh. too many hashes to check

[ViroMan]

indeed. Can't wait for the new system to kick in. So much easier.

Alright.. I have had enough. Im going to take some NyQuil and it will knock me out.

Edited by ViroMan, 19 April 2012 - 10:32 AM.

[click-click]

click-click, on 19 April 2012 - 10:14 AM, said:

There's one small size issue causing AP to be Unofficial. Ugggh. too many hashes to check

Problem caused locally. dotNET should be official for the rest.

Edited by click-click, 19 April 2012 - 12:45 PM.

[Whatacrock]

You are correct there click-click.....the x86 and x64 dotNET sttements state true

[Killjoy]

Hi to all. Here I am, as always with more and more questions.
Today, I'm testing slipstreamed/hotfix integrated Windows Xp with Sp3 and something bothers me.

With all hotfixes, I've slipstreamed .NET addon packs: 1.1 with its hotfixes and 3.5 sp1 which contains all hotfixes AND .NET 3.0 and 2.0.

According to Microsoft Update site, there are no new OR available hotfixes for none of those .NETs.
SO, those update packs/addon pack of .NET are pretty OK.


BUT, where is my problem??? WITH apup.

I've downloaded x86 package of .NET and he reports that more hotfixes are available.

Here they are.







I'm Sorry If I've posted question on wrong part of Forum, please move it to the right place.

[click-click]

Did you slipstream dotNET 1.1 with those security fixes?
http://technet.micro...lletin/ms11-100
http://technet.micro...lletin/ms12-025

The other updates are optional and may not be offered by Windows Update. If you want to know more about a specific fix, select the item and in the Item Description, select More Info on the far right.

How did you slipstream the packs?

Edited by click-click, 20 April 2012 - 10:34 PM.

[click-click]

@Killjoy

The detections for the two mentioned security updates are incorrect and will always show as not installed. This will be corrected in the next update.

KB925168 was superseded by KB2656353 and will be removed from APUP.

Edited by click-click, 21 April 2012 - 12:00 AM.

[Killjoy]

click-click, on 20 April 2012 - 10:17 PM, said:

Did you slipstream dotNET 1.1 with those security fixes?
http://technet.micro...lletin/ms11-100
http://technet.micro...lletin/ms12-025

The other updates are optional and may not be offered by Windows Update. If you want to know more about a specific fix, select the item and in the Item Description, select More Info on the far right.

How did you slipstream the packs?

I guess Microsoft HAS to offer them one way or another.
How did I slipstream them? Through nLite.
Those are Nonno Fabios addons. Every one of them is OK according to many opinions and experiences.
Source: WinCert's Forum

click-click, on 20 April 2012 - 11:44 PM, said:

@Killjoy

The detections for the two mentioned security updates are incorrect and will always show as not installed. This will be corrected in the next update.

KB925168 was superseded by KB2656353 and will be removed from APUP.

Great!!! Can't wait.

Edited by Killjoy, 21 April 2012 - 12:18 AM.

[Killjoy]

P.S. Those are CAB archives. I didn't look into them. That guy says that those are up-to-date.
According to WU/MU, HE is right.

I think that the same problem lies within .NET 4.
I'll try later to install .NET 4 on tested Windows. .NET 4 with offered fixes from Microsoft.

I'll post results later.



P.S. Too bad that .NET 3.5 sp1 (almost 300MB) can't be separated into x86 and x64 releases. That stupid app is too big.

Edited by Killjoy, 21 April 2012 - 12:24 AM.

[click-click]

dotNET Addons updated 21 Apr 2012 :

fixed dotNET 1.1 detections and removed KB925168

>> I think that the same problem lies within .NET 4.

I'm not aware of any problems with dotNET 4

>> P.S. Too bad that .NET 3.5 sp1 (almost 300MB) can't be separated into x86 and x64 releases. That stupid app is too big.

I'm afraid you'll have to talk to Microsoft to have them split that one.

Edited by click-click, 21 April 2012 - 10:49 AM.

[Whatacrock]

Extracted to a temp folder the .Net3.5SP1 and found the following within the archive.

These are contained in folder named wcu which contains folder named dotNetFramework and the files contained within this one
and the manifest file

dotNetFX20 47.6Mb 18 files

dotNetFX30 46.8Mb 26 files in 2 folders(x86 and x64)

dotNetFX35 31.5 Mb 3 files in 3 folders(ia64, x64 and x86)

dotNetMSP 111Mb 12 files in 3 folders(ia64 ,x64 and x86)

Tools 528Kb 3 files

dotNetFx35setup.exe 2.82Mb

As they say curiousity killed the cat!!!

[Killjoy]

click-click, on 21 April 2012 - 10:38 AM, said:

dotNET Addons updated 21 Apr 2012 :

fixed dotNET 1.1 detections and removed KB925168

That's cool! Thanks.

>> I think that the same problem lies within .NET 4.

click-click, on 21 April 2012 - 10:38 AM, said:

I'm not aware of any problems with dotNET 4

I'll install .NET 4 through MS update site and I'll show you.

click-click, on 21 April 2012 - 10:38 AM, said:

I'm afraid you'll have to talk to Microsoft to have them split that one.

I've splitted that one and packed it into installation. I'll try to do that again and put it here for download and testing.
I mean for you to test it.

[click-click]

Sorry, but we are not in the business of repackaging Microsoft's installers. If there is no official KB link, we won't be offering or using it.

[ViroMan]

indeed we cannot store any of there updates on the site in any form. Only make you download from their sites.

[Killjoy]

Ah! Nevermind.
Do you want to test that "repacked" x86 edition of .NET 3.5 SP1???

Edited by Killjoy, 23 April 2012 - 07:42 PM.

[click-click]

Killjoy, on 23 April 2012 - 07:35 PM, said:

Ah! Nevermind.
Do you want to test that "repacked" x86 edition of .NET 3.5 SP1???

Thanks for the offer, but I already have a switchless installer that I use on my systems.
Were you able to find your problem with dotNET 4?

[Whatacrock]

click-click is absolutely correct..there are no problems with the .Net 4 updates...they all display as blue on both my vista x86 and XP x86 machines.
My Vista x86 updated entirely by Windows Update and the XP machine partly by Autopatcher and the rest of it by Windows Update.
Unable to run xp X64 at the moment to comment for the 64 bit stuff.

[eherz]

Shouldn't KB982167 be removed since it was superseded by KB2418241?