Jump to content

Silent .NET Maker synthesized 20100118 - W2K/XP/2K3 x86


strel

Recommended Posts

Oh, it happens with all MSI files, not just the .NET Frameworks. I was asking you because you seem to know your way around MSIEXEC. In any event, since I use a VBS file to run my installers, I just have it open the log file, and I do a string replace of Chr(0) with "" to get rid of all the NULLs. It works fantastically.

Link to comment
Share on other sites


strel

Can you update your script so this reg key gets created ?

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\9E0DE89293FE9BB33898F24ED18CCF08]
"State"=dword:00000001

And please remove this !

WARNING: NDP1.1sp1-KB928366-X86.exe regular hotfix is not present.

Edited by atolica
Link to comment
Share on other sites

New version released!

It is a major update.

Fixes has been atomized, and grouped, folder structure has changed to adapt to the new situation, TMP folder now hosts all temporary files. Many changes has been made in the script to support all that.

It gives full support for the new regular and restricted hotfixes. It finally implements complete YumeYao's methods. Added: slimming down 3.5 SP# langpacks, removing frameworks subcomponents, and other optimizations.

It solves all bugs documented, and one new important about generic fixes for langpacks not applying on some languages because of a codepage conflict between the transform and the installer. Any of you probably have experienced this simptoms but not reported it, this bug has been around many months.

I've included links to many ready to use .NET releases in the guide.

Testing is a growing task as there are many new paths of execution. So despite I have made a lot of tests, for sure some bugs will appear. I rely on you to help me remove them.

See you later. :zzz:

Enjoy! :thumbup

Edited by strel
Link to comment
Share on other sites

As of 7-zip 9.07, you must specify the type during extraction of executable files. Otherwise it will extract each individual resource and binary section. I already put in a suggestion to make that action switch-activated, but he says he'd rather have use the type switch if they don't like it.

I might have posted this earlier. Sorry if I'm repeating myself.

Link to comment
Share on other sites

Test results under Windows 2000

For .Net 1.1 sp1

File processing under SNM:

dotnetfx.exe

NDP1.1sp1-KB867460-X86.exe

NDP1.1sp1-KB953297-X86.exe Not processed, shows on Windows update

NDP1.1sp1-KB971108-X86.exe

Also the AddOn creates the following error:

For .Net 2.0 sp2

File processing under SNM:

NetFx20SP2_x86.exe

NDP20SP2-KB958481-x86.exe Not processed

NDP20SP2-KB974417-x86.exe Not processed, shows on Windows update

NDP20SP2-KB971111-x86.exe

Link to comment
Share on other sites

Got this while running _SNMsynth.cmd.

b842ad567485b2fd26b0c13e475ad84c053414a6.png

Again, that's not during an installation. That's during the building process itself. Below are my settings:

; _SNMsynth.cmd 20091029 PROCESS SETTINGS.   ----   Complete guide at:   [url="http://www.msfn.org/board/index.php?showtopic=127790"]http://www.msfn.org/board/index.php?showtopic=127790[/url]

; Unless expressely stated, settings have 1, case insensitive, working value: "YES" meaning yes only if related packet is present.

; ------- 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
PROCESS_DNF20=
PROCESS_DNF35_DNF20=YES
PROCESS_DNF35_DNF30=YES
PROCESS_DNF35_DNF35=YES

; ------- SUBCOMPONENTS OF .NETFX 2.0 --->> DON'T TOUCH THIS UNLESS YOU KNOW WHAT YOU'RE DOING!
; These settings let you remove Visual C 8 Runtime Libraries and Office 2003 Crash Reporting Tools from installers/add-ons
; containing 2.0 SP# framework, useful for installing them from another updated source, see guide.

DNF20_VC8_RUNTIME=NO
DNF20_OFFICE2K3_DEBUGGER=NO

