About the error messages arisen when showing the install window, they are simply the result of the execution of pending assemblies compiling tasks without waiting to idle state. That's how the installer is made, ask MS, there's some entries in the installer pointing to void, maybe there's some reason for it, I don't know. But they don't make any harm and don't generate errors in the event viewer nor the install/unsintall logs.
Full Version: Silent .NET Maker synthesized 20091105 - W2K/XP/2K3 x86
mooms, are you sure you were not playing with the addons? I'm lost, CA_KB928416FIX2 is only supposed to execute on uninstall because of an execution condition. And I didn't get those results in the past (I'm not using a non-english windows to test conditions like this now). By the way you can test with this:Uncompress the addon to a folder, then the installer under SVCPACK folder, and in the remaining forder substitute NETWUFIXES.MST with above one. This new file doesn't change anything but slightly modify the execution conditions about detecting install/uninstall process in a equivalent way, for them to be more restrictive. Last, install through INSTALL.CMD and tell me whether event viewer keeps showing that error.
About the error messages arisen when showing the install window, they are simply the result of the execution of pending assemblies compiling tasks without waiting to idle state. That's how the installer is made, ask MS, there's some entries in the installer pointing to void, maybe there's some reason for it, I don't know. But they don't make any harm and don't generate errors in the event viewer nor the install/unsintall logs.
About the error messages arisen when showing the install window, they are simply the result of the execution of pending assemblies compiling tasks without waiting to idle state. That's how the installer is made, ask MS, there's some entries in the installer pointing to void, maybe there's some reason for it, I don't know. But they don't make any harm and don't generate errors in the event viewer nor the install/unsintall logs.
ah, thanks for this tool, trying the installers with nlite right now
hi, me confirmed Error reported by Mooms :
Compiling assembly C:\Program Files\Reference Assemblies\Micros
\v3.0\System.Runtime.Serialization.dll ...
Warning: Failed to load method token 69000401 from profile data.
Warning: Failed to load method token 69000402 from profile data.
Warning: Failed to load method token 69000403 from profile data.
Warning: Failed to load method token 69000404 from profile data.
Warning: Failed to load method token 69000401 from profile data.
Warning: Failed to load method token 69000402 from profile data.
Warning: Failed to load method token 69000403 from profile data.
Warning: Failed to load method token 69000404 from profile data.
Warning: Failed to load method token 69000401 from profile data.
Warning: Failed to load method token 69000402 from profile data.
Warning: Failed to load method token 69000403 from profile data.
Warning: Failed to load method token 69000404 from profile data.
C:\DOCUME~1\VIRTUA~1\LOCALS~1\Temp\7zS3.tmp>FOR /F "DELIMS=[]" %I IN (DNFWIN5.TX
T) DO REG DELETE "%I" /f
Le système ne peut trouver le fichier DNFWIN5.TXT
sorry me use translator , no speak English
EDit : me sepparate installer error repported in Framework 3.0 SP2
C:\NET TEST 2>XCOPY/DY DNF30\SYS32\rgb9rast_2.dll C:\WINDOWS\system32
0 fichier(s) copié(s)
C:\NET TEST 2>FOR /F "DELIMS=[]" %I IN (DNFWIN5.TXT) DO REG DELETE "%I" /f
Le système ne peut trouver le fichier DNFWIN5.TXT.
Warning: Failed to load method token 69000401 from profile data.
Warning: Failed to load method token 69000402 from profile data.
Warning: Failed to load method token 69000403 from profile data.
Warning: Failed to load method token 69000404 from profile data.
Warning: Failed to load method token 69000401 from profile data.
Warning: Failed to load method token 69000402 from profile data.
Warning: Failed to load method token 69000403 from profile data.
Warning: Failed to load method token 69000404 from profile data.
Warning: Failed to load method token 69000401 from profile data.
Warning: Failed to load method token 69000402 from profile data.
Warning: Failed to load method token 69000403 from profile data.
Warning: Failed to load method token 69000404 from profile data.
fichier spécifié est introuvable. while compiling method WasHttpHandlersInstall
Component.Install
Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Le
fichier spécifié est introuvable. while compiling method WasHttpHandlersInstall
Component.CopyHandlerAttributes
Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Le
fichier spécifié est introuvable. while compiling method WasHttpHandlersInstall
Component.AddSvcHandlers
Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Le
fichier spécifié est introuvable. while compiling method WasHttpHandlersInstall
Component.Uninstall
Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Le
fichier spécifié est introuvable. while compiling method WasHttpHandlersInstall
Component.VerifyInstall
Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Le
fichier spécifié est introuvable. while compiling method WasHttpModulesInstallC
omponent.get_InstalledVersions
Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Le
fichier spécifié est introuvable. while compiling method WasHttpModulesInstallC
omponent.get_IsInstalled
Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Le
fichier spécifié est introuvable. while compiling method WasHttpModulesInstallC
omponent.GetHttpModuleFromCollection
Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Le
fichier spécifié est introuvable. while compiling method WasHttpModulesInstallC
omponent.Install
Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Le
fichier spécifié est introuvable. while compiling method WasHttpModulesInstallC
omponent.Uninstall
Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Le
fichier spécifié est introuvable. while compiling method WasHttpModulesInstallC
omponent.VerifyInstall
ServiceModelReg, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a
Framework 3.5 SP1 :
Failed to load dependency Microsoft.Web.Administration of assembly ServiceModelR
eg, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a because of
the following error : Le fichier spécifié est introuvable. (Exception from HRES
ULT: 0x80070002)
Warning: Failed to load method token 69000029 from profile data.
Warning: Failed to load method token 6900002a from profile data.
Warning: Failed to load method token 6900002e from profile data.
Warning: Failed to load method token 69000029 from profile data.
Warning: Failed to load method token 6900002a from profile data.
Warning: Failed to load method token 6900002e from profile data.
Warning: Failed to load method token 69000029 from profile data.
Warning: Failed to load method token 6900002a from profile data.
Warning: Failed to load method token 6900002e from profile data.
Compiling assembly C:\Program Files\Reference Assemblies\Micros
\v3.0\System.Runtime.Serialization.dll ...
Warning: Failed to load method token 69000401 from profile data.
Warning: Failed to load method token 69000402 from profile data.
Warning: Failed to load method token 69000403 from profile data.
Warning: Failed to load method token 69000404 from profile data.
Warning: Failed to load method token 69000401 from profile data.
Warning: Failed to load method token 69000402 from profile data.
Warning: Failed to load method token 69000403 from profile data.
Warning: Failed to load method token 69000404 from profile data.
Warning: Failed to load method token 69000401 from profile data.
Warning: Failed to load method token 69000402 from profile data.
Warning: Failed to load method token 69000403 from profile data.
Warning: Failed to load method token 69000404 from profile data.
C:\DOCUME~1\VIRTUA~1\LOCALS~1\Temp\7zS3.tmp>FOR /F "DELIMS=[]" %I IN (DNFWIN5.TX
T) DO REG DELETE "%I" /f
Le système ne peut trouver le fichier DNFWIN5.TXT
sorry me use translator , no speak English
EDit : me sepparate installer error repported in Framework 3.0 SP2
C:\NET TEST 2>XCOPY/DY DNF30\SYS32\rgb9rast_2.dll C:\WINDOWS\system32
0 fichier(s) copié(s)
C:\NET TEST 2>FOR /F "DELIMS=[]" %I IN (DNFWIN5.TXT) DO REG DELETE "%I" /f
Le système ne peut trouver le fichier DNFWIN5.TXT.
Warning: Failed to load method token 69000401 from profile data.
Warning: Failed to load method token 69000402 from profile data.
Warning: Failed to load method token 69000403 from profile data.
Warning: Failed to load method token 69000404 from profile data.
Warning: Failed to load method token 69000401 from profile data.
Warning: Failed to load method token 69000402 from profile data.
Warning: Failed to load method token 69000403 from profile data.
Warning: Failed to load method token 69000404 from profile data.
Warning: Failed to load method token 69000401 from profile data.
Warning: Failed to load method token 69000402 from profile data.
Warning: Failed to load method token 69000403 from profile data.
Warning: Failed to load method token 69000404 from profile data.
fichier spécifié est introuvable. while compiling method WasHttpHandlersInstall
Component.Install
Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Le
fichier spécifié est introuvable. while compiling method WasHttpHandlersInstall
Component.CopyHandlerAttributes
Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Le
fichier spécifié est introuvable. while compiling method WasHttpHandlersInstall
Component.AddSvcHandlers
Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Le
fichier spécifié est introuvable. while compiling method WasHttpHandlersInstall
Component.Uninstall
Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Le
fichier spécifié est introuvable. while compiling method WasHttpHandlersInstall
Component.VerifyInstall
Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Le
fichier spécifié est introuvable. while compiling method WasHttpModulesInstallC
omponent.get_InstalledVersions
Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Le
fichier spécifié est introuvable. while compiling method WasHttpModulesInstallC
omponent.get_IsInstalled
Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Le
fichier spécifié est introuvable. while compiling method WasHttpModulesInstallC
omponent.GetHttpModuleFromCollection
Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Le
fichier spécifié est introuvable. while compiling method WasHttpModulesInstallC
omponent.Install
Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Le
fichier spécifié est introuvable. while compiling method WasHttpModulesInstallC
omponent.Uninstall
Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Le
fichier spécifié est introuvable. while compiling method WasHttpModulesInstallC
omponent.VerifyInstall
ServiceModelReg, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a
Framework 3.5 SP1 :
Failed to load dependency Microsoft.Web.Administration of assembly ServiceModelR
eg, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a because of
the following error : Le fichier spécifié est introuvable. (Exception from HRES
ULT: 0x80070002)
Warning: Failed to load method token 69000029 from profile data.
Warning: Failed to load method token 6900002a from profile data.
Warning: Failed to load method token 6900002e from profile data.
Warning: Failed to load method token 69000029 from profile data.
Warning: Failed to load method token 6900002a from profile data.
Warning: Failed to load method token 6900002e from profile data.
Warning: Failed to load method token 69000029 from profile data.
Warning: Failed to load method token 6900002a from profile data.
Warning: Failed to load method token 6900002e from profile data.
As I said above that's the process of compiling assemblies, the only difference is that you are now seeing what the process does, it's the result of ngen.exe /executequeueditems command execution for processing the queue inmediately, not waiting to idle state. There's nothing there a vanilla install process wouldn't do, except to avoid waiting.
The installer assemblies tables points to some void entries causing that errors, you're not supposed to see them, so I don't know if there's a reason for them, but sure it doesn't make any harm.
The installer assemblies tables points to some void entries causing that errors, you're not supposed to see them, so I don't know if there's a reason for them, but sure it doesn't make any harm.
and : If i try to uninstall the French language pack for .net3.0sp2 (installed with an addon, at T-13) i have an error message about some script, the uninstall continue anyway
La description pour l'ID d'événement ( 11720 ) dans la source (MsiInstaller) est introuvable. L'ordinateur local n'a peut-être pas les informations de Registre ou les librairies requises pour afficher les messages émanant d'un ordinateur distant. Vous pourrez peut-être utiliser l'option /AUXSOURCE= pour récupérer cette description. Reportez-vous aux rubriques Aide et support pour plus de détails. Les informations suivantes font partie de l'événement : Produit : Microsoft .NET Framework 3.0 Service Pack 2 Language Pack - FRA -- Erreur 1720. Problème détecté dans ce package d’installation Windows. Un script requis pour cette installation n’a pas pu être lancé. Contactez votre support technique ou l’éditeur du package. Action personnalisée CA_KB928416FIX2, erreur de script -2147024894, WshShell.RegDelete : Impossible de supprimer la clé de Registre "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0\Setup\Windows Presentation Foundation\fr\". ligne 51, colonne 1, ; (NULL); (NULL); (NULL); (NULL); ; .
La description pour l'ID d'événement ( 11720 ) dans la source (MsiInstaller) est introuvable. L'ordinateur local n'a peut-être pas les informations de Registre ou les librairies requises pour afficher les messages émanant d'un ordinateur distant. Vous pourrez peut-être utiliser l'option /AUXSOURCE= pour récupérer cette description. Reportez-vous aux rubriques Aide et support pour plus de détails. Les informations suivantes font partie de l'événement : Produit : Microsoft .NET Framework 3.0 Service Pack 2 Language Pack - FRA -- Erreur 1720. Problème détecté dans ce package d’installation Windows. Un script requis pour cette installation n’a pas pu être lancé. Contactez votre support technique ou l’éditeur du package. Action personnalisée CA_KB928416FIX2, erreur de script -2147024894, WshShell.RegDelete : Impossible de supprimer la clé de Registre "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0\Setup\Windows Presentation Foundation\fr\". ligne 51, colonne 1, ; (NULL); (NULL); (NULL); (NULL); ; .
QUOTE (strel @ Jul 20 2009, 03:58 AM) 
mooms, are you sure you were not playing with the addons? I'm lost, CA_KB928416FIX2 is only supposed to execute on uninstall because of an execution condition. And I didn't get those results in the past (I'm not using a non-english windows to test conditions like this now). By the way you can test with this:Click to view attachmentUncompress the addon to a folder, then the installer under SVCPACK folder, and in the remaining forder substitute NETWUFIXES.MST with above one. This new file doesn't change anything but slightly modify the execution conditions about detecting install/uninstall process in a equivalent way, for them to be more restrictive. Last, install through INSTALL.CMD and tell me whether event viewer keeps showing that error.
About the error messages arisen when showing the install window, they are simply the result of the execution of pending assemblies compiling tasks without waiting to idle state. Ask MS.
About the error messages arisen when showing the install window, they are simply the result of the execution of pending assemblies compiling tasks without waiting to idle state. Ask MS.
Strel,
I have forgotten to say that i have replaced four files with newer ones : (KB959206 )
QUOTE
unires.dll
unidrv.dll
unidrvui.dll
unidrv.hlp
unidrv.dll
unidrvui.dll
unidrv.hlp
It's the only modification to the installer created by SNMsynth.
Tried with the new NETWUFIXES.mst, installed on live system, same error showing when uninstalling .net30 langpack FRA
the copy of the error in event viewer:
QUOTE
La description pour l'ID d'événement ( 11720 ) dans la source (MsiInstaller) est introuvable. L'ordinateur local n'a peut-être pas les informations de Registre ou les librairies requises pour afficher les messages émanant d'un ordinateur distant. Vous pourrez peut-être utiliser l'option /AUXSOURCE= pour récupérer cette description. Reportez-vous aux rubriques Aide et support pour plus de détails. Les informations suivantes font partie de l'événement : Produit : Microsoft .NET Framework 3.0 Service Pack 2 Language Pack - FRA -- Erreur 1720. Problème détecté dans ce package d’installation Windows. Un script requis pour cette installation n’a pas pu être lancé. Contactez votre support technique ou l’éditeur du package. Action personnalisée CA_KB928416FIX2, erreur de script -2147024894, WshShell.RegDelete : Impossible de supprimer la clé de Registre "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0\Setup\Windows Presentation Foundation\fr\". ligne 51, colonne 1, ; (NULL); (NULL); (NULL); (NULL); ; .
Edit: now the error is also showing when trying to uninstall langpack for .net2
QUOTE
La description pour l'ID d'événement ( 11720 ) dans la source (MsiInstaller) est introuvable. L'ordinateur local n'a peut-être pas les informations de Registre ou les librairies requises pour afficher les messages émanant d'un ordinateur distant. Vous pourrez peut-être utiliser l'option /AUXSOURCE= pour récupérer cette description. Reportez-vous aux rubriques Aide et support pour plus de détails. Les informations suivantes font partie de l'événement : Produit : Microsoft .NET Framework 2.0 Service Pack 2 Language Pack - FRA -- Error 1720.Un problème s'est produit sur ce package Windows Installer. Un script nécessaire pour que cette installation puisse se terminer n'a pas pu être exécuté. Contactez votre service de support ou le distributeur du package. Action personnalisé CA_KB951847FIX4a, erreur de script -2147024894, WshShell.RegDelete: Impossible de supprimer la clé de Registre "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5\1036\". ligne 2, colonne 1, ; (NULL); (NULL); (NULL); (NULL); ;
and langpack for .net3.5
QUOTE
La description pour l'ID d'événement ( 11720 ) dans la source (MsiInstaller) est introuvable. L'ordinateur local n'a peut-être pas les informations de Registre ou les librairies requises pour afficher les messages émanant d'un ordinateur distant. Vous pourrez peut-être utiliser l'option /AUXSOURCE= pour récupérer cette description. Reportez-vous aux rubriques Aide et support pour plus de détails. Les informations suivantes font partie de l'événement : Produit : Microsoft .NET Framework 3.5 Language Pack SP1 - fra -- Erreur 1720. Problème détecté dans ce package d’installation Windows. Un script requis pour cette installation n’a pas pu être lancé. Contactez votre support technique ou l’éditeur du package. Action personnalisée CA_KB951847FIX4c, erreur de script -2147024894, WshShell.RegDelete : Impossible de supprimer la clé de Registre "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5\1036\". ligne 2, colonne 1, ; (NULL); (NULL); (NULL); (NULL); ; .
I have one question: do the language pack is needed if we only use and don't make .net apps ?
That late...
As long as you don't mind receiving dialogs in english, it's optional.
I'm testing now the next update...
As long as you don't mind receiving dialogs in english, it's optional.
I'm testing now the next update...
Hi,
I noticed KB886903 for .NET 1.1 SP1, which is from 2005
RogueSpear includes it in its packs : http://www.doitrightconsulting.net/forum/viewtopic.php?t=132
and here is the Microsoft page : http://www.microsoft.com/downloads/details...BC-1A0DC2273FF9
It seems .NET Maker doesn't support it, is it simply a miss? In this case, it would be great to add it
Cheers
I noticed KB886903 for .NET 1.1 SP1, which is from 2005
RogueSpear includes it in its packs : http://www.doitrightconsulting.net/forum/viewtopic.php?t=132
and here is the Microsoft page : http://www.microsoft.com/downloads/details...BC-1A0DC2273FF9
It seems .NET Maker doesn't support it, is it simply a miss? In this case, it would be great to add it
Cheers
Didn't know about its existance since it is not pushed by update system and it isn't a restricted hotfix, but I bet you can apply it with actual, SNMsynth.
Thx.
Thx.
KB886903 was replaced KB928366 as described in Security Bulletin MS07-040.
New update issued!
All previous bugs fixed and added new features. I've tested it deeply but maybe something is missed, let us know.
Enjoy!
All previous bugs fixed and added new features. I've tested it deeply but maybe something is missed, let us know.
Enjoy!
hi
new SNMsynth no working.
me decompressing : DNF20SP230SP235SP1.exe
error create temp file in INSTALL.CMD
Edited SNMsynth.cmd change %temp% by %%temp%%, installed
dotnetfx35langpack_x86fr.exe no detected
new SNMsynth no working.
me decompressing : DNF20SP230SP235SP1.exe
error create temp file in INSTALL.CMD
Edited SNMsynth.cmd change %temp% by %%temp%%, installed
dotnetfx35langpack_x86fr.exe no detected
I also have problem with the new _SNMsynth.
I can make the package but it won't install.
Am I doing something wrong or does the new version has a problem?
Below are my settings in _SNMsynth.ini and a snapshot with the files i use
Plz help!
Click to view attachment
I can make the package but it won't install.
Am I doing something wrong or does the new version has a problem?
Below are my settings in _SNMsynth.ini and a snapshot with the files i use
Plz help!
CODE
PROCESS_DNF1=YES
PROCESS_DNF2=
PROCESS_DNF35_DNF2=YES
PROCESS_DNF35_DNF3=YES
PROCESS_DNF35_DNF35=YES
PROCESS_DNF3_RGBRAST=YES
PROCESS_DNF3_WINIMAGING=YES
PROCESS_DNF3_MSXML6=YES
PROCESS_DNF3_XMLPSSC=YES
DNF_FF_ADDON=YES
PROCESS_LNG_DNF1=
PROCESS_LNG_DNF2=
PROCESS_LNG_DNF35_DNF2=
PROCESS_LNG_DNF35_DNF3=
PROCESS_LNG_DNF35_DNF35=
ADDON=
MERGE_FRAMEWORKS=YES
SILENT=YES
COMPRESSION_RATIO=LOW
WINXP=YES
PROCESS_DNF2=
PROCESS_DNF35_DNF2=YES
PROCESS_DNF35_DNF3=YES
PROCESS_DNF35_DNF35=YES
PROCESS_DNF3_RGBRAST=YES
PROCESS_DNF3_WINIMAGING=YES
PROCESS_DNF3_MSXML6=YES
PROCESS_DNF3_XMLPSSC=YES
DNF_FF_ADDON=YES
PROCESS_LNG_DNF1=
PROCESS_LNG_DNF2=
PROCESS_LNG_DNF35_DNF2=
PROCESS_LNG_DNF35_DNF3=
PROCESS_LNG_DNF35_DNF35=
ADDON=
MERGE_FRAMEWORKS=YES
SILENT=YES
COMPRESSION_RATIO=LOW
WINXP=YES
Click to view attachment
2 bruno32600
You're right, in addition to the %'s, one parenthesis was missed.
Thx a lot.
2 peoman
1. I discovered a bug detecting the OS setting from _SNMsynth.ini, but in your case is not affecting at all.
2. I've made my test and the installers work perfectly with the same conditions you posted.I think you have not checked Task Manager to see if there was installations running because the installer is absolutely silent and takes some time to finish. Check your Add/Remove Programs too, and refresh from time to time, you'll see the frameworks appearing as they get installed.
Thx a lot.
EDIT: Sorry forgot to mention I did the test after fix bugs bruno pointed. That's what's failing for you too.
New update released!
Enjoy!
You're right, in addition to the %'s, one parenthesis was missed.
Thx a lot.
2 peoman
1. I discovered a bug detecting the OS setting from _SNMsynth.ini, but in your case is not affecting at all.
2. I've made my test and the installers work perfectly with the same conditions you posted.
Thx a lot.
EDIT: Sorry forgot to mention I did the test after fix bugs bruno pointed. That's what's failing for you too.
New update released!
Enjoy!
hi
dotnetfx35langpack_x86fr.exe detection fixed tks
me integrate at @T13 repport multi erreur dabs Observateur d'événements.
http://www.fileden.com/files/2009/5/2/2426...application.txt
Edit : when msxml6-KB954459-fra-x86.exe no integrated error disappeared .
dotnetfx35langpack_x86fr.exe detection fixed tks
me integrate at @T13 repport multi erreur dabs Observateur d'événements.
http://www.fileden.com/files/2009/5/2/2426...application.txt
Edit : when msxml6-KB954459-fra-x86.exe no integrated error disappeared .
Yes, i could see it from the Task Manager but not in Add/Remove Programs.
Anyway, with the new 20090820_SNMsynth, i was able to create a working package!
Thanks for your time.
Anyway, with the new 20090820_SNMsynth, i was able to create a working package!
Thanks for your time.
QUOTE (bruno32600 @ Aug 20 2009, 09:17 AM)
me integrate at @T13 repport multi erreur dabs Observateur d'événements.
http://www.fileden.com/files/2009/5/2/2426...application.txt
Edit : when dotnetfx35langpack_x86fr.exe no integrated error disappeared .
http://www.fileden.com/files/2009/5/2/2426...application.txt
Edit : when dotnetfx35langpack_x86fr.exe no integrated error disappeared .
Seems like the same error in the same second. The script avoid waiting to idle time to execute the process of compiling assemblies, what the installers normally do. That's what this process does, including errors, is not an issue of executing at T-13 you'll get these errors at any time of setup and out of setup. Don't worry, doesn't harm install, and in case something was missed, compiling will complete later in idle time. And you can always install updated XML out of the .NET install.
2 all
I updated the realease version in the header of the script without renewing version. Those of you who downloaded first can change it manually to 20090820. No more changes.
I found incomplete checkings of 2.0 SP2 hotfixes when the source is the 3.5 SP1 package.
If you were not applying KB958481 you may have been getting problems with KB951847 being pushed by update system, without advetence during the building process.
You may have got too dialog windows errors if you were applying the latest 2.0 SP2 restricted hotfixes.
Now it's fixed in the released new update.
Enjoy!
If you were not applying KB958481 you may have been getting problems with KB951847 being pushed by update system, without advetence during the building process.
You may have got too dialog windows errors if you were applying the latest 2.0 SP2 restricted hotfixes.
Now it's fixed in the released new update.
Enjoy!
ECHO>>INSTALL3.CMD START/WAIT DNF30\Netfx30a_x86.msi /l*v ""%%%TEMP%%%\NETFX30.log" ADDEPLOY=1 ARPNOMODIFY=0 ARPNOREPAIR=0 /%%VERBOSITY%% /norestart
IF DEFINED NOKB951847FIX (ECHO>>INSTALL3.CMD START/WAIT DNF30\Netfx30a_x86.msi /l*v "%%%TEMP%%%\NETFX30.log" ADDEPLOY=1 ARPNOMODIFY=0 ARPNOREPAIR=0 /%%VERBOSITY%% /norestart
%%%temp%%% is errors ??
""%%%TEMP%%%\NETFX30.log" : "" is errors ??
sorry me bad speak english
IF DEFINED NOKB951847FIX (ECHO>>INSTALL3.CMD START/WAIT DNF30\Netfx30a_x86.msi /l*v "%%%TEMP%%%\NETFX30.log" ADDEPLOY=1 ARPNOMODIFY=0 ARPNOREPAIR=0 /%%VERBOSITY%% /norestart
%%%temp%%% is errors ??
""%%%TEMP%%%\NETFX30.log" : "" is errors ??
sorry me bad speak english
An error fixing the error, not my day, douh!
Fixed now.
Fixed now.
no fixed : ""%%TEMP%%\NETFX30.log"
fixed : "%%TEMP%%\NETFX30.log"
version 20090821c ?
sorry lol
fixed : "%%TEMP%%\NETFX30.log"
version 20090821c ?
sorry lol
20something letters in the alphabet, hope I don't have to waste all. Doh!
=)
Fixed now.
=)
Fixed now.
Hi strel. First I'd like to thank you for making this script. I've used previous versions without problems (including the install I'm typing this on).
But with the latest one I'm getting this error:
My _SNMSynth.ini file looks like this:
Cheers!
But with the latest one I'm getting this error:
My _SNMSynth.ini file looks like this:
CODE
PROCESS_DNF1=
PROCESS_DNF2=
PROCESS_DNF35_DNF2=YES
PROCESS_DNF35_DNF3=YES
PROCESS_DNF35_DNF35=YES
PROCESS_DNF3_RGBRAST=YES
PROCESS_DNF3_WINIMAGING=YES
PROCESS_DNF3_MSXML6=YES
PROCESS_DNF3_XMLPSSC=YES
DNF_FF_ADDON=YES
PROCESS_LNG_DNF1=
PROCESS_LNG_DNF2=
PROCESS_LNG_DNF35_DNF2=
PROCESS_LNG_DNF35_DNF3=
PROCESS_LNG_DNF35_DNF35=
ADDON=YES
MERGE_FRAMEWORKS=YES
SILENT=
COMPRESSION_RATIO=
WINXP=YES
PROCESS_DNF2=
PROCESS_DNF35_DNF2=YES
PROCESS_DNF35_DNF3=YES
PROCESS_DNF35_DNF35=YES
PROCESS_DNF3_RGBRAST=YES
PROCESS_DNF3_WINIMAGING=YES
PROCESS_DNF3_MSXML6=YES
PROCESS_DNF3_XMLPSSC=YES
DNF_FF_ADDON=YES
PROCESS_LNG_DNF1=
PROCESS_LNG_DNF2=
PROCESS_LNG_DNF35_DNF2=
PROCESS_LNG_DNF35_DNF3=
PROCESS_LNG_DNF35_DNF35=
ADDON=YES
MERGE_FRAMEWORKS=YES
SILENT=
COMPRESSION_RATIO=
WINXP=YES
Cheers!
There's a bug processing 1.1 and 2.0 SP2 hotfixes, write KB instead of kb in the filename and you won't get this error. I'll release the update soon.
Cheers.
Cheers.
Thanks, that worked a treat. Keep up the great work.
Hi,strel 
I avoid to install NET Framework 3.5 with the following registry.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5\Setup]
"BlockSP"=dword:00000001
But,DNF20SP2.exe describes unnecessary registries.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5]
"SP"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5\1041]
"SP"=dword:00000001
These registries cause appearance KB963707 on WUD.
I avoid to install NET Framework 3.5 with the following registry.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5\Setup]
"BlockSP"=dword:00000001
But,DNF20SP2.exe describes unnecessary registries.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5]
"SP"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5\1041]
"SP"=dword:00000001
These registries cause appearance KB963707 on WUD.
Hi karmatron.
I didn't understand you first time, you mean I can substitute second and third regkeys with first one. Is it that? I think it is not enough to avoid KB951847 as the fix included do in case you are not having all 2.0 SP2+3.0 SP2+3.5 SP1 installed, but anyway I'll give it a go. This fix makes win/ms update (not WUD that's another useful piece of software) believe the whole set are installed, and this should cause update system to push KB963707 if another fix avoiding this were not being applied.
And thx for your interest.
I didn't understand you first time, you mean I can substitute second and third regkeys with first one. Is it that? I think it is not enough to avoid KB951847 as the fix included do in case you are not having all 2.0 SP2+3.0 SP2+3.5 SP1 installed, but anyway I'll give it a go. This fix makes win/ms update (not WUD that's another useful piece of software) believe the whole set are installed, and this should cause update system to push KB963707 if another fix avoiding this were not being applied.
And thx for your interest.
Hi,strel.
I'm sorry in the insufficient explanation.
First reg key refers to
How to temporarily block the installation of the .NET Framework 3.5 Service Pack 1
http://support.microsoft.com/kb/959211/
I integrated only NET2.0SP2 nLite addon (DNF20SP2ja.7z) into Windows XP SP3 disc.
And I avoid to install NET3.5 on WUD with the first reg key.
Because, I do not want to install NET3.5 if it is unnecessary.
After Installation of Windows with the integrated disc, WUD pushes KB963707 there is no NET3.5SP1.
If remove the second and third reg key, KB963707 disappears on WUD.
I'm sorry in the insufficient explanation.
First reg key refers to
How to temporarily block the installation of the .NET Framework 3.5 Service Pack 1
http://support.microsoft.com/kb/959211/
I integrated only NET2.0SP2 nLite addon (DNF20SP2ja.7z) into Windows XP SP3 disc.
And I avoid to install NET3.5 on WUD with the first reg key.
Because, I do not want to install NET3.5 if it is unnecessary.
After Installation of Windows with the integrated disc, WUD pushes KB963707 there is no NET3.5SP1.
If remove the second and third reg key, KB963707 disappears on WUD.
karmatron, first I didn't know this article, I'll see what can I do with it. Thx.
But SNMsynth's add-on you used (if made with latest version of the script) include a fix to avoid win/ms update to push KB951847, and this update is what it is going to install 3.0 SP2+3.5 SP1+regular hotfixes for both (and for 2.0 SP2 if you didn't apply them)+langpacks for both, in your case. This fix makes win/ms update think the previous set is installed.
If you apply that "BlockSP" reg key, you're applying 2 different fixes to avoid intalling 3.5 SP1 through KB951847 at the same time. And I suppose this should be the cause KB963707 is being pushed, because there's a fix included in that add-on too, for making win/ms update think KB963707 is installed (as it is thinking 3.5 SP1 is installed, so that KB963707 should be applied), that seem not to be working when you apply that reg key.
And again, I suppose you're referring to WU and not WUD (Windows Update Downloader) that is another piece of software not related with all this.
EDIT: While doing my tests I remembered I was playing time ago with this regkey when looking for the KB951847 fix and I finally discarded it but I've forgotten the reasons that led me to this. Now I realized the reason why I did it. Using the block regkey is not a perfect solution from the point of view of consistency.
While it is far simple to use that regkey than to simulate that absent frameworks (from the group of KB951847) + their regular hotfixes + their langpacks (matching OS language), are installed (method used by SNMsynth installers), it doesn't allow to happen things like this: Imagine you use SNMsynth installer to install .NET 2.0 SP2 + its regular hotfixes + its langpack (matching OS language), i.e. making KB951847 fix applies simulating 3.0 SP2 and 3.5 SP1 + their regular hotfixes + their langpacks (matching OS language) are installed, thus removing KB951847 prompting you to install this framework versions from win/ms update; then you remove 2.0 SP2 langpack, at this moment you should be prompted by win/ms update to install 2.0 SP2 langpack through an ad-hoc KB951847 update, but if you use that block regkey method, you won't be prompted to do that.
But SNMsynth's add-on you used (if made with latest version of the script) include a fix to avoid win/ms update to push KB951847, and this update is what it is going to install 3.0 SP2+3.5 SP1+regular hotfixes for both (and for 2.0 SP2 if you didn't apply them)+langpacks for both, in your case. This fix makes win/ms update think the previous set is installed.
If you apply that "BlockSP" reg key, you're applying 2 different fixes to avoid intalling 3.5 SP1 through KB951847 at the same time. And I suppose this should be the cause KB963707 is being pushed, because there's a fix included in that add-on too, for making win/ms update think KB963707 is installed (as it is thinking 3.5 SP1 is installed, so that KB963707 should be applied), that seem not to be working when you apply that reg key.
And again, I suppose you're referring to WU and not WUD (Windows Update Downloader) that is another piece of software not related with all this.
EDIT: While doing my tests I remembered I was playing time ago with this regkey when looking for the KB951847 fix and I finally discarded it but I've forgotten the reasons that led me to this. Now I realized the reason why I did it. Using the block regkey is not a perfect solution from the point of view of consistency.
While it is far simple to use that regkey than to simulate that absent frameworks (from the group of KB951847) + their regular hotfixes + their langpacks (matching OS language), are installed (method used by SNMsynth installers), it doesn't allow to happen things like this: Imagine you use SNMsynth installer to install .NET 2.0 SP2 + its regular hotfixes + its langpack (matching OS language), i.e. making KB951847 fix applies simulating 3.0 SP2 and 3.5 SP1 + their regular hotfixes + their langpacks (matching OS language) are installed, thus removing KB951847 prompting you to install this framework versions from win/ms update; then you remove 2.0 SP2 langpack, at this moment you should be prompted by win/ms update to install 2.0 SP2 langpack through an ad-hoc KB951847 update, but if you use that block regkey method, you won't be prompted to do that.
Updated.
Enjoy!
Enjoy!
Hi I see there is an update for this Silen .net maker but i cannot find the link, could you pleasew post it again or point me in the right direction?? Taa
Link is in the instructions section bellow in the guide, and is apparently working.
Thx for your interest.
Thx for your interest.
If you are interested in making the output smaller in size:
http://www.msfn.org/board/tutorial-modify-...ll-t137477.html
this method can be applied on language pack for .NET 3.5, also.
http://www.msfn.org/board/tutorial-modify-...ll-t137477.html
this method can be applied on language pack for .NET 3.5, also.
Thanks to strel and his regular updates on the first page, I've decided to make my own contribution here to make the life easier for those who find .NET integration (particularly the editing of _SNMsynth.ini file) difficult. Below is MY OWN understanding - explained in a layman terms - of how this file should be edited to get successful results for different scenarios, based on strel's instructions. His instructions is a must-read before posting here. Although the description inside .INI is self-explanatory, based on my own experience, I hoped this post will make the things easier for lazies like me. 
This info is for English version of XP only! Users of systems with different languages must download separate language packs. strel and other gurus, please correct me if I'm wrong. Again, this in NO WAY compares to strel's full explanation of the process and reflects my own understanding of the integration process only! So, here we go:
SCENARIO 1
Goals:
- to make a merged installer which contains .NET 1.1, 2.0 SP2, 3.0 SP2 and 3.5 SP1.
- to apply all regular hotfixes for the above.
- to avoid possible error messages in Event Viewer after Windows startup.
- optional: to avoid installation of Firefox ClickOnce addon
- number of "_SNMsynth.cmd" runs: 1
Solution:
1) Read "INSTRUCTIONS" section to know which files are required to start integration and download them as instructed.
2) Download the following files and put ALL of them together with files mentioned at point 1 inside a single folder:
.NET 1.1 Redistributable Package
NDP1.1sp1-KB867460-X86.exe
NDP1.1sp1-KB928366-X86.exe
.NET 3.5 SP1 Redistributable Package
NDP20SP2-KB958481-x86.exe
NDP30SP2-KB958483-x86.exe
NDP35SP1-KB958484-x86.exe
3) Edit "_SNMsynth.ini" as follows (without my comments inside the code):
4) Run "_SNMsynth.cmd" and wait until the merged .NET installer is ready.
NOTE: Make sure you use RunOnceEx method with this scenario to avoid resulting Event Viewer errors at the end of installation. To use partial (!) SVCPACK method or to slipstream driver packs which require installation of .NET-dependent applications like ATI Catalyst Control Panel into Windows installation disc (more info @ DriverPacks.NET), please use Scenario 2 below.
SCENARIO 2
Goals:
- to make separate installers for i) .NET 1.1 and 2.0 SP2; ii) 3.0 SP2 and 3.5 SP1.
- to apply all regular hotfixes for the above.
- to avoid possible error messages in Event Viewer after drivers' installation and at Windows startup.
- optional: to avoid installation of Firefox ClickOnce addon
- number of "_SNMsynth.cmd" runs: 2
Solution:
1) same as at point 1 of Scenario 1
2) same as at point 2 of Scenario 1
3) For the first run, i.e. to make a separate merged installer for .NET 1.1 and .NET 2.0 SP2, edit "_SNMsynth.ini" as follows:
Note: Optionally you can download NetFx20SP2_x86.exe to build a merged installer for .NET 1.1 + 2.0 SP2. This is advantageous for those with weak systems, if you don't want to wait long until the silent maker extracts the 2.0 SP2 portion out of 3.5 SP1, as shown above. In this case you need to replace "PROCESS_DNF35_DNF2=YES" with "PROCESS_DNF2=YES".
4) Run "_SNMsynth.cmd" and wait until the merged .NET installer is ready.
5) For the second run, i.e. to make a separate merged installer for .NET 3.0 SP2 and .NET 3.5 SP1, edit "_SNMsynth.ini" as follows:
6) Again, run "_SNMsynth.cmd" and wait until the merged .NET installer is ready.
NOTE: This scenario requires that you use SVCPACK method first to install the merged installer for .NET 1.1 + 2.0 SP2 at T-13/T-12, and only then apply RunOnceEx method to run the installer for .NET 3.0 SP2 + 3.5 SP1.
Applies to both scenarios:
1) If you want to add an uninstall button to .NET Framework Assistant 1.0 add-on for Firefox, download NDP35SP1-KB963707-x86.exe as well. Put "DNF_FF_ADDON=YES" if you want to install this optional fix for Firefox.
Caution: If you include Firefox ClickOnce addon ("DNF_FF_ADDON=YES"), before running the compiled .NET installer through either of SVCPACK or RunOnceEx methods, make sure that you edit respective .inf or .cmd files so that Firefox has priority in the list, i.e. is installed first! As recommended by strel, if you choose to install the Firefox addon, the script makes you apply KB963707 to build installers since the last version it's mandatory to use "DNF_FF_ADDON=YES" because KB963707 contains important fixes for the Firefox addon.
2) Since the LAST FOUR STRINGS are self-explanatory and do not have a direct impact on integration process, I just show my own edits here but you may change them to "NO" or "YES" as you like.
3) If you use OncePiece's post-SP3 update pack v2.7.0 for Windows XP, it already contains updated MSXML (KB954459 and KB960380-v2 which supersedes KB954459) and you install it before 3.0 during Windows setup, you don't need to include MSXML in 3.0 installer (PROCESS_DNF3_MSXML6=NO).
That's it for now! Don't know, may be other scenarios are also possible to derive out of strel's recommendations but I use the above two in particular with no side-effects yet. Feel free to comment on this post!
Hope this helps!
This info is for English version of XP only! Users of systems with different languages must download separate language packs. strel and other gurus, please correct me if I'm wrong. Again, this in NO WAY compares to strel's full explanation of the process and reflects my own understanding of the integration process only! So, here we go:SCENARIO 1
Goals:
- to make a merged installer which contains .NET 1.1, 2.0 SP2, 3.0 SP2 and 3.5 SP1.
- to apply all regular hotfixes for the above.
- to avoid possible error messages in Event Viewer after Windows startup.
- optional: to avoid installation of Firefox ClickOnce addon
- number of "_SNMsynth.cmd" runs: 1
Solution:
1) Read "INSTRUCTIONS" section to know which files are required to start integration and download them as instructed.
2) Download the following files and put ALL of them together with files mentioned at point 1 inside a single folder:
.NET 1.1 Redistributable Package
NDP1.1sp1-KB867460-X86.exe
NDP1.1sp1-KB928366-X86.exe
.NET 3.5 SP1 Redistributable Package
NDP20SP2-KB958481-x86.exe
NDP30SP2-KB958483-x86.exe
NDP35SP1-KB958484-x86.exe
3) Edit "_SNMsynth.ini" as follows (without my comments inside the code):
CODE
PROCESS_DNF1=YES ; builds installer with .NET 1.1
PROCESS_DNF2=
PROCESS_DNF35_DNF2=YES ; builds installer with .NET 2.0 SP2 portion of .NET 3.5 SP1 redistributable package
PROCESS_DNF35_DNF3=YES ; builds installer with .NET 3.0 SP2 portion of .NET 3.5 SP1 redistributable package
PROCESS_DNF35_DNF35=YES ; builds installer with .NET 3.5 SP1
PROCESS_DNF3_RGBRAST=YES
PROCESS_DNF3_WINIMAGING=YES
PROCESS_DNF3_MSXML6=YES
PROCESS_DNF3_XMLPSSC=YES
DNF_FF_ADDON=NO
PROCESS_LNG_DNF1=NO
PROCESS_LNG_DNF2=NO
PROCESS_LNG_DNF35_DNF2=NO
PROCESS_LNG_DNF35_DNF3=NO
PROCESS_LNG_DNF35_DNF35=NO
ADDON=YES
MERGE_FRAMEWORKS=YES
SILENT=YES
COMPRESSION_RATIO=HIGHER
PROCESS_DNF2=
PROCESS_DNF35_DNF2=YES ; builds installer with .NET 2.0 SP2 portion of .NET 3.5 SP1 redistributable package
PROCESS_DNF35_DNF3=YES ; builds installer with .NET 3.0 SP2 portion of .NET 3.5 SP1 redistributable package
PROCESS_DNF35_DNF35=YES ; builds installer with .NET 3.5 SP1
PROCESS_DNF3_RGBRAST=YES
PROCESS_DNF3_WINIMAGING=YES
PROCESS_DNF3_MSXML6=YES
PROCESS_DNF3_XMLPSSC=YES
DNF_FF_ADDON=NO
PROCESS_LNG_DNF1=NO
PROCESS_LNG_DNF2=NO
PROCESS_LNG_DNF35_DNF2=NO
PROCESS_LNG_DNF35_DNF3=NO
PROCESS_LNG_DNF35_DNF35=NO
ADDON=YES
MERGE_FRAMEWORKS=YES
SILENT=YES
COMPRESSION_RATIO=HIGHER
4) Run "_SNMsynth.cmd" and wait until the merged .NET installer is ready.
NOTE: Make sure you use RunOnceEx method with this scenario to avoid resulting Event Viewer errors at the end of installation. To use partial (!) SVCPACK method or to slipstream driver packs which require installation of .NET-dependent applications like ATI Catalyst Control Panel into Windows installation disc (more info @ DriverPacks.NET), please use Scenario 2 below.
SCENARIO 2
Goals:
- to make separate installers for i) .NET 1.1 and 2.0 SP2; ii) 3.0 SP2 and 3.5 SP1.
- to apply all regular hotfixes for the above.
- to avoid possible error messages in Event Viewer after drivers' installation and at Windows startup.
- optional: to avoid installation of Firefox ClickOnce addon
- number of "_SNMsynth.cmd" runs: 2
Solution:
1) same as at point 1 of Scenario 1
2) same as at point 2 of Scenario 1
3) For the first run, i.e. to make a separate merged installer for .NET 1.1 and .NET 2.0 SP2, edit "_SNMsynth.ini" as follows:
CODE
PROCESS_DNF1=YES ; builds installer with .NET 1.1
PROCESS_DNF2=
PROCESS_DNF35_DNF2=YES ; builds installer with .NET 2.0 SP2 portion of .NET 3.0 SP2.
PROCESS_DNF35_DNF3=
PROCESS_DNF35_DNF35=
PROCESS_DNF3_RGBRAST=YES
PROCESS_DNF3_WINIMAGING=YES
PROCESS_DNF3_MSXML6=YES
PROCESS_DNF3_XMLPSSC=YES
DNF_FF_ADDON=NO
PROCESS_LNG_DNF1=NO
PROCESS_LNG_DNF2=NO
PROCESS_LNG_DNF35_DNF2=NO
PROCESS_LNG_DNF35_DNF3=NO
PROCESS_LNG_DNF35_DNF35=NO
ADDON=YES
MERGE_FRAMEWORKS=YES
SILENT=YES
COMPRESSION_RATIO=HIGHER
PROCESS_DNF2=
PROCESS_DNF35_DNF2=YES ; builds installer with .NET 2.0 SP2 portion of .NET 3.0 SP2.
PROCESS_DNF35_DNF3=
PROCESS_DNF35_DNF35=
PROCESS_DNF3_RGBRAST=YES
PROCESS_DNF3_WINIMAGING=YES
PROCESS_DNF3_MSXML6=YES
PROCESS_DNF3_XMLPSSC=YES
DNF_FF_ADDON=NO
PROCESS_LNG_DNF1=NO
PROCESS_LNG_DNF2=NO
PROCESS_LNG_DNF35_DNF2=NO
PROCESS_LNG_DNF35_DNF3=NO
PROCESS_LNG_DNF35_DNF35=NO
ADDON=YES
MERGE_FRAMEWORKS=YES
SILENT=YES
COMPRESSION_RATIO=HIGHER
Note: Optionally you can download NetFx20SP2_x86.exe to build a merged installer for .NET 1.1 + 2.0 SP2. This is advantageous for those with weak systems, if you don't want to wait long until the silent maker extracts the 2.0 SP2 portion out of 3.5 SP1, as shown above. In this case you need to replace "PROCESS_DNF35_DNF2=YES" with "PROCESS_DNF2=YES".
4) Run "_SNMsynth.cmd" and wait until the merged .NET installer is ready.
5) For the second run, i.e. to make a separate merged installer for .NET 3.0 SP2 and .NET 3.5 SP1, edit "_SNMsynth.ini" as follows:
CODE
PROCESS_DNF1=
PROCESS_DNF2=
PROCESS_DNF35_DNF2=
PROCESS_DNF35_DNF3=YES ; builds installer with .NET 3.0 SP2
PROCESS_DNF35_DNF35=YES ; builds installer with .NET 3.5 SP1
PROCESS_DNF3_RGBRAST=YES
PROCESS_DNF3_WINIMAGING=YES
PROCESS_DNF3_MSXML6=YES
PROCESS_DNF3_XMLPSSC=YES
DNF_FF_ADDON=NO
PROCESS_LNG_DNF1=NO
PROCESS_LNG_DNF2=NO
PROCESS_LNG_DNF35_DNF2=NO
PROCESS_LNG_DNF35_DNF3=NO
PROCESS_LNG_DNF35_DNF35=NO
ADDON=YES
MERGE_FRAMEWORKS=YES
SILENT=YES
COMPRESSION_RATIO=HIGHER
PROCESS_DNF2=
PROCESS_DNF35_DNF2=
PROCESS_DNF35_DNF3=YES ; builds installer with .NET 3.0 SP2
PROCESS_DNF35_DNF35=YES ; builds installer with .NET 3.5 SP1
PROCESS_DNF3_RGBRAST=YES
PROCESS_DNF3_WINIMAGING=YES
PROCESS_DNF3_MSXML6=YES
PROCESS_DNF3_XMLPSSC=YES
DNF_FF_ADDON=NO
PROCESS_LNG_DNF1=NO
PROCESS_LNG_DNF2=NO
PROCESS_LNG_DNF35_DNF2=NO
PROCESS_LNG_DNF35_DNF3=NO
PROCESS_LNG_DNF35_DNF35=NO
ADDON=YES
MERGE_FRAMEWORKS=YES
SILENT=YES
COMPRESSION_RATIO=HIGHER
6) Again, run "_SNMsynth.cmd" and wait until the merged .NET installer is ready.
NOTE: This scenario requires that you use SVCPACK method first to install the merged installer for .NET 1.1 + 2.0 SP2 at T-13/T-12, and only then apply RunOnceEx method to run the installer for .NET 3.0 SP2 + 3.5 SP1.
Applies to both scenarios:
1) If you want to add an uninstall button to .NET Framework Assistant 1.0 add-on for Firefox, download NDP35SP1-KB963707-x86.exe as well. Put "DNF_FF_ADDON=YES" if you want to install this optional fix for Firefox.
Caution: If you include Firefox ClickOnce addon ("DNF_FF_ADDON=YES"), before running the compiled .NET installer through either of SVCPACK or RunOnceEx methods, make sure that you edit respective .inf or .cmd files so that Firefox has priority in the list, i.e. is installed first! As recommended by strel, if you choose to install the Firefox addon, the script makes you apply KB963707 to build installers since the last version it's mandatory to use "DNF_FF_ADDON=YES" because KB963707 contains important fixes for the Firefox addon.
2) Since the LAST FOUR STRINGS are self-explanatory and do not have a direct impact on integration process, I just show my own edits here but you may change them to "NO" or "YES" as you like.
3) If you use OncePiece's post-SP3 update pack v2.7.0 for Windows XP, it already contains updated MSXML (KB954459 and KB960380-v2 which supersedes KB954459) and you install it before 3.0 during Windows setup, you don't need to include MSXML in 3.0 installer (PROCESS_DNF3_MSXML6=NO).
That's it for now! Don't know, may be other scenarios are also possible to derive out of strel's recommendations but I use the above two in particular with no side-effects yet.
Feel free to comment on this post!Hope this helps!
Strel, if i want to install the update from .net framework asssitant in firefox (KB963707) wich option should i use in _snmsynth.ini ?
I don't understand what the default option do, avoids the update showing in MU by adding some keys, or integrate KB963707 into snmsynth installation ?
QUOTE
; ------- PROCESS SUBCOMPONENTS OF DNF 3.5 SP1
; The following setting allows you to avoid installing .NET Assistant Firefox add-on implementing clickonce, .NET's software
; downloading/updating technollogy, into FF (in addition to IE). Some people dislikes this in FF for various reasons, see guide.
DNF_FF_ADDON=YES
; The following setting allows you to avoid installing .NET Assistant Firefox add-on implementing clickonce, .NET's software
; downloading/updating technollogy, into FF (in addition to IE). Some people dislikes this in FF for various reasons, see guide.
DNF_FF_ADDON=YES
I don't understand what the default option do, avoids the update showing in MU by adding some keys, or integrate KB963707 into snmsynth installation ?
The default option installs the firefox add-on as the original installer do, moreover, for this default option the script makes you apply mandatory KB963707 hotfix, as it contains important fixes for FF add-on like being able to install on firefox > 3.0.*, giving the uninstall button, but more important, removing the .NET user agent that were reporting every webserver about the .NET update condition of your machine.
This setting is useful in case you just don't want to install the firefox add-on.
2 simurqq (see above) and everybody
In point 1 of your "applies to both scenarios" section there's something incorrect. It's not mandatory to set "DNF_FF_ADDON=YES" it's a choice. As explained in my previous lines.
This setting is useful in case you just don't want to install the firefox add-on.
2 simurqq (see above) and everybody
In point 1 of your "applies to both scenarios" section there's something incorrect. It's not mandatory to set "DNF_FF_ADDON=YES" it's a choice. As explained in my previous lines.
thank you strel
Hello there,
I created a .NET package for W2K3 with this _SNMsynth.ini:
I had these hotfixes in the work folder:
NDP20SP2-KB958481-x86.exe
NDP30SP2-KB958483-x86.exe
NDP35SP1-KB958484-x86.exe
NDP35SP1-KB963707-x86.exe
It created a 45 MB installer. However, when I try to run it on a freshly installed W2k3 box, after I logged in, it fails almost immediately. This is the content of the NETFX20.log:
Do you guys have any idea why it failed?
Thanks
I created a .NET package for W2K3 with this _SNMsynth.ini:
CODE
; SNMsynth.CMD PROCESS SETTINGS.
PROCESS_DNF1=
PROCESS_DNF2=
PROCESS_DNF35_DNF2=YES
PROCESS_DNF35_DNF3=YES
PROCESS_DNF35_DNF35=YES
PROCESS_DNF3_RGBRAST=YES
PROCESS_DNF3_WINIMAGING=YES
PROCESS_DNF3_MSXML6=YES
PROCESS_DNF3_XMLPSSC=YES
DNF_FF_ADDON=NO
PROCESS_LNG_DNF1=NO
PROCESS_LNG_DNF2=NO
PROCESS_LNG_DNF35_DNF2=NO
PROCESS_LNG_DNF35_DNF3=NO
PROCESS_LNG_DNF35_DNF35=NO
WIN2K3=YES
ADDON=NO
MERGE_FRAMEWORKS=YES
SILENT=
COMPRESSION_RATIO=HIGH
PROCESS_DNF1=
PROCESS_DNF2=
PROCESS_DNF35_DNF2=YES
PROCESS_DNF35_DNF3=YES
PROCESS_DNF35_DNF35=YES
PROCESS_DNF3_RGBRAST=YES
PROCESS_DNF3_WINIMAGING=YES
PROCESS_DNF3_MSXML6=YES
PROCESS_DNF3_XMLPSSC=YES
DNF_FF_ADDON=NO
PROCESS_LNG_DNF1=NO
PROCESS_LNG_DNF2=NO
PROCESS_LNG_DNF35_DNF2=NO
PROCESS_LNG_DNF35_DNF3=NO
PROCESS_LNG_DNF35_DNF35=NO
WIN2K3=YES
ADDON=NO
MERGE_FRAMEWORKS=YES
SILENT=
COMPRESSION_RATIO=HIGH
I had these hotfixes in the work folder:
NDP20SP2-KB958481-x86.exe
NDP30SP2-KB958483-x86.exe
NDP35SP1-KB958484-x86.exe
NDP35SP1-KB963707-x86.exe
It created a 45 MB installer. However, when I try to run it on a freshly installed W2k3 box, after I logged in, it fails almost immediately. This is the content of the NETFX20.log:
CODE
=== Verbose logging started: 9/3/2009 13:22:15 Build type: SHIP UNICODE 4.05.6001.00 Calling process: C:\WINDOWS\System32\msiexec.exe ===
MSI © (C8:D4) [13:22:15:619]: Resetting cached policy values
MSI © (C8:D4) [13:22:15:619]: Machine policy value 'Debug' is 0
MSI © (C8:D4) [13:22:15:619]: ******* RunEngine:
******* Product: C:\Temp\7ZipSfx.000\DNF20\Netfx20a_x86.msi
******* Action:
******* CommandLine: **********
MSI © (C8:D4) [13:22:15:619]: Client-side and UI is none or basic: Running entire install on the server.
MSI © (C8:D4) [13:22:15:619]: Grabbed execution mutex.
MSI © (C8:D4) [13:22:15:681]: Cloaking enabled.
MSI © (C8:D4) [13:22:15:681]: Attempting to enable all disabled privileges before calling Install on Server
MSI © (C8:D4) [13:22:15:697]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (E4:00) [13:22:15:744]: Running installation inside multi-package transaction C:\Temp\7ZipSfx.000\DNF20\Netfx20a_x86.msi
MSI (s) (E4:00) [13:22:15:744]: Grabbed execution mutex.
MSI (s) (E4:1C) [13:22:15:775]: Resetting cached policy values
MSI (s) (E4:1C) [13:22:15:775]: Machine policy value 'Debug' is 0
MSI (s) (E4:1C) [13:22:15:775]: ******* RunEngine:
******* Product: C:\Temp\7ZipSfx.000\DNF20\Netfx20a_x86.msi
******* Action:
******* CommandLine: **********
MSI (s) (E4:1C) [13:22:15:775]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (E4:1C) [13:22:16:291]: File will have security applied from OpCode.
MSI (s) (E4:1C) [13:22:16:291]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Temp\7ZipSfx.000\DNF20\Netfx20a_x86.msi' against software restriction policy
MSI (s) (E4:1C) [13:22:16:291]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (s) (E4:1C) [13:22:16:291]: SOFTWARE RESTRICTION POLICY: C:\Temp\7ZipSfx.000\DNF20\Netfx20a_x86.msi is not digitally signed
MSI (s) (E4:1C) [13:22:16:322]: SOFTWARE RESTRICTION POLICY: C:\Temp\7ZipSfx.000\DNF20\Netfx20a_x86.msi is permitted to run at the 'unrestricted' authorization level.
MSI (s) (E4:1C) [13:22:16:338]: End dialog not enabled
MSI (s) (E4:1C) [13:22:16:338]: Original package ==> C:\Temp\7ZipSfx.000\DNF20\Netfx20a_x86.msi
MSI (s) (E4:1C) [13:22:16:338]: Package we're running from ==> C:\WINDOWS\Installer\1d0c47.msi
MSI (s) (E4:1C) [13:22:16:385]: APPCOMPAT: looking for appcompat database entry with ProductCode '{C09FB3CD-3D0C-3F2D-899A-6A1D67F2073F}'.
MSI (s) (E4:1C) [13:22:16:385]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (E4:1C) [13:22:16:400]: MSCOREE not loaded loading copy from system32
MSI (s) (E4:1C) [13:22:16:478]: Machine policy value 'TransformsSecure' is 1
MSI (s) (E4:1C) [13:22:16:510]: Machine policy value 'DisablePatch' is 0
MSI (s) (E4:1C) [13:22:16:510]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (E4:1C) [13:22:16:510]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (E4:1C) [13:22:16:510]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (E4:1C) [13:22:16:510]: Looking for secure file transform:
MSI (s) (E4:1C) [13:22:16:510]: Note: 1: 2343
MSI (s) (E4:1C) [13:22:16:510]: Unable to create a temp copy of transform ''.
MSI (s) (E4:1C) [13:22:16:510]: Note: 1: 2203 2: 3: -2147287037
MSI (s) (E4:1C) [13:22:16:510]: Couldn't find cached transform . Looking for it at the source.
MSI (s) (E4:1C) [13:22:16:510]: Resolving source.
MSI (s) (E4:1C) [13:22:16:510]: Resolving source to launched-from source.
MSI (s) (E4:1C) [13:22:16:510]: Setting launched-from source as last-used.
MSI (s) (E4:1C) [13:22:16:510]: SOURCEDIR ==> C:\Temp\7ZipSfx.000\DNF20\
MSI (s) (E4:1C) [13:22:16:510]: SOURCEDIR product ==> {C09FB3CD-3D0C-3F2D-899A-6A1D67F2073F}
MSI (s) (E4:1C) [13:22:16:510]: Looking for secure file transform:
MSI (s) (E4:1C) [13:22:16:510]: Note: 1: 2343
MSI (s) (E4:1C) [13:22:16:510]: Unable to create a temp copy of transform ''.
MSI (s) (E4:1C) [13:22:16:510]: Note: 1: 2203 2: 3: -2147287037
MSI (s) (E4:1C) [13:22:16:510]: Couldn't find cached transform . Looking for it at the source.
MSI (s) (E4:1C) [13:22:16:510]: Looking for secure file transform: C:\Temp\7ZipSfx.000\DNF20\NETWUFIXES.mst
MSI (s) (E4:1C) [13:22:16:510]: Unable to create a temp copy of transform 'C:\Temp\7ZipSfx.000\DNF20\NETWUFIXES.mst'.
MSI (s) (E4:1C) [13:22:16:510]: Note: 1: 2203 2: C:\Temp\7ZipSfx.000\DNF20\NETWUFIXES.mst 3: -2147287038
DEBUG: Error 2203: Database: C:\Temp\7ZipSfx.000\DNF20\NETWUFIXES.mst. Cannot open database file. System error -2147287038
1: 2203 2: C:\Temp\7ZipSfx.000\DNF20\NETWUFIXES.mst 3: -2147287038
MSI (s) (E4:1C) [13:22:16:541]: Note: 1: 1708
MSI (s) (E4:1C) [13:22:16:556]: Product: Microsoft .NET Framework 2.0 Service Pack 2 -- Installation failed.
MSI (s) (E4:1C) [13:22:16:556]: Windows Installer installed the product. Product Name: Microsoft .NET Framework 2.0 Service Pack 2. Product Version: 2.2.30729. Product Language: 0. Installation success or error status: 1624.
MSI (s) (E4:1C) [13:22:16:556]: MainEngineThread is returning 1624
MSI (s) (E4:00) [13:22:16:556]: No System Restore sequence number for this installation.
Error applying transforms. Verify that the specified transform paths are valid.
C:\Temp\7ZipSfx.000\DNF20\NETWUFIXES.mst
MSI (s) (E4:00) [13:22:16:556]: User policy value 'DisableRollback' is 0
MSI (s) (E4:00) [13:22:16:556]: Machine policy value 'DisableRollback' is 0
MSI (s) (E4:00) [13:22:16:556]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (E4:00) [13:22:16:588]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (E4:00) [13:22:16:603]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (E4:00) [13:22:16:603]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (E4:00) [13:22:16:603]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (E4:00) [13:22:16:603]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (E4:00) [13:22:16:603]: Restoring environment variables
MSI © (C8:D4) [13:22:16:603]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI © (C8:D4) [13:22:16:603]: MainEngineThread is returning 1624
=== Verbose logging stopped: 9/3/2009 13:22:16 ===
MSI © (C8:D4) [13:22:15:619]: Resetting cached policy values
MSI © (C8:D4) [13:22:15:619]: Machine policy value 'Debug' is 0
MSI © (C8:D4) [13:22:15:619]: ******* RunEngine:
******* Product: C:\Temp\7ZipSfx.000\DNF20\Netfx20a_x86.msi
******* Action:
******* CommandLine: **********
MSI © (C8:D4) [13:22:15:619]: Client-side and UI is none or basic: Running entire install on the server.
MSI © (C8:D4) [13:22:15:619]: Grabbed execution mutex.
MSI © (C8:D4) [13:22:15:681]: Cloaking enabled.
MSI © (C8:D4) [13:22:15:681]: Attempting to enable all disabled privileges before calling Install on Server
MSI © (C8:D4) [13:22:15:697]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (E4:00) [13:22:15:744]: Running installation inside multi-package transaction C:\Temp\7ZipSfx.000\DNF20\Netfx20a_x86.msi
MSI (s) (E4:00) [13:22:15:744]: Grabbed execution mutex.
MSI (s) (E4:1C) [13:22:15:775]: Resetting cached policy values
MSI (s) (E4:1C) [13:22:15:775]: Machine policy value 'Debug' is 0
MSI (s) (E4:1C) [13:22:15:775]: ******* RunEngine:
******* Product: C:\Temp\7ZipSfx.000\DNF20\Netfx20a_x86.msi
******* Action:
******* CommandLine: **********
MSI (s) (E4:1C) [13:22:15:775]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (E4:1C) [13:22:16:291]: File will have security applied from OpCode.
MSI (s) (E4:1C) [13:22:16:291]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Temp\7ZipSfx.000\DNF20\Netfx20a_x86.msi' against software restriction policy
MSI (s) (E4:1C) [13:22:16:291]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (s) (E4:1C) [13:22:16:291]: SOFTWARE RESTRICTION POLICY: C:\Temp\7ZipSfx.000\DNF20\Netfx20a_x86.msi is not digitally signed
MSI (s) (E4:1C) [13:22:16:322]: SOFTWARE RESTRICTION POLICY: C:\Temp\7ZipSfx.000\DNF20\Netfx20a_x86.msi is permitted to run at the 'unrestricted' authorization level.
MSI (s) (E4:1C) [13:22:16:338]: End dialog not enabled
MSI (s) (E4:1C) [13:22:16:338]: Original package ==> C:\Temp\7ZipSfx.000\DNF20\Netfx20a_x86.msi
MSI (s) (E4:1C) [13:22:16:338]: Package we're running from ==> C:\WINDOWS\Installer\1d0c47.msi
MSI (s) (E4:1C) [13:22:16:385]: APPCOMPAT: looking for appcompat database entry with ProductCode '{C09FB3CD-3D0C-3F2D-899A-6A1D67F2073F}'.
MSI (s) (E4:1C) [13:22:16:385]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (E4:1C) [13:22:16:400]: MSCOREE not loaded loading copy from system32
MSI (s) (E4:1C) [13:22:16:478]: Machine policy value 'TransformsSecure' is 1
MSI (s) (E4:1C) [13:22:16:510]: Machine policy value 'DisablePatch' is 0
MSI (s) (E4:1C) [13:22:16:510]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (E4:1C) [13:22:16:510]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (E4:1C) [13:22:16:510]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (E4:1C) [13:22:16:510]: Looking for secure file transform:
MSI (s) (E4:1C) [13:22:16:510]: Note: 1: 2343
MSI (s) (E4:1C) [13:22:16:510]: Unable to create a temp copy of transform ''.
MSI (s) (E4:1C) [13:22:16:510]: Note: 1: 2203 2: 3: -2147287037
MSI (s) (E4:1C) [13:22:16:510]: Couldn't find cached transform . Looking for it at the source.
MSI (s) (E4:1C) [13:22:16:510]: Resolving source.
MSI (s) (E4:1C) [13:22:16:510]: Resolving source to launched-from source.
MSI (s) (E4:1C) [13:22:16:510]: Setting launched-from source as last-used.
MSI (s) (E4:1C) [13:22:16:510]: SOURCEDIR ==> C:\Temp\7ZipSfx.000\DNF20\
MSI (s) (E4:1C) [13:22:16:510]: SOURCEDIR product ==> {C09FB3CD-3D0C-3F2D-899A-6A1D67F2073F}
MSI (s) (E4:1C) [13:22:16:510]: Looking for secure file transform:
MSI (s) (E4:1C) [13:22:16:510]: Note: 1: 2343
MSI (s) (E4:1C) [13:22:16:510]: Unable to create a temp copy of transform ''.
MSI (s) (E4:1C) [13:22:16:510]: Note: 1: 2203 2: 3: -2147287037
MSI (s) (E4:1C) [13:22:16:510]: Couldn't find cached transform . Looking for it at the source.
MSI (s) (E4:1C) [13:22:16:510]: Looking for secure file transform: C:\Temp\7ZipSfx.000\DNF20\NETWUFIXES.mst
MSI (s) (E4:1C) [13:22:16:510]: Unable to create a temp copy of transform 'C:\Temp\7ZipSfx.000\DNF20\NETWUFIXES.mst'.
MSI (s) (E4:1C) [13:22:16:510]: Note: 1: 2203 2: C:\Temp\7ZipSfx.000\DNF20\NETWUFIXES.mst 3: -2147287038
DEBUG: Error 2203: Database: C:\Temp\7ZipSfx.000\DNF20\NETWUFIXES.mst. Cannot open database file. System error -2147287038
1: 2203 2: C:\Temp\7ZipSfx.000\DNF20\NETWUFIXES.mst 3: -2147287038
MSI (s) (E4:1C) [13:22:16:541]: Note: 1: 1708
MSI (s) (E4:1C) [13:22:16:556]: Product: Microsoft .NET Framework 2.0 Service Pack 2 -- Installation failed.
MSI (s) (E4:1C) [13:22:16:556]: Windows Installer installed the product. Product Name: Microsoft .NET Framework 2.0 Service Pack 2. Product Version: 2.2.30729. Product Language: 0. Installation success or error status: 1624.
MSI (s) (E4:1C) [13:22:16:556]: MainEngineThread is returning 1624
MSI (s) (E4:00) [13:22:16:556]: No System Restore sequence number for this installation.
Error applying transforms. Verify that the specified transform paths are valid.
C:\Temp\7ZipSfx.000\DNF20\NETWUFIXES.mst
MSI (s) (E4:00) [13:22:16:556]: User policy value 'DisableRollback' is 0
MSI (s) (E4:00) [13:22:16:556]: Machine policy value 'DisableRollback' is 0
MSI (s) (E4:00) [13:22:16:556]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (E4:00) [13:22:16:588]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (E4:00) [13:22:16:603]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (E4:00) [13:22:16:603]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (E4:00) [13:22:16:603]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (E4:00) [13:22:16:603]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (E4:00) [13:22:16:603]: Restoring environment variables
MSI © (C8:D4) [13:22:16:603]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI © (C8:D4) [13:22:16:603]: MainEngineThread is returning 1624
=== Verbose logging stopped: 9/3/2009 13:22:16 ===
Do you guys have any idea why it failed?
Thanks
Great you include the log file!
After searching around, error code 2203 seems to suggest a problem with permissions that seems to be obstructing .mst to get copied to the installer cache folder, typically %SYSTEMROOT%\Installer and/or to be uncompressed to the %TEMP% folder. To overcome this error try giving full permissions to SYSTEM account on these folders, begin with %TEMP%. You may need to give full permissions on that folders too to current user account.
Please tell us about your progress.
Is it happening that to any of you using win 2K3?
After searching around, error code 2203 seems to suggest a problem with permissions that seems to be obstructing .mst to get copied to the installer cache folder, typically %SYSTEMROOT%\Installer and/or to be uncompressed to the %TEMP% folder. To overcome this error try giving full permissions to SYSTEM account on these folders, begin with %TEMP%. You may need to give full permissions on that folders too to current user account.
Please tell us about your progress.
Is it happening that to any of you using win 2K3?
Thanks for your quick reply!
I don't think it is a permission issue, because both the System and user accounts have full permission on the temp folder. Also, I generated a .NET package with an early version of your script (from June 2008) and I was able to install it without any problem. Unfortunately, that early version doesn't integrate the new hotfixes...
I don't think it is a permission issue, because both the System and user accounts have full permission on the temp folder. Also, I generated a .NET package with an early version of your script (from June 2008) and I was able to install it without any problem. Unfortunately, that early version doesn't integrate the new hotfixes...
Well, I still think something is obstructing .mst files to get copied over the installer cache folder. If we read the log file, install process first try to look for the .mst files in the installer cache folder, when it don't find them, then it searches them in the installer source folder, but .mst files are not in the installer source folder, they are in the install script folder, I may have to change this for the next version.
I think if you give permissions to the installer cache folder or if you manage to put a copy of the .mst files in the DNF20 DNF30 DNF35 folders when the installer uncompress (or if you uncompress the installer and then put a copy of .mst files in folders DNF20 DNF30 and DNF35 manually and then run INSTALL.cmd), you'd solve the problem.
About permissions I think this is self explicative.
Again tell us about your progress please.
I think if you give permissions to the installer cache folder or if you manage to put a copy of the .mst files in the DNF20 DNF30 DNF35 folders when the installer uncompress (or if you uncompress the installer and then put a copy of .mst files in folders DNF20 DNF30 and DNF35 manually and then run INSTALL.cmd), you'd solve the problem.
About permissions I think this is self explicative.
Again tell us about your progress please.
You were right! It was a permission issue after all. I did what you recommended: extracted the files, copied the .mst files into the DNF20, DNF30 and DNF35 folders and ran the install.cmd. This way I was able to install it without any error.
Thanks for your help!
Thanks for your help!
But this is only a workaround for installing, if you don't get .mst files are effectively copied over a subfolder of the installers cache folder (%SYSTEMROOT%\Installer\{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}), and you remove the folder from wich you are installing .NET, the uninstall process will have access to .mst files, and will not be able to remove the tweaks made by SNMsynth installers so you may have incorrect win/ms update messages. You need to get .mst files copied over that folder, this way all fixes applied will get properly removed on uninstall.
I'd try changing the permissions of %SYSTEMROOT%\Installer folder as explained before, to get .mst files copied during install. Or try making it manually, to get the folder name you need the GUID of the installer, you can get it from registry in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, there you'll see varios GUID named keys, browse through them looking for .NET in DisplayName values, and you'll have folder name. Copy .mst files used by the installer for that framerwork version (in the TRASFORMS= property of the install command of each framework version, inside the install script of SNMsynth installer) to the installer cache subfolder.
As you see it's far more easy to fix intaller cache folder permissions.
I'd try changing the permissions of %SYSTEMROOT%\Installer folder as explained before, to get .mst files copied during install. Or try making it manually, to get the folder name you need the GUID of the installer, you can get it from registry in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, there you'll see varios GUID named keys, browse through them looking for .NET in DisplayName values, and you'll have folder name. Copy .mst files used by the installer for that framerwork version (in the TRASFORMS= property of the install command of each framework version, inside the install script of SNMsynth installer) to the installer cache subfolder.
As you see it's far more easy to fix intaller cache folder permissions.
Hey strel..
I've been using your method for quite a while now and it always works like a charm! Thanks alot!
I just have a question.. Is it possible to implement a method in the script so it supports x64 .Net Framework as well..
I mean.. The method would be more or less the same wouldn't it?
I stumbled upon this site where someone has managed to create such an addon
http://forum.ragezone.com/f528/microsoft-n...lls-aio-522307/
The only "problem" with this pack is that the hotfixes is not included...
Cheers
I've been using your method for quite a while now and it always works like a charm! Thanks alot!
I just have a question.. Is it possible to implement a method in the script so it supports x64 .Net Framework as well..
I mean.. The method would be more or less the same wouldn't it?
I stumbled upon this site where someone has managed to create such an addon
http://forum.ragezone.com/f528/microsoft-n...lls-aio-522307/
The only "problem" with this pack is that the hotfixes is not included...
Cheers
Hi djanz.
Suppose it would be similar but I'm sure there would be things to adapt and test. Someone asked me about this time ago, at that time I was thinking in making a 64-bit version of the script, the problem is that I'm not having access to a 64-bit machine, so I'm not doing it. What I can offer is my help to anyone who want to do it.
At the moment you have a better option with HJW's .NET x64 installer that includes regular hotfixes, thx to RickSteele for the link.
Cheers.
Suppose it would be similar but I'm sure there would be things to adapt and test. Someone asked me about this time ago, at that time I was thinking in making a 64-bit version of the script, the problem is that I'm not having access to a 64-bit machine, so I'm not doing it. What I can offer is my help to anyone who want to do it.
At the moment you have a better option with HJW's .NET x64 installer that includes regular hotfixes, thx to RickSteele for the link.
Cheers.
Im currently trying to add some extra registry entries.
To do this I do the following.
Extract config.txt and the original archive with 7zsplit.
Extract the original archive to a folder.
Add my UPDATE.REG (to disable WebClient service and edit some titles in add/remove).
Edit INSTALL.CMD
As you can see I put it afterwards your DNF11.REG
Then I make an archive.
Compile an exe with the silentswitchmaker, using the same config.txt as you did.
When I start it, it immidiatly crashess.
Could you tell me how I should do it, since I have tried it in several ways, and it doesnt work, always crashes.
edit:
Hmm I am thinking about something else.
I edit your generated config.txt to this:
And then just make a new installer. (so i dont have to remake it, just your way with editted config.txt).
Only im not sure if the 2nd runprogram will work?
Oh i forgot, then i have to edit the "_SNMsynth.cmd" also, otherwise it wont grab my UPDATE.REG file (and include it in the archive..)..
hm hm
im stuck. Help 
edit:
Hmm I tried making the installer in this way:
http://www.wincert.net/forum/index.php?/to...less-installer/
And it didnt crash, i used the config.txt I placed earlier this post.
To do this I do the following.
Extract config.txt and the original archive with 7zsplit.
Extract the original archive to a folder.
Add my UPDATE.REG (to disable WebClient service and edit some titles in add/remove).
Edit INSTALL.CMD
CODE
%SYSTEMROOT%\REGEDIT /S DNF11.REG
REGEDIT /S UPDATE.REG
REGEDIT /S UPDATE.REG
As you can see I put it afterwards your DNF11.REG
Then I make an archive.
Compile an exe with the silentswitchmaker, using the same config.txt as you did.
When I start it, it immidiatly crashess.
Could you tell me how I should do it, since I have tried it in several ways, and it doesnt work, always crashes.
edit:
Hmm I am thinking about something else.
I edit your generated config.txt to this:
CODE
;!@Install@!UTF-8!
RunProgram="hidcon:INSTALL.CMD"
RunProgram="REGEDIT /S UPDATE.REG"
GUIMode="2"
;!@InstallEnd@!
RunProgram="hidcon:INSTALL.CMD"
RunProgram="REGEDIT /S UPDATE.REG"
GUIMode="2"
;!@InstallEnd@!
And then just make a new installer. (so i dont have to remake it, just your way with editted config.txt).
Only im not sure if the 2nd runprogram will work?
Oh i forgot, then i have to edit the "_SNMsynth.cmd" also, otherwise it wont grab my UPDATE.REG file (and include it in the archive..)..
hm hm
im stuck.
Help edit:
Hmm I tried making the installer in this way:
http://www.wincert.net/forum/index.php?/to...less-installer/
And it didnt crash, i used the config.txt I placed earlier this post.
Not sure why it fails in your first trial. For your second trial, the sfx accept multiple RunPogram entries, try RunProgram="hidcon:%SYSTEMROOT%\REGEDIT /S UPDATE.REG" if you want to hide the console, and don't forget to save the config.txt in UTF-8 mode, otherwise it won't work. Remember that 7zsd.sfx included in the SNMsynth packet is yet compressed with UPX.
And finally you got it, nice idea to make an ad-hoc _SNMsynth.cmd, are you having questions about how to do it?
And finally you got it, nice idea to make an ad-hoc _SNMsynth.cmd, are you having questions about how to do it?
Strel: Do i need to add KB963707 in the folder of SNMSynth or the fix is included in KB963707FIX.mst ?
The script will ask you for it if needed.
You'll need NDP35SP1-KB963707-x86.exe in the work folder in case you are building an installer/nLite add-on containing .NET 3.5 SP1 framework, if you allowed it to install .NET Assistant add-on for Firefox therein, through the related setting in the .ini file. KB963707FIX.mst is precisely a fix to get that hotfix correctly applied to the installer, otherwise it generates errors on install (if I recall it correctly).
You'll need NDP35SP1-KB963707-x86.exe in the work folder in case you are building an installer/nLite add-on containing .NET 3.5 SP1 framework, if you allowed it to install .NET Assistant add-on for Firefox therein, through the related setting in the .ini file. KB963707FIX.mst is precisely a fix to get that hotfix correctly applied to the installer, otherwise it generates errors on install (if I recall it correctly).
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.