[Kiki Burgh]

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.

Attached File(s)

•  PROCESSDATA.TXT (3.79K)
  Number of downloads: 10

This post has been edited by Kiki Burgh: 19 November 2009 - 08:12 PM

[strel]

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.

This post has been edited by strel: 20 November 2009 - 10:05 AM

[Kiki Burgh]

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.

This post has been edited by Kiki Burgh: 20 November 2009 - 05:06 PM

[strel]

NetFx20SP1_x86.exe and NetFx20SP2_x86.exe are not going to be processed if 2.0 SP# framework is being processed from dotnetfx35.exe.

[Kiki Burgh]

strel, on Nov 21 2009, 12:00 AM, said:

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.

[strel]

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.

[Kiki Burgh]

hi strel! as you could see in the processdata.txt i attached previously, i had:
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP20SP2-KB958481-x86.exe
E:\Documents and Settings\KIKI\Desktop\SNMSynth\NDP20SP2-KB974417-x86.exe
then you posted:

strel, on Nov 21 2009, 12:00 AM, said:

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.

i wonder if i had them in there, why were these updates to 2.0 not processed. based on my selections:
;PROCESS_DNF20=YES
PROCESS_DNF35_DNF20=YES
2.0 is being processed in this case too, right? so i guess have set everything right (or so i believe). as for KB951847, i read from the 1st post this is an ad-hoc update:

strel, on Dec 26 2008, 03:50 AM, said:

[*]Avoid win/ms update to push .NET 3.5 SP1 Family update KB951847 for WXP/2K3. KB951847 is an ad-hoc update (variable size depending on components included) prompted via win/ms update to complete your own installed .NET set with the parts not installed of the following set (3.5 SP1 family):

as per http://support.micro....com/kb/951847/, this was supposed to have been addressed in .NET Framework 3.5 Service Pack 1. incidentally, also had this in my work directory after the initial run of the script:
E:\Documents and Settings\KIKI\Desktop\SNMSynth\_KB951847FIX.7z
do i include KB951847 still?
i just want to be able to utilize your tool & come up with the best (& complete) AIO .net

strel, on Nov 22 2009, 12:21 AM, said:

Better you include NDP20SP2-KB971111-x86.exe or it will appear in the update system.

is this not for 2k as per instructions from the 1st post? should i still include it? again, i appreciate the feedback. cheers!

This post has been edited by Kiki Burgh: 21 November 2009 - 05:25 PM

[strel]

Don't use ; before settings in the .ini file, the script makes all possible settings yes by default unless the .ini file set another value (empty included), this was probably causing you errors when you put NetFx20SP1_x86.exe and/or NetFx20SP2_x86.exe along with dotnetfx35.exe in the work folder. I should change this.

Apart from that, when I set correctly a 2.0 framework to be processed from one possible source, the script process 2.0 hotfixes without problems in my case. I'm getting messages:
Processing NDP20SP2-KB958481-x86.exe...
Processing NDP20SP2-KB974417-x86.exe...

About KB951847, yes is an ad-hoc update for 3.5 family, but this family includes KB958481. And you're right KB971111 is a 2K only hotfix.

This post has been edited by strel: 21 November 2009 - 06:33 PM

[Kiki Burgh]

strel, on Nov 22 2009, 08:17 AM, said:

Don't use ; before settings in the .ini file, the script makes all possible settings yes by default unless the .ini file set another value (empty included), this was probably causing you errors when you put NetFx20SP1_x86.exe and/or NetFx20SP2_x86.exe along with dotnetfx35.exe in the work folder.

 
[font="Lucida Console"][color="#0000FF"][b];[/b][/color]PROCESS_DNF20=YES[/font] 