; ------- SUBCOMPONENTS OF .NETFX 3.0 --->> DON'T TOUCH THIS UNLESS YOU KNOW WHAT YOU'RE DOING!
; These settings let you remove those 3.0 framework pre-required components from your installer/add-on containing 3.0 SP# framework,
; useful if your OS have them installed, like WIC in XP SP3, or for installing them from another updated source. See guide.

DNF30_RGB_RASTERIZER=NO
DNF30_WIC=NO
DNF30_MSXML6=NO
DNF30_XPS=NO

; ------- SUBCOMPONENTS OF .NETFX 3.5 --->> DON'T TOUCH THIS UNLESS YOU KNOW WHAT YOU'RE DOING!
; These settings let you remove .NET Framework Assistant 1.0 add-on for Firefox from installers containing 3.5 SP1 framework and
; Visual C 9 Runtime Libraries from installers with .NET 3.5 SP#, useful for installing them from another updated source. See guide.

DNF35_FF_ADDON=YES
DNF35_VC9_RUNTIME=NO

; ------- PROCESS LANGUAGE PACKS
; "YES" here means yes only if both framework and langpack are present and set to be processed. These settings request langpacks
; processing for .NET 1.1 (langpack.exe), .NET 2.0 SP1/SP2 (from NetFx20SP1_x86*.exe/NetFx20SP2_x86*.exe), and each one of 2.0 SP1/SP2,
; 3.0 SP1/SP2 and 3.5 SP0/SP1 langpacks inside 3.5/3.5 SP1 redistributable langpack (dotnetfx35langpack_x86*.exe, same filename)

PROCESS_LNG_DNF11=YES
PROCESS_LNG_DNF20=YES
PROCESS_LNG_DNF35_DNF20=YES
PROCESS_LNG_DNF35_DNF30=YES
PROCESS_LNG_DNF35_DNF35=YES

; ------- SPECIAL
; -- Add WIN2K=YES / WINXP=YES / WIN2K3=YES define the target OS version for your ad-hoc installer(s)/add-on(s), instead of the your
; host OS version. Installer(s)/add-on(s) for each OS version are incompatible with another OS versions.
; -- T13ADDON=YES builds T-13 nLite/RVMI add-on(s) packing the .EXE installer(s) (HFSLIP compatible), so you can extract them later.
; -- MERGE_FRAMEWORKS=YES merge all frameworks that are being processed into a unique installer/add-on, instead of, otherwise
; single framework version installer(s). Merged installers/add-ons keep installing priorities, see guide.
; -- SILENT=YES makes quiet switchless installer(s)/add-on(s) instead of, otherwise, default passive one(s) (progress bars with
; no cancel button). The switchless default verbosity of installer(s)/add-on(s) can be modified at run with switches. See guide.
; -- UPX_SFX=YES Adds 50KB extra compression on .sfx module with UPX. False positives on eSafe and Comodo antivirus appear. See guide.
; -- COMPRESSION_RATIO=HIGHER / HIGH / NONE , reduce compression from, otherwise, HIGHEST setting. Useful for low RAM or slow machines.
; On the fly, you can restart compression subprocess with the next lower ratio in the previous scale.

WIN___=
T13ADDON=
MERGE_FRAMEWORKS=YES
SILENT=
UPX_SFX=NO
COMPRESSION_RATIO=NONE

Edited by Dumpy Dooby
Link to comment
Share on other sites

As of 7-zip 9.07, you must specify the type during extraction of executable files. Otherwise it will extract each individual resource and binary section. I already put in a suggestion to make that action switch-activated, but he says he'd rather have use the type switch if they don't like it.

I might have posted this earlier. Sorry if I'm repeating myself.

Did you missed the thread to post to?

About the other post with the error not finding FF addon file, I have to say I've seen this error ago but I though it was completely solved. In fact I cannot recreate the error, using exactly the same settings in .ini file. Can I have the file list? Any other useful info to recreate this condition?

Kurt_Aust

The add-on error is only a TMP\ prefix I dropped in the wrong place.

