I've tested the last release and ALL (software, update and reboot) work!
Thanks a lot!
PS Windows Installer on my system worked correctly, but the service was not started...
thanks also for this 
Full Version: Silent .NET Maker synthesized 20091105 - W2K/XP/2K3 x86
@strel
I've tested the last release and ALL (software, update and reboot) work!
Thanks a lot!
PS Windows Installer on my system worked correctly, but the service was not started... thanks also for this
I've tested the last release and ALL (software, update and reboot) work!
Thanks a lot!
PS Windows Installer on my system worked correctly, but the service was not started...
thanks also for this QUOTE (strel @ Nov 5 2009, 11:34 AM) 
New version released!!
2 minor bugs removed.
mooms
Thx a lot!!!
You helped me a lot finding one of the most slippery bugs I have had with this method. I dropped a wrong single digit in 30SP2LNG_KB951847FIX.mst causing your (and everybody's using 3.0 SP2 langpacks) problem.
What's happening is that it was failing to remove 1 regvalue used as KB951847 fix for 3.5 SP1 family langpacks, only in the case 3.0 SP2 langpack was the last langpack from this family to be uninstalled (tricky). But the error appears not only in that circumstance, because it is triggered when the script to execute is not found, whether it has to be executed or not.
What's curious is that it seems the error dialog is only showed sometimes because only sometimes makes the langpack removing fail (go figure), what's your case, or at least is what your log says, though you say you could managed to remove it successfully. That's not my case for example, though the error was in the uninstall log, it didn't make the uninstall fail (log says), hence didn't show the error dialog.
2 minor bugs removed.
mooms
Thx a lot!!!
You helped me a lot finding one of the most slippery bugs I have had with this method. I dropped a wrong single digit in 30SP2LNG_KB951847FIX.mst causing your (and everybody's using 3.0 SP2 langpacks) problem.
What's happening is that it was failing to remove 1 regvalue used as KB951847 fix for 3.5 SP1 family langpacks, only in the case 3.0 SP2 langpack was the last langpack from this family to be uninstalled (tricky). But the error appears not only in that circumstance, because it is triggered when the script to execute is not found, whether it has to be executed or not.
What's curious is that it seems the error dialog is only showed sometimes because only sometimes makes the langpack removing fail (go figure), what's your case, or at least is what your log says, though you say you could managed to remove it successfully. That's not my case for example, though the error was in the uninstall log, it didn't make the uninstall fail (log says), hence didn't show the error dialog.
I'm glad i have helped you!
Thank your for the update strel, everything is workin fine now!
Hi strel,
Everything works fine, thanks a lot of!
LG Ganesha
Everything works fine, thanks a lot of!
LG Ganesha
Strel,
Love this program.
For XP everything worked great with no problems.
For 2k, even though it says it will not process 3.0 SP2 and 3.5 SP1 it still tries to, and has problems. If I change the _SNMsynth.ini to not process those, everything works fine. In your previous version I didn't have to do this. Did a line of code go missing? Just wondering.
Thanks for all your hard work on this. You guys amaze me.
M2GD
Love this program.
For XP everything worked great with no problems.
For 2k, even though it says it will not process 3.0 SP2 and 3.5 SP1 it still tries to, and has problems. If I change the _SNMsynth.ini to not process those, everything works fine. In your previous version I didn't have to do this. Did a line of code go missing? Just wondering.
Thanks for all your hard work on this. You guys amaze me.
M2GD
Hi!
With the last version (20091105) WU still wants to install 951847 for DNF2SP2. I've attached logs. I'm using Vista SP2 and installing on XP SP3 (targetos=xp).
With the last version (20091105) WU still wants to install 951847 for DNF2SP2. I've attached logs. I'm using Vista SP2 and installing on XP SP3 (targetos=xp).
hi strel! i used to utilize the one tomcat prepared. sadly, he has left the scene (hopefully only temporarily) & today was my 1st time to employ what you have prepared (for use with HFSLIP) ... & for which i am thankful.
i encountered a roadblock though in my 1st run which shows:
i encountered a roadblock though in my 1st run which shows:
CODE
Cleaning work folder...
Checking .NET stuff to build installer(s)/addon(s) for XP...
ERROR: Choose the package to process 2.0 framework from. See _SNMsynth.ini
Press any key to exit.
at 1st run, i didn't attempt to change any of the settings contained in _SNMsynth; i tried to give it a go the 2nd time, remarking the other lines while leaving only the following:Checking .NET stuff to build installer(s)/addon(s) for XP...
ERROR: Choose the package to process 2.0 framework from. See _SNMsynth.ini
Press any key to exit.
CODE
PROCESS_DNF11=YES
PROCESS_DNF20=YES
PROCESS_DNF35_DNF20=YES
PROCESS_DNF35_DNF30=YES
PROCESS_DNF35_DNF35=YES
& at the latter part putting YES on some lines as may be seen below:PROCESS_DNF20=YES
PROCESS_DNF35_DNF20=YES
PROCESS_DNF35_DNF30=YES
PROCESS_DNF35_DNF35=YES
CODE
TARGETOS=XP
T13ADDON=YES
MERGE_FRAMEWORKS=YES
SILENT=
UPX_SFX=
COMPRESSION_RATIO=
below would also show the contents of my work folder (path included):T13ADDON=YES
MERGE_FRAMEWORKS=YES
SILENT=
UPX_SFX=
COMPRESSION_RATIO=
CODE
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_30SP#LNG_KB928416FIX.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_35SP1_KB963707FIX_NOFFADDONPROPERTY.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_35SP#_SLIMMING.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_KB951847FIX.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_REM_MSI_BLOCKING.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\7za.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\dotnetfx.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\dotnetfx35.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP1.1sp1-KB867460-X86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP1.1sp1-KB953297-X86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP20SP2-KB958481-x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP20SP2-KB974417-x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP30SP2-KB958483-x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP35SP1-KB958484-x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP35SP1-KB963707-x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NetFx20SP2_x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\upx.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\WindowsServer2003-KB971276-v2-x86-ENU.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\WindowsXP-KB971276-v3-x86-ENU.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_SNMsynth.ini
E:\Documents and Settings\KIKI\Desktop\SNMSynth\7zSD.sfx
E:\Documents and Settings\KIKI\Desktop\SNMSynth\msxml6.msi
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_SNMsynth.cmd
E:\Documents and Settings\KIKI\Desktop\SNMSynth\OUT1
E:\Documents and Settings\KIKI\Desktop\SNMSynth\TMP
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_20SP2_KB974417FIX.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_20SP#_SLIMMING.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_20SP#LNGbr_KB829019FIX.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_30SP2_REMFONTCACHEFIX.7z
NetFx20SP2_x86.exe is in the directory (tried moving the entire directory too to the root with the same results as i thought the long path could have something to do with it) but it doesn't seem to be recognized. i could be overlooking something ... your support will be greatly appreciated.
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_35SP1_KB963707FIX_NOFFADDONPROPERTY.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_35SP#_SLIMMING.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_KB951847FIX.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_REM_MSI_BLOCKING.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\7za.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\dotnetfx.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\dotnetfx35.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP1.1sp1-KB867460-X86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP1.1sp1-KB953297-X86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP20SP2-KB958481-x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP20SP2-KB974417-x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP30SP2-KB958483-x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP35SP1-KB958484-x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP35SP1-KB963707-x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NetFx20SP2_x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\upx.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\WindowsServer2003-KB971276-v2-x86-ENU.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\WindowsXP-KB971276-v3-x86-ENU.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_SNMsynth.ini
E:\Documents and Settings\KIKI\Desktop\SNMSynth\7zSD.sfx
E:\Documents and Settings\KIKI\Desktop\SNMSynth\msxml6.msi
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_SNMsynth.cmd
E:\Documents and Settings\KIKI\Desktop\SNMSynth\OUT1
E:\Documents and Settings\KIKI\Desktop\SNMSynth\TMP
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_20SP2_KB974417FIX.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_20SP#_SLIMMING.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_20SP#LNGbr_KB829019FIX.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_30SP2_REMFONTCACHEFIX.7z
My2GirlsDad
Oops, I used the pre-checking setting to trigger 3.5 SP1 family frameworks processes, bad idea. It only affects this case. Will be ready for next version, I'm testing now. Thx for the heads up.
Killgore
I claimed victory over KB951847FIX atomization too soon. I'm testing a new version fixing this now. Thx for you help.
Kiki Burgh
Your problem is simple, you have put 2 different .NET 2.0 framework sources in the work folder. The .ini file is set to process both what is not possible, but it is intended that you have only one of them in the work folder or you to change settings. You have to choose which one to process from.
Oops, I used the pre-checking setting to trigger 3.5 SP1 family frameworks processes, bad idea. It only affects this case. Will be ready for next version, I'm testing now. Thx for the heads up.
Killgore
I claimed victory over KB951847FIX atomization too soon. I'm testing a new version fixing this now. Thx for you help.
Kiki Burgh
Your problem is simple, you have put 2 different .NET 2.0 framework sources in the work folder. The .ini file is set to process both what is not possible, but it is intended that you have only one of them in the work folder or you to change settings. You have to choose which one to process from.
QUOTE (strel @ Nov 12 2009, 05:41 PM)
Kiki Burgh
Your problem is simple, you have put 2 different .NET 2.0 framework sources in the work folder. The .ini file is set to process both what is not possible, but it is intended that you have only one of them in the work folder or you to change settings. You have to choose which one to process from.
thanks for the reply strel. i'd like to know though how to set in _SNMsynth.ini which to choose. also, kindly clarify:Your problem is simple, you have put 2 different .NET 2.0 framework sources in the work folder. The .ini file is set to process both what is not possible, but it is intended that you have only one of them in the work folder or you to change settings. You have to choose which one to process from.
CODE
2.0 SP# can only be processed from 1 of the possible sources, individual or full redistributable packet. Choose.
i basically donwloaded those in the list (not including those that have been replaced) & put them in the work folder. i only had NetFx20SP2_x86.exe in the work folder in all the runs i did. if i already have the later ver (in this case, NetFx20SP2_x86.exe), would the script still seek for the older ver (NetFx20SP1_x86.exe)? tried having both in the work folder too, but still with the same result. as far as other 2.0s are concerned, i only had updates (NDP20SP2-KB958481-x86.exe & NDP20SP2-KB974417-x86.exe), both included in the list to download, in the work folder, as may be seen in my list above. would these cause the problem? do i need to take these out? lastly, did i do the right thing by remarking the rest while leaving only the "PROCESS MAIN PACKAGES" portion intact & answering YES to some under the "SPECIAL" segment. thanks again.
It is quite obvious you have PROCESS_DNF20 and PROCESS_DNF35_DNF20 to choose, anyway will be clarified for next version. If you want to process all the frameworks you can get rid of NetFx20SP2_x86.exe and to process 2.0 from dotnet35.exe without changing the .ini file.
Settings under PROCESS MAIN PACKAGES marked to YES only work if the related package is in the work folder, no matter the setting unless you have the packet.
If you have NetFx20SP1_x86.exe and NetFx20SP2_x86.exe in the work folder and PROCESS_DNF20=YES, 2.0 SP2 is processed and you are advised by the script (add a prefix e.g. -NetFx20SP2_x86.exe and NetFx20SP1_x86.exe will be processed). For dotnetfx35.exe, both versions have the same filename, you have to rename the one you don't want to process for both to be in the work folder.
Settings under PROCESS MAIN PACKAGES marked to YES only work if the related package is in the work folder, no matter the setting unless you have the packet.
If you have NetFx20SP1_x86.exe and NetFx20SP2_x86.exe in the work folder and PROCESS_DNF20=YES, 2.0 SP2 is processed and you are advised by the script (add a prefix e.g. -NetFx20SP2_x86.exe and NetFx20SP1_x86.exe will be processed). For dotnetfx35.exe, both versions have the same filename, you have to rename the one you don't want to process for both to be in the work folder.
thank you
hi strel! just need to confirm if file generated after running the script is with .7z extention (in my case: XPDNF11SP120SP230SP235SP1.7z about 42.9mb) which i will run in HFSLIP via svc pack? i've attached processdata.txt from OUT1 folder, in case you might need to view it (including files & settings i've used). your feedback will be greatly appreciated.
You are building an add-on for nLite-RVMI, for HFSLIP you need a switchless installer I think, you can extract it from the add-on. You didn't include 2.0 regular hotfixes so they will appear in the the update system in addition to KB951847 because KB958481 is not being applied.
thanks for the reply strel! that is strange ... apparently, i have downloaded all specified files from post # 1. as suggested, i only took out the ff to process 2.0 from 3.5:
NetFx20SP1_x86.exe
NetFx20SP2_x86.exe
below are the contents of my work directory:
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_20SP2_KB974417FIX.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_20SP#_SLIMMING.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_20SP#LNGbr_KB829019FIX.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_30SP2_REMFONTCACHEFIX.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_30SP#LNG_KB928416FIX.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_35SP1_KB963707FIX_NOFFADDONPROPERTY.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_35SP#_SLIMMING.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_KB951847FIX.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_REM_MSI_BLOCKING.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_SNMsynth.cmd
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_SNMsynth.ini
E:\Documents and Settings\KIKI\Desktop\SNMSynth\7za.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\7zSD.sfx
E:\Documents and Settings\KIKI\Desktop\SNMSynth\dotnetfx.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\dotnetfx35.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\msxml6.msi
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP1.1sp1-KB867460-X86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP1.1sp1-KB953297-X86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP20SP2-KB958481-x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP20SP2-KB974417-x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP30SP2-KB958483-x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP35SP1-KB958484-x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP35SP1-KB963707-x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\upx.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\WindowsServer2003-KB971276-v2-x86-ENU.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\WindowsXP-KB971276-v3-x86-ENU.exe
why were they not processed?
your suggestions will be greatly appreciated.
NetFx20SP1_x86.exe
NetFx20SP2_x86.exe
below are the contents of my work directory:
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_20SP2_KB974417FIX.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_20SP#_SLIMMING.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_20SP#LNGbr_KB829019FIX.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_30SP2_REMFONTCACHEFIX.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_30SP#LNG_KB928416FIX.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_35SP1_KB963707FIX_NOFFADDONPROPERTY.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_35SP#_SLIMMING.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_KB951847FIX.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_REM_MSI_BLOCKING.7z
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_SNMsynth.cmd
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_SNMsynth.ini
E:\Documents and Settings\KIKI\Desktop\SNMSynth\7za.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\7zSD.sfx
E:\Documents and Settings\KIKI\Desktop\SNMSynth\dotnetfx.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\dotnetfx35.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\msxml6.msi
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP1.1sp1-KB867460-X86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP1.1sp1-KB953297-X86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP20SP2-KB958481-x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP20SP2-KB974417-x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP30SP2-KB958483-x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP35SP1-KB958484-x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP35SP1-KB963707-x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\upx.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\WindowsServer2003-KB971276-v2-x86-ENU.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\WindowsXP-KB971276-v3-x86-ENU.exe
why were they not processed?
your suggestions will be greatly appreciated.
NetFx20SP1_x86.exe and NetFx20SP2_x86.exe are not going to be processed if 2.0 SP# framework is being processed from dotnetfx35.exe.
QUOTE (strel @ Nov 21 2009, 12:00 AM)
You didn't include 2.0 regular hotfixes so they will appear in the the update system in addition to KB951847 because KB958481 is not being applied.
hi strel! this was what my inquiry was about ... how come the updates were not processed even if these were included in my run? your feedback will be greatly appreciated.
Any NDP20SP2-KB*.exe present should be processed if any 2.0 framework is being processed, is it not your case?
Better you include NDP20SP2-KB971111-x86.exe or it will appear in the update system.
Better you include NDP20SP2-KB971111-x86.exe or it will appear in the update system.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.