madpenguin Posted October 31, 2009 Posted October 31, 2009 Something isn't right for me.... I've tried various settings in the SNM config file but nlite just refuses to add it. It'll work for 30 or 40 seconds like everything is OK but then I always get that error...--- WORK FOLDER CONTENT: Volume in drive C has no label. Volume Serial Number is C81D-239A Directory of C:\Documents and Settings\Madpenguin\Desktop\20091029_SNMsynth10/31/2009 03:29 PM <DIR> .10/31/2009 03:29 PM <DIR> ..10/23/2009 09:32 PM 4,181 _20SP#_SLIMMING.7z10/29/2009 02:49 PM 1,369 _20SP#LNGbr_KB829019FIX.7z10/28/2009 09:46 AM 1,429 _20SP2_KB974417FIX.7z09/27/2009 09:34 AM 1,109 _30SP#_REMFONTCACHEFIX.7z09/27/2009 09:35 AM 1,626 _30SP#LNG_KB928416FIX.7z10/19/2009 08:19 PM 16,941 _35SP#_SLIMMING.7z10/29/2009 02:26 PM 1,009 _35SP1_KB963707FIX_NOFFADDONPROPERTY.7z09/27/2009 09:33 AM 3,474 _KB951847FIX.7z10/09/2009 07:54 PM 3,097 _REM_MSI_BLOCKING.7z10/29/2009 04:32 PM 87,163 _SNMsynth.cmd10/31/2009 03:27 PM 3,961 _SNMsynth.ini02/03/2009 12:21 PM 536,064 7za.exe09/14/2009 02:14 AM 57,344 7zSD.sfx05/31/2009 01:47 PM 24,265,736 dotnetfx.exe05/31/2009 01:47 PM 10,703,680 NDP1.1sp1-KB867460-X86.exe10/13/2009 08:31 PM 14,120,896 NDP1.1sp1-KB953297-X86.exe05/31/2009 01:50 PM 8,981,856 NDP20SP2-KB958481-x86.exe10/13/2009 08:32 PM 11,459,928 NDP20SP2-KB974417-x86.exe05/31/2009 01:49 PM 25,001,480 NetFx20SP2_x86.exe10/31/2009 03:29 PM 26 PROCESSDATA.TXT09/27/2009 05:04 PM 283,648 upx.exe 21 File(s) 95,536,017 bytes 2 Dir(s) 396,956,704,768 bytes free--- _SNMSYNTH.ini SETTINGS USED:PROCESS_DNF11=YESPROCESS_DNF20=YESPROCESS_DNF35_DNF20=YESPROCESS_DNF35_DNF30=YESPROCESS_DNF35_DNF35=YESDNF20_VC8_RUNTIME=YESDNF20_OFFICE2K3_DEBUGGER=YESDNF30_RGB_RASTERIZER=YESDNF30_WIC=YESDNF30_MSXML6=YESDNF30_XPS=YESDNF35_FF_ADDON=YESDNF35_VC9_RUNTIME=YESPROCESS_LNG_DNF11=YESPROCESS_LNG_DNF20=YESPROCESS_LNG_DNF35_DNF20=YESPROCESS_LNG_DNF35_DNF30=YESPROCESS_LNG_DNF35_DNF35=YESWINXP=YEST13ADDON=NOMERGE_FRAMEWORKS=YESSILENT=YESUPX_SFX=YESCOMPRESSION_RATIO=HIGHER--- TMP FOLDER CONTENT: Volume in drive C has no label. Volume Serial Number is C81D-239A Directory of C:\Documents and Settings\Madpenguin\Desktop\20091029_SNMsynth\TMP10/31/2009 03:31 PM <DIR> .10/31/2009 03:31 PM <DIR> ..09/24/2009 07:22 PM 9,728 20SP2_KB951847FIX.mst10/28/2009 04:45 AM 5,632 20SP2_KB974417FIX.mst10/09/2009 01:24 PM 4,096 20SP2_REM_MSI_BLOCKING.mst10/23/2009 04:15 PM 10,752 20SP2_REM_W2K_COMPONENTS.mst09/24/2009 07:28 PM 6,144 20SP2LNG_KB951847FIX.mst10/31/2009 03:31 PM 83 config.txt10/31/2009 03:31 PM <DIR> DNF10/31/2009 03:30 PM 9 DNF11REM.TXT10/31/2009 03:31 PM 20 DNF20REM.TXT10/31/2009 03:30 PM 117 INSTALL1.CMD10/31/2009 03:30 PM 132 INSTALL2.CMD10/31/2009 03:31 PM 416 INSTCOMMONEND.CMD10/31/2009 03:31 PM 181 INSTREGDOWN.CMD10/31/2009 03:31 PM 249 INSTREGDOWN2.CMD10/31/2009 03:33 PM 26,252,194 TEMP.7z10/31/2009 03:29 PM <DIR> TMP110/31/2009 03:29 PM <DIR> TMP210/31/2009 03:29 PM <DIR> TMP310/31/2009 03:31 PM <DIR> TMP410/31/2009 03:31 PM 220 TRANSFORMDB.vbs 15 File(s) 26,289,973 bytes 7 Dir(s) 396,461,944,832 bytes free
strel Posted October 31, 2009 Author Posted October 31, 2009 (edited) Please use attachment better for a file that long. nLite doesn't accept your file because you are trying to integrate a switchless installer and not an nLite add-on. To build an add-on you should have used T13ADDON=YES setting in the .ini file. Edited October 31, 2009 by strel
madpenguin Posted November 1, 2009 Posted November 1, 2009 I did try that setting. Gave me the same error and also an .exe file, which I expected a 7zip file like previous versions. Let me try it again but I'm positive I had T13ADDON=YES the first time around. It produced an .exe which nlite refused to use....Thanks for the help strel...
madpenguin Posted November 1, 2009 Posted November 1, 2009 (edited) Alright.... I changed that option back and your right. A second command window came up that said it was converting to a 7zip file and indeed I now have a "DNF11SP120SP230~4%DNF30LNGSTR35~4%DNF35LNGSTR.7z" in the OUT1 directory.Sorry about jumping the gun but I could have sworn I used that option because I specifically read the comments. We'll see how the nlite integration and format/fresh install goes with regards to KB974417 still showing up on Automatic Updates or not.Thanks again Strel for your hard work on SNMsynthPROCESSDATA.TXT Edited November 1, 2009 by madpenguin
Dumpy Dooby Posted November 1, 2009 Posted November 1, 2009 Dumpy DoobyI see, OK, suppose all files to extract are zip, I'll check it to include the switch. Thx.I suppose 35SP1_KB963707FIX_NOFFADDONPROPERTY.mst appears in .\TMP folder, is that right?I have not defined any timeframe limitation for the script subprocesses. Waiting for your tests.I ran it all the way through a couple times. Both times everything came out fine. I have no idea what caused that error message initially. If it ever shows up again, I'll go through everything and see what happened.
madpenguin Posted November 1, 2009 Posted November 1, 2009 (edited) Thanks Strel. Everything seemes to work fine with the new version. You can look at my last attachment to see what files I processed but it's basically an up-to-date 1&2 addon for nlite. I added the .7z file after 60 or so other hotfixes, no problems there as someone earlier suggested. Windows update doesn't list it as me needed it.It appears, atleast for my needs, that your latest version works perfectly. I haven't compared file versions or gone indepth to make sure all the hotfixes were applied correctly during the windows install but for now, I'll just assume they have.I've also noticed that firefox .NET assistant update is missing in Automatic updates. Huzzah for who ever made that one happen. Was really getting tired of looking at it.Thanks again for all the hard work. Edited November 1, 2009 by madpenguin
madpenguin Posted November 2, 2009 Posted November 2, 2009 (edited) FYI, my new nlite CD worked perfect. Did a format and freash install and only have the updates I intentionally left out. The new version of SNMsynth seems to work and do what I need it to do.Thanks much. Edited November 2, 2009 by madpenguin
Glowy Posted November 2, 2009 Posted November 2, 2009 GlowyI built 3.0 SP2+3.5 SP1 merged installers with exactly the same .ini file settings and with the same files in the work folder as you. Then I proceed to install and the error didn't appear. Can you check again even repeating the process or so?Weird thing is when i run it from an existing installation it runs fine.When I use it from HFGUIRUNONCE (I'm using HFSLIP) I get the error.
Sp0iLedBrAt Posted November 2, 2009 Posted November 2, 2009 (edited) I compared the versions; mscordacwks.dll has 2.0.50727.3082 version, which should be at least 2.0.50727.3603.I checked if 20SP2_KB974417FIX.mst was in the folder; affirmative.I'm attaching PROCESSDATA.txt so you can check it out and point me to possible errors in my procedure.Thank you for your prompt reply.I did another one incorporating what is said above plus a few changes; the result is still the same (see post #490). I'm also attaching the log inside OUT1 from this latest experiment.Edit: I extracted the package and verified that the necessary files (newer versions in accordance with MS's description) are indeed inside, so the question is why aren't they updated in the Microsoft.NET\Framework\v2.0.50727\ folder. Edited November 2, 2009 by Sp0iLedBrAt
Glowy Posted November 2, 2009 Posted November 2, 2009 (edited) There probably is something wrond in the KB971276 code.I had to put WINXP=YES in the ini or the KB971276 updates did not get processed.Starting up a VM installation to test if the file not found error dissapeared.At least the file exists in the archive now (DNF30\XPS\update\update.exe) Edited November 2, 2009 by Glowy
strel Posted November 2, 2009 Author Posted November 2, 2009 (edited) SNMsynth 20091029 presents important bugs, I'd recommend you to not use it except for testing purposes. Hopefully will fix all bugs for the next verion soon.thnx4thepenWhat method did you used to install? Did you installed 3.0 from win setup? At what time?zorro1Thx for your help, I've found and fixed the 1.1 language bug, next version will handle it.Sp0iLedBrAtI'm not getting KB974417 in win/ms update after using an SNMsynth installer over an installed XP. Are you sure is that KB# and not KB951847?, because there's a bug with the second that I managed to fix, next version will handle it. In addition, the right files from KB974417 are applied both in my 2.0 SP2 installer and in %systemroot%\Microsoft.NET\Framework\v2.0.50727\ folder. Check this folder is removed when you remove 2.0.GlowyYou said you need to set WINXP=yes in .ini file to make the script process KB971276. This sounds strange to me, I don't think it is related with target OS setting in the script, but new method for detecting host OS (which define target OS, in case .ini file setting is not defined) is being used with 20091029 SNMsynth, and though I'm confident with it, you should check it is not failing. The 2nd line after you run the script, indicates the target OS version for the installers being built. If you find any error on this let me know. Edited November 2, 2009 by strel
thnx4thepen Posted November 2, 2009 Posted November 2, 2009 SNMsynth 20091029 presents important bugs, I'd recommend you to not use it except for testing purposes. Hopefully will fix all bugs for the next verion soon.ok! thnx4thepenWhat method did you used to install? Did you installed 3.0 from win setup? At what time?I simply run the installer created in a Virtual Machine (VirtualBox 2.2.2 Windows XP SP3 full updated).I used only the "dotnetfx35.exe", the language pack and the updates.PS when the procedure is finished I did clean the .\TMP folder
Glowy Posted November 3, 2009 Posted November 3, 2009 (edited) When omitting the winxp=yes veriable the output is:Checking .NET stuff to build installer(s)/addon(s) for ..."net config work" returns "Softwareversie Windows 2002"When I change the "TOKENS=4" in "TOKENS=3" in the OS detection part, it detects correctly, so I think it's a language issueBecause the english output is "Software version Windows 2002", there is an extra space. Edited November 3, 2009 by Glowy
Glowy Posted November 3, 2009 Posted November 3, 2009 Building the packages went fine using winxp=yes, but in WU KB951847 and language pack for .NET 1.1 are back
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now