Your right; I just did it in a vhd-no problems at all. I guess I got my wires crossed-burfadel may have a point.
So you pre-installed dotNET4 without KB958488 and all is well? I think you can also look in the registry for the path to the mount folder, let me investigate a bit Edit: Its stored here in the registry, this way you could probably only offer the option if you detect it (maybe even automatically enter path) Code: Windows Registry Editor Version 5.00 ; GUID varies [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images\e8f0fb12-d9e7-4570-9046-764a7601d3ca] "Mount Path"="C:\\mount"
Yes; I just finished a sysprep on a vhd inwhich I installed .NET 4 complete with 958488 not installed and it went fine-no issues at all on a SP 1 image integrated by M$.
hi all i sleep now also sorry for mistakes i read all the post but maybe a have dont seen it but for what or when are the files inside folder "Integrate to installation media" needed? thanks for answer good night
Okay, got that part sorted. The whole thing is taking a bit longer than I originally expected! (all good though) The easy part is integration. The hard part is making it cover a wider range of scenarios - and I want to try and do this without the need to release 3 or 4 new versions! lol
What is the deal with the new directx june 2k10 installer? The size keeps changing for me, cant dl it to compare md5 Here is to hoping they updated it for xp pre-sp2 and dotnet4+dx managed code incompatibility
Yep, directx installer definitely updated, file version, md5 differ...even digital signature is of this year Many of the setup files inside also updated
Can't seem to get it with those hashes-downloaded 8 times, all the same size and hashes: Code: File: directx_Jun2010_redist.exe CRC-32: 0f024bfa MD4: 51f50b36139c074c3e97c240270f7b76 MD5: 4e41372e8775e8025be013480b0629b3 SHA-1: 3b90e800086f75fdb129bdb3a5d875e381c89736
The Directx redists just included new Directx extensions in what I believe were cumulative? files (the ones ending in 42, then 43 etc). If a program called for an older redist version, the Directx files from that redist were used instead. Nvidia did the same with its Physx meaning you have many copies of cumulative files. The idea is for compatibility, the downside is its very space intensive and probably wasn't the smartest way of doing things. Ideally, you would have just one updated file and if the API changed, then when calling for the older API the older API is used in the new file instead. This way is much more space friendly, and means that in most cases programs can use code that may have become more optimised. These could also be dynamically loaded, such that only the typical set of instructions are loaded and if an older API is called for, the older API set is then loaded. This is just an idea... Anyways, to the answer of Directx's updatedness, you are correct in saying Directx isn't fully optimised. The Directx redists were all about having extensions to the current code, and most likely there hasn't been a need to release a new version. At the moment, I have no doubt Microsoft are working on optimising the current code, and further utilising SSE, SSE2, SSE3, SSSE3, SSSE4x where appropriate, and also possibly enabling AVX for the new Intel 'Sandy Bridge' processors, and AMD 'Bulldozer' processor, and also the new FMA4, XOP, and CVT16 instruction sets on the AMD 'Bulldozer' if they are appropriate to use. If this was indeed being done, it would be a big overhaul and no doubt would be the basis for Directx 12 in Windows 8. (this is just speculation of course, but in many ways makes sense...) Updated files in the new redist: So in other words, only the setup files! The rest of them are the same as the old June 2010 redist.