About the difficulties with hotfixes, when you say "not processed" I think you're meaning not installing, am I wrong? Anyway, were there any problems during building process? Have you checked a verbose output after removing ECHO OFF in the script? I have not made test yet, but a priori sounds strange to me, the way hotfixes are applied has not changed, and what is more strange is that only some of them are missing. Any extra info to help me recreate it?

Link to comment
Share on other sites

Well here is the results of the command _SNMsynth.cmd > Output.txt

Cleaning work folder...

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

** Processing .NET 1.1 package...
Processing NDP1.1SP1-KB867460-X86.EXE...
Processing NDP1.1SP1-KB971108-X86.EXE...

** Processing .NET 2.0 SP2 package...
Processing NDP20SP2-KB971111-x86.exe...

Creating .NET 1.1 SP1 passive installer...
Creating .NET 1.1 SP1 passive add-on...
Creating .NET 2.0 SP2 passive installer...
Creating .NET 2.0 SP2 passive add-on...

DONE!

Remove .\TMP folder? (Y/N):
Cleaning work folder...

Interestingly the very first thing that happened was 2 File not Found messages, from cleaning work folder perhaps?

ProcessData.txt

--- WORK FOLDER CONTENT:
Volume in drive C has no label.
Volume Serial Number is 58AA-CDCA

Directory of C:\Documents and Settings\Administrator\My Documents\20091029_SNMsynth

31/10/2009 12:24a <DIR> .
31/10/2009 12:24a <DIR> ..
23/10/2009 09:32p 4,181 _20SP#_SLIMMING.7z
29/10/2009 02:49p 1,369 _20SP#LNGbr_KB829019FIX.7z
28/10/2009 09:46a 1,429 _20SP2_KB974417FIX.7z
27/09/2009 09:34a 1,109 _30SP#_REMFONTCACHEFIX.7z
27/09/2009 09:35a 1,626 _30SP#LNG_KB928416FIX.7z
19/10/2009 08:19p 16,941 _35SP#_SLIMMING.7z
29/10/2009 02:26p 1,009 _35SP1_KB963707FIX_NOFFADDONPROPERTY.7z
27/09/2009 09:33a 3,474 _KB951847FIX.7z
09/10/2009 07:54p 3,097 _REM_MSI_BLOCKING.7z
29/10/2009 04:32p 87,163 _SNMsynth.cmd
31/10/2009 12:23a 3,945 _SNMsynth.ini
03/02/2009 12:21p 536,064 7za.exe
14/09/2009 02:14a 108,032 7zSD.sfx
19/12/2006 08:42p 24,265,736 DOTNETFX.EXE
04/05/2008 02:52p 10,703,680 NDP1.1SP1-KB867460-X86.EXE
18/10/2009 05:30a 14,120,896 NDP1.1SP1-KB953297-X86.EXE
14/10/2009 08:45p 7,002,048 NDP1.1SP1-KB971108-X86.EXE
21/01/2009 05:48p 8,981,856 NDP20SP2-KB958481-X86.EXE
14/10/2009 08:45p 1,679,720 NDP20SP2-KB971111-X86.EXE
14/10/2009 06:59p 11,459,928 NDP20SP2-KB974417-X86.EXE
21/01/2009 05:46p 25,001,480 NETFX20SP2_X86.EXE
31/10/2009 12:24a 0 Output.txt
31/10/2009 12:24a 26 PROCESSDATA.TXT
27/09/2009 05:04p 283,648 upx.exe
24 File(s) 104,268,457 bytes
2 Dir(s) 13,335,912,448 bytes free

