For quite some time I did have a warning to NOT run any of the runtimes installers that contain .NET 2.0 from anywhere other than svcpack. Then I received several reports from people that they tried it on an existing machine and it worked so... I removed the warning.
The issue is that normally, you cannot install .NET 2.0 from svcpack. In order to do this you need to make a registry change, install .NET 2.0, then change the registry back to the way it was. In theory it should all work out no matter where you install it from, but I did have problems myself; hence the warning.
I cannot say this for sure, but my guess is that if something interrupts the install process, the registry setting modified will not get changed back to it's original setting and this is what's screwing things up. I'll be sure to put the warning message back in again as there is obviously great potential for this to not work from anywhere other than svcpack.
The issue is that normally, you cannot install .NET 2.0 from svcpack. In order to do this you need to make a registry change, install .NET 2.0, then change the registry back to the way it was. In theory it should all work out no matter where you install it from, but I did have problems myself; hence the warning.
I cannot say this for sure, but my guess is that if something interrupts the install process, the registry setting modified will not get changed back to it's original setting and this is what's screwing things up. I'll be sure to put the warning message back in again as there is obviously great potential for this to not work from anywhere other than svcpack.
Is it installable from SVCPACK only due to these entries in your Install.cmd?
QUOTE ( Install.cmd )
reg delete HKLM\Software\Microsoft\PCHealth\ErrorReporting\DW /f
reg add HKLM\SYSTEM\Setup /v SystemSetupInProgress /t REG_DWORD /d 0 /f
.
.
.
reg add HKLM\SYSTEM\Setup /v SystemSetupInProgress /t REG_DWORD /d 1 /f
reg add HKLM\SYSTEM\Setup /v SystemSetupInProgress /t REG_DWORD /d 0 /f
.
.
.
reg add HKLM\SYSTEM\Setup /v SystemSetupInProgress /t REG_DWORD /d 1 /f
If so (I'm sure it is!), can't you just use sort of IF or FOR statement to set
SystemSetupInProgress to 0 if it's found to be 1? Then you set it to 1 after
installation finishes.
This routine fits installation from SVCPACK.
For the package to work from other places (other than SVCPACK), if SystemSetupInProgress
is found to be 0, let it be 0 and continue installation.
This routine fits installation from other points.
I hope you get my right 'cause, this way, your package is installable everywhere.
