Leaderboard

Add: 3072311, 3072311

Updated 3.0: KB3072303 4.0: KB3072309 @molecule all updates are integrated

Yes it will

Then nai4fle must have a different issue, or something wrong with his system, or I misunderstood. Cheers and Regards I did compact: http://forums.mydigi...l=1#post1080416 If you used Dism++ to compact, and the update did not install after that, then it might be that Dism++ is at fault. To test, you could do a build and do everything you usually do except do not use Dism++. If the update then installs correctly, then that would seem to point the finger at Dism++ and you should address this with the Dism++ developers so they could help figure out what exactly is creating the problem. You could also ask over at MDL if anyone else has had similar problems. Please report back with whatever you find out. Cheers and Regards

wow! this is a nice package and I've been struggling with building Addon bphlpt over at MSFN turned me on to it. This may require I completely rethink how I rebulid my XPsp3 x86 questions -- == edit == I can't see where 3048074 has been replaced? It's still on a recent XP POSReady thread on MSFN === Being an old dog with old habits ... (arghh ...) Can this package be converted into an Addon for RyanVMI? I see it requires VC. Why is VC required? Like the soup-guy said, that means ... no addon for me! If it's an installer only, will it install .NET over top of an existing intall, of the out of date .NETs that are packed in OnePiece's AIO Update Pack? Did you catch [post=https://support.microsoft.com/en-us/kb/2833941]KB2833941-MS13-052 for .net 1.1sp1? It was July 2013 (before XP EOL). Maybe OnePiece included it in his AIO, and he forgot to include it in his change log. It's a big one. for post-EOL are you including patches for EX Embedded and Server 2003? I've run the post-EOL exe's in manually and they work fine. But at 2-3 min each, it's over an hour ... the /integrate switch doesn't work. I haven't tested the /nobackup. Does your installer create an unstall backup, or an option to not do that? I see no reason to replace bad files with worse ones. thanks, Rick (my list of post EOL patchs -- the postEOL NPD11sp1's are for server 03 and require inf tweaking and exe hacking to install in XP NDP11SP1-XP-x86-KB2972207.exe NDP11SP1-XP-x86-KB2978114.exe NDP11SP1-XP-x86-KB3023211.exe NDP11SP1-XP-x86-KB3037572.exe the postEOL NDPs for .net 2,3,4 are for XPEmbedded or 2003sp2 but they install directly into XPsp3 NDP20SP2-KB2894843-x86.exe NDP20SP2-KB2972105-x86.exe NDP20SP2-KB2972214-x86.exe NDP20SP2-KB2978124-x86.exe NDP20SP2-KB2979574-v2-x86.exe NDP20SP2-KB3023220-x86.exe NDP20SP2-KB3035488-x86.exe NDP20SP2-KB3037577-x86.exe NDP30SP2-KB2973115-x86.exe NDP30SP2-KB3048073-v2-x86.exe NDP40-KB2894842-v2-x86.exe NDP40-KB2931365-x86.exe NDP40-KB2972106-x86.exe NDP40-KB2972215-x86.exe NDP40-KB2978125-x86.exe NDP40-KB2979575-v2-x86.exe NDP40-KB3023221-x86.exe NDP40-KB3032662-x86.exe NDP40-KB3037578-x86.exe NDP40-KB3048074-x86.exe