i just thought that by putting ;, it would bypass that line. i'll just leave it empty then. apart from this, i didn't make any change from the default settings of _SNMsynth.ini when initially running _SNMsynth.cmd (except for some under SPECIAL portion by setting values of the following to:

 
[font="Lucida Console"]TARGETOS=[color="#0000FF"]XP[/color]
T13ADDON=[color="#0000FF"]YES[/color]
MERGE_FRAMEWORKS=[color="#0000FF"]YES[/color]
SILENT=
UPX_SFX=
COMPRESSION_RATIO=[/font] 

also, when you suggested to take out NetFx20SP1_x86.exe & NetFx20SP2_x86.exe, i removed these from the work folder (so i didn't have these 2 in there anymore when i made my following runs) to process 2.0 instead from 3.5 with this default setting:
PROCESS_DNF35_DNF20=YES

Kiki Burgh, on Nov 21 2009, 06:56 AM, said:

... 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

strel, on Nov 21 2009, 10:53 AM, said:

NetFx20SP1_x86.exe and NetFx20SP2_x86.exe are not going to be processed if 2.0 SP# framework is being processed from dotnetfx35.exe.

i'll try a fresh run again. the only change though will be your latest suggestion of not using ;. these are the default settings i see in the .ini:

 
; -------  [font="Lucida Console"]PROCESS MAIN PACKAGES
; These settings request processing for .NET 1.1 (dotnetfx.exe), 2.0 SP1/SP2 (NetFx20SP1_x86.exe/NetFx20SP2_x86.exe, if both are
; present SP2 is processed) and each one of 2.0 SP1/SP2,; 3.0 SP1/SP2 and 3.5/3.5 SP1 inside any of the dotnetfx35.exe (3.5/3.5 SP1
; respectively). 2.0 SP# can only be processed from 1 of the possible sources, individual or full redistributable packet. Choose.

PROCESS_DNF11=YES
[color="#0000FF"]PROCESS_DNF20=YES[/color]
[color="#0000FF"]PROCESS_DNF35_DNF20=YES[/color]
PROCESS_DNF35_DNF30=YES
PROCESS_DNF35_DNF35=YES[/font] 

as observed, PROCESS_DNF20 is set to YES as well as PROCESS_DNF35_DNF20 (set to YES too). my apologies, but should this not be modified from the current default settings to avoid conflict (both being set to YES), given that common users could either have NetFx20SP1_x86.exe &/or NetFx20SP2_x86.exe present while dotnetfx35.exe exists too (just like what happened to me) or both being neither present in the work folder prior to the initial run?

strel, on Nov 22 2009, 08:17 AM, said:

About KB951847, yes is an ad-hoc update for 3.5 family, but this family includes KB958481.

i have KB958481 in the work folder (as well as KB951847 - Microsoft .NET Framework 3.5 Service pack 1 (Full Package): dotnetfx35.exe) but you said it wasn't processed.
appreciate your patience strel! cheers!

This post has been edited by Kiki Burgh: 23 November 2009 - 12:04 AM

[strel]

The script set all possible/needed settings not defined by .ini file to be able to run if the .ini file is not present. I recently fix the script for the .ini file to adapt to .ini standards but didn't fix this issue, i.e. after ; the setting is now bypassed in the .ini file but the script set default value later anyway. I'll change this for the next version.

About NetFx20SP1_x86.exe & NetFx20SP2_x86.exe, keep them if you want to, along with dotnetfx35.exe, but then change .ini settings to process 2.0 framework only from one source (single or redistributable). Both 2.0 framework process settings are yes at the same in the original .ini file, because It is not expected the user to download 2 different sources (single and redistributable) to process 2.0 framework from (and in that case an error message is displayed). It is intended for the user to be able to start the process without changing the .ini file for the general use. I'll keep it.

[Kiki Burgh]

strel, on Nov 23 2009, 05:08 PM, said:

I'll change this for the next version.

i'll wait for your next ver

strel, on Nov 23 2009, 05:08 PM, said:

Both 2.0 framework process settings are yes at the same in the original .ini file, because It is not expected the user to download 2 different sources (single and redistributable) to process 2.0 framework from (and in that case an error message is displayed).

just a suggestion, perhaps it must be noted in the 1st post not to have both present.

strel, on Nov 23 2009, 05:08 PM, said:

It is intended for the user to be able to start the process without changing the .ini file for the general use.

precisely what i did in my initial run (not modifying anything) ... the only deviation being was the presence of both (NetFx20SP2_x86.exe & dotnetfx35.exe) sources in the work folder. again, noting in the 1st post would help. or perhaps, a modification in the script to skip or ignore specific line(s) if both are present but to be processed only from 1 source - dotnetfx35.exe being the latest (which incidentally contains .net 2.0 already). thanks again strel!

This post has been edited by Kiki Burgh: 23 November 2009 - 07:58 PM

[Kiki Burgh]

hi strel! how about this for a result as per your suggestion: XPDNF11SP120SP230SP235SP1.7z (abt 42.9mb)? below shows contents of the work folder (paths included):
E:\SNMSynth\OUT1
E:\SNMSynth\OUT1\PROCESSDATA.TXT
E:\SNMSynth\OUT1\XPDNF11SP120SP230SP235SP1.7z
E:\SNMSynth\_20SP2_KB974417FIX.7z
E:\SNMSynth\_20SP#_SLIMMING.7z
E:\SNMSynth\_20SP#LNGbr_KB829019FIX.7z
E:\SNMSynth\_30SP2_REMFONTCACHEFIX.7z
E:\SNMSynth\_30SP#LNG_KB928416FIX.7z
E:\SNMSynth\_35SP1_KB963707FIX_NOFFADDONPROPERTY.7z
E:\SNMSynth\_35SP#_SLIMMING.7z
E:\SNMSynth\_KB951847FIX.7z
E:\SNMSynth\_REM_MSI_BLOCKING.7z
E:\SNMSynth\7za.exe
E:\SNMSynth\dotnetfx.exe
E:\SNMSynth\dotnetfx35.exe
E:\SNMSynth\NDP1.1sp1-KB867460-X86.exe
E:\SNMSynth\NDP1.1sp1-KB953297-X86.exe
E:\SNMSynth\NDP20SP2-KB958481-x86.exe
E:\SNMSynth\NDP20SP2-KB974417-x86.exe
E:\SNMSynth\NDP30SP2-KB958483-x86.exe
E:\SNMSynth\NDP35SP1-KB958484-x86.exe
E:\SNMSynth\NDP35SP1-KB963707-x86.exe
E:\SNMSynth\upx.exe
E:\SNMSynth\WindowsServer2003-KB971276-v2-x86-ENU.exe
E:\SNMSynth\WindowsXP-KB971276-v3-x86-ENU.exe
E:\SNMSynth\_SNMsynth.ini
E:\SNMSynth\7zSD.sfx
E:\SNMSynth\msxml6.msi
E:\SNMSynth\_SNMsynth.cmd

E:\SNMSynth\20091105_SNMsynth.zip

i've yet to try the processed product though via svcpack in my UA install. i copied from the cmd window what went on as may be seen below:

 
Cleaning work folder...

Checking .NET stuff to build installer(s)/addon(s) for XP...

NOTE: 3.0 SP2 XPS driver will be updated with WindowsXP-KB971276-v3-x86-ENU.exe
patched with the latest files from WindowsServer2003-KB971276-v2-x86-ENU.exe

** Processing .NET 1.1 package...
Processing NDP1.1sp1-KB867460-X86.exe...
Processing NDP1.1sp1-KB953297-X86.exe...

** Processing .NET 3.5 SP1 redistributable package...
** Processing .NET 2.0 SP2 portion...
Processing NDP20SP2-KB958481-x86.exe...
Processing NDP20SP2-KB974417-x86.exe...
** Processing .NET 3.0 SP2 portion...
Updating XPS driver with latest files from XP+2K3 KB971376...
Processing NDP30SP2-KB958483-x86.exe...
** Processing .NET 3.5 SP1 portion...
Processing NDP35SP1-KB958484-x86.exe...
Processing NDP35SP1-KB963707-x86.exe...

Creating merged .NET 1.1 SP1, .NET 2.0 SP2,
.NET 3.0 SP2, .NET 3.5 SP1 passive installer....
Creating merged .NET 1.1 SP1, .NET 2.0 SP2,
.NET 3.0 SP2, .NET 3.5 SP1 passive add-on...

DONE!

Remove .\TMP folder? (Y/N) Y

Cleaning work folder... 

kindly see if everything went well as far as the process is concerned. pls see attached text file (PROCESSDATA.txt) too for your review. thanks!

Attached File(s)

•  PROCESSDATA.TXT (4.28K)
  Number of downloads: 2

This post has been edited by Kiki Burgh: 24 November 2009 - 03:06 AM

[Kiki Burgh]

strel, on Nov 21 2009, 12:00 AM, said:

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.

hi strel! quick Q: wouldn't i need entries_XPDNF11SP120SP230SP235SP1.ini if i extract only XPDNF11SP120SP230SP235SP1.exe from the SVCPACK folder inside the compressed XPDNF11SP120SP230SP235SP1.7z to HFSVCPACK (of HFSLIP)? i'll ask the same in HFSLIP forum. thanks!

[Kiki Burgh]

hi strel! pardon me for asking but wouldn't your script be more complete if it included .NET Framework 1.0 SP3? or is it not necessary?
kindly look at my other posts lately too. i'll wait for your feedback.
thanks!

This post has been edited by Kiki Burgh: 25 November 2009 - 01:36 AM

[mooms]

.net 1.0 is superseded by .net 1.1. Both have very little use today.

[Sp0iLedBrAt]

How I wish you were right, mooms. But the STUPID Encarta 2005 and 2006 don't care if you have .NET 2.0 or .NET 3.5 on you PC. It just goes ahead and installs .NET 1.1 and all you can do is whine, like I am doing now.

[Kiki Burgh]

mooms, on Nov 26 2009, 03:55 AM, said:

.net 1.0 is superseded by .net 1.1. Both have very little use today.

hi mooms! i have a few addon's (there could be others) that require .net 1.0 SP3 (i.e., Windows XP Tablet PC 2005 (English) by CODYQX4 (although the maker has already provided a modded 1:)). thanks!

[strel]

New version released.

Bugs fixed and new features added, specially support to build RunOnceEx add-ons.
Let me know if you find bugs.

Enjoy!



Kiki Burgh
You better use new version. It seems you are in the right path with your process. I'm not a user of HFSLIP, but I think it need switchless installers for HFSVCPACK, so you'll need .exe installer(s) only. And 1.1 superseeded 1.0 SP3.

This post has been edited by strel: 27 November 2009 - 01:45 PM

[Kiki Burgh]

strel, on Nov 28 2009, 02:00 AM, said:

New version released.

Kiki Burgh
You better use new version. It seems you are in the right path with your process. I'm not a user of HFSLIP, but I think it need switchless installers for HFSVCPACK, so you'll need .exe installer(s) only. And 1.1 superseeded 1.0 SP3.

appreciate this strel!

EDIT:just wanted to verify this part:

 
; -------  SPECIAL
; -- ALSOINSTALLERS=YES beside add-on(s) (any XXXADDONS=YES), also output switchless installer(s) compatible with HFSLIP. 

setting this to YES is the one for me, right as i use hfslip? just need to rename XPDNF11SP120SP230SP235SP1.exe to something like DNAIO.exe to conform to the 8.3 file name format. already did a "hiccup-less" run btw. just merely confirming ... thanks again.

This post has been edited by Kiki Burgh: 27 November 2009 - 10:31 PM

[My2GirlsDad]

strel, on Nov 27 2009, 01:00 PM, said:

New version released.

Bugs fixed and new features added, specially support to build RunOnceEx add-ons.
Let me know if you find bugs.

Enjoy!

Just tested your new version for 2k and XP. It worked flawlessly.

Thanks for fixing the problem when running for 2k.

Another great job, strel. You rock!

M2GD