--- _SNMSYNTH.ini SETTINGS USED:
PROCESS_DNF11=YES
PROCESS_DNF20=YES
PROCESS_DNF35_DNF20=YES
PROCESS_DNF35_DNF30=YES
PROCESS_DNF35_DNF35=YES
DNF20_VC8_RUNTIME=YES
DNF20_OFFICE2K3_DEBUGGER=YES
DNF30_RGB_RASTERIZER=YES
DNF30_WIC=YES
DNF30_MSXML6=YES
DNF30_XPS=YES
DNF35_FF_ADDON=YES
DNF35_VC9_RUNTIME=YES
PROCESS_LNG_DNF11=YES
PROCESS_LNG_DNF20=YES
PROCESS_LNG_DNF35_DNF20=YES
PROCESS_LNG_DNF35_DNF30=YES
PROCESS_LNG_DNF35_DNF35=YES
WIN___=
T13ADDON=YES
MERGE_FRAMEWORKS=
SILENT=
UPX_SFX=
COMPRESSION_RATIO=

--- TMP FOLDER CONTENT:
Volume in drive C has no label.
Volume Serial Number is 58AA-CDCA

Directory of C:\Documents and Settings\Administrator\My Documents\20091029_SNMsynth\TMP

31/10/2009 12:26a <DIR> .
31/10/2009 12:26a <DIR> ..
28/10/2009 07:45p 5,632 20SP2_KB974417FIX.mst
10/10/2009 04:24a 4,096 20SP2_REM_MSI_BLOCKING.mst
25/09/2009 10:28a 6,144 20SP2LNG_KB951847FIX.mst
31/10/2009 12:26a 83 config.txt
31/10/2009 12:25a <DIR> DNF11
31/10/2009 12:24a 9 DNF11REM.TXT
31/10/2009 12:25a <DIR> DNF20
31/10/2009 12:25a 10 DNF20REM.TXT
31/10/2009 12:25a 1,656 INSTALL.CMD
31/10/2009 12:24a 117 INSTALL1.CMD
31/10/2009 12:25a 132 INSTALL2.CMD
31/10/2009 12:25a 416 INSTCOMMONEND.CMD
31/10/2009 12:25a 181 INSTREGDOWN.CMD
31/10/2009 12:25a 155 INSTREGDOWN2.CMD
31/10/2009 12:27a 17,160,704 TEMP.7z
31/10/2009 12:24a <DIR> TMP1
31/10/2009 12:24a <DIR> TMP2
31/10/2009 12:24a <DIR> TMP3
31/10/2009 12:25a <DIR> TMP4
31/10/2009 12:26a <DIR> TMP5
31/10/2009 12:27a <DIR> TMP6
31/10/2009 12:25a 220 TRANSFORMDB.vbs
14 File(s) 17,179,555 bytes
10 Dir(s) 12,955,451,392 bytes free

Link to comment
Share on other sites

@strel

DNF20_VC8_RUNTIME and DNF35_VC9_RUNTIME settings remove outdated VC runtimes subcomponents from 2.0 SP# and 3.5 SP# frameworks respectively, allowing to install updated ones from external files (see Suppported Files section above). Updated VC runtimes has to be installed previously to the framework from which the same the VC version is removed. They are pre-required.

I don't quite understand what you mean by the last line:

Updated VC runtimes has to be installed previously to the framework from which the same the VC version is removed. They are pre-required.

Do I have to update the VC runtimes on the system I am building the addon so I can remove them?

Link to comment
Share on other sites

Kurt_Aust

I don't think file not found messages came from cleaning subprocess. Making tests.

Glowy

Thx I'll check it.

atolica

First, there's a typo, sorry. I meant updated VC runtimes (that ones not comming from .NET frameworks but from the updated VC runtimes sources I posted in Supported Files section) has to be installed previously to the framework version from which the same VC runtime version is removed, i.e. if you remove VC8 from any 2.0 SP# you have to install VC8 from updated sources previosly to install that 2.0 SP# framework because it is a pre-requisite. The same goes for VC9 and 3.5 SP# frameworks.

Everybody

I'm fixing bugs.

Anyone more having problems?

Anyone experiencing difficulties on uninstall not finding the cached .msi installer to proceed?

Edited by strel
Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...