And they're paying Akamai (or whatever content distribution network they're using) out the arse for it too I'm sure. Luckily for Microsoft, that's not their turf so they just shell out some money and it doesn't completely fill the tubes.
If they release the same version that got released via MSDN/Technet (one disc image with all versions on it), then it's 2.5GB for the x86 and 3.5GB for the x64.
Did you first try to see if you have any add-ons or toolbars installed into IE that could be causing this behavior? I've had experience with 3rd party IE add-ons (popup blockers, yahoo toolbar, etc) effectively making IE (6 and 7) "not work" and make the user very mad at Microsoft.
I've never seen explicitly this behavior, but the article is hardly backed up by any real evidence that you isolated it to IE7 and not your environment.
Applications get a very distinct message indicating a shutdown of Windows. If the application doesn't handle said message and not turn off, Windows is forced to kill the program.
If Firefox can't turn off in the required amount of time (Windows gives apps around 20 seconds or so to comply before killing them) or simply doesn't listen for the message, it would indeed be a bug.
.NET has the exact same thing. If you run your.NET code in a "sandbox" you can disable reflection permissions, thus making it impossible for a running application to reflect over your assemblies.
Just like java, however, get it out of a sandbox and you can do whatever you want to it.
Actually as far as the.NET Framework goes, you have what is called Publisher Policy. In the Global Assembly Cache (GAC) are all of your shared assemblies (dll's). To get a shared assembly in the GAC you have to "Strong Name" it and give it a version number. Any new versions of said assembly put in the GAC with the same strong name/version number will overwrite the old ones (and note that the strong name is made by take a hash of the contents of the dll, so it would be awfully hard to fake).
However, if you are a good developer and modify your version numbers on subsequent builds, when you put that assembly in the GAC you'll have two versions. Publisher Policy is an XML file compiled into a dll that allows a developer to say "don't use version 1.1.2.345, use 1.1.2.456 instead". Then all requests for the old version will be redirected to the new version instead.
Hence, if you do it correctly, there's no security risk with what you're talking about.
Well funny you should say that, as Microsoft had announced last monday that they were changing the SmartTags in WindowsXP to be off by default.
Those who know do not speak. Those who speak do not know. Keep your mouth closed.
Slashdot Mirror
The simple answer is because all the files are bigger :)
Winlogon.exe
x86: 301KB
x64: 388KB
The other answer is that there's more 1's and 0's when using 64 bit memory addresses and the like.
And they're paying Akamai (or whatever content distribution network they're using) out the arse for it too I'm sure. Luckily for Microsoft, that's not their turf so they just shell out some money and it doesn't completely fill the tubes.
If they release the same version that got released via MSDN/Technet (one disc image with all versions on it), then it's 2.5GB for the x86 and 3.5GB for the x64.
Did you first try to see if you have any add-ons or toolbars installed into IE that could be causing this behavior? I've had experience with 3rd party IE add-ons (popup blockers, yahoo toolbar, etc) effectively making IE (6 and 7) "not work" and make the user very mad at Microsoft.
I've never seen explicitly this behavior, but the article is hardly backed up by any real evidence that you isolated it to IE7 and not your environment.
Applications get a very distinct message indicating a shutdown of Windows. If the application doesn't handle said message and not turn off, Windows is forced to kill the program.
If Firefox can't turn off in the required amount of time (Windows gives apps around 20 seconds or so to comply before killing them) or simply doesn't listen for the message, it would indeed be a bug.
.NET has the exact same thing. If you run your .NET code in a "sandbox" you can disable reflection permissions, thus making it impossible for a running application to reflect over your assemblies.
Just like java, however, get it out of a sandbox and you can do whatever you want to it.
Actually as far as the .NET Framework goes, you have what is called Publisher Policy. In the Global Assembly Cache (GAC) are all of your shared assemblies (dll's). To get a shared assembly in the GAC you have to "Strong Name" it and give it a version number. Any new versions of said assembly put in the GAC with the same strong name/version number will overwrite the old ones (and note that the strong name is made by take a hash of the contents of the dll, so it would be awfully hard to fake).
However, if you are a good developer and modify your version numbers on subsequent builds, when you put that assembly in the GAC you'll have two versions. Publisher Policy is an XML file compiled into a dll that allows a developer to say "don't use version 1.1.2.345, use 1.1.2.456 instead". Then all requests for the old version will be redirected to the new version instead.
Hence, if you do it correctly, there's no security risk with what you're talking about.
Well funny you should say that, as Microsoft had announced last monday that they were changing the SmartTags in WindowsXP to be off by default.
Those who know do not speak.
Those who speak do not know.
Keep your mouth closed.