strel

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

1,004 posts in this topic

dbdawn

That bug you point is fixed since 20100101, I think. Also I'm not getting this error with the version I'm testing right now, in which code related to this bug is untouched since then. Please check your're effectively using 20100103.

Pasha_ZZZ

We were wrong thinking about using the /MIN switch to minimize frameworks progress boxes during building process as that only affects to the command line window that doesn't even show up (as it is executing only 1 command), but not to the .NET boxes.

mooms

Yes, I'm familiar with WaitNET, but I don't know why it is useful to avoid transient errors, as it is simply waiting until only 1 mscorsvw.exe process is running as a mark of the "event" that no transient errors have ocurred, what I think it's not right. RogueSpear also states that no .NET mangaged application can be installed until the optimization for the framework versions required ends, what I think it's not true as it's the application what relies on .NET frameworks, not its install process. Also I think that the application can even be run previously to the optimation process ends.

Edited by strel
0

Share this post


Link to post
Share on other sites

New version released!

My tests are clean, so I hope to have fixed all previous bugs reported. See changelog.

A lot of thx for your help folks! :thumbup

0

Share this post


Link to post
Share on other sites

Cool!

I don't have any problems with the latest version (20100104).

0

Share this post


Link to post
Share on other sites
We were wrong thinking about using the /MIN switch to minimize frameworks progress boxes during building process as that only affects to the command line window that doesn't even show up (as it is executing only 1 command), but not to the .NET boxes.
I know MSI windows are not minimized, but I think with /MIN key they will be created as background windows, not foreground...
0

Share this post


Link to post
Share on other sites

Hi strel, thank you for updating always. :hello:

20100104_SNMsynth

Some errors occurred while _SNMsynth.cmd integration process.

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

NOTE: Visual C 8 runtime libraries from 2.0 SP2 framework will be removed.
Use another source to install them. See guide.

NOTE: Office 2K3 debugger from 2.0 SP2 framework will be removed. See guide.

NOTE: MSXML6 will be removed from 3.0 SP2 framework.
Use another source to install it 3.0 SP2 framework. See guide.

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

NOTE: Visual C 9 runtime libraries will be removed from 3.5 SP1 framework.
Use another source to install them. See guide.

NOTE: NDP35SP1-KB963707-x86.exe won't be used as ClickOnce is being removed.


** 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 dotnetfx35langpack_x86ja.exe...
** Processing .NET 2.0 SP2 ja language portion...
E:\SNM20-35\TMP\TRANSFORMDB.VBS(5, 1) Msi API Error: ApplyTransform,TransformFile,ErrorConditions

** Processing .NET 3.0 SP2 ja language portion...
E:\SNM20-35\TMP\TRANSFORMDB.VBS(5, 1) Msi API Error: ApplyTransform,TransformFile,ErrorConditions

E:\SNM20-35\TMP\TRANSFORMDB.VBS(5, 1) Msi API Error: ApplyTransform,TransformFile,ErrorConditions

** Processing .NET 3.5 SP1 ja language portion...
E:\SNM20-35\TMP\TRANSFORMDB.VBS(5, 1) Msi API Error: ApplyTransform,TransformFile,ErrorConditions


Creating merged .NET 2.0 SP2 ja, .NET 3.0 SP2 ja,
.NET 3.5 SP1 ja XP passive installer....
Creating merged .NET 2.0 SP2 ja, .NET 3.0 SP2 ja,
.NET 3.5 SP1 ja XP passive T-13 add-on...


DONE!

But, T13XPDNF20SP2ja30SP2ja35SP1ja.7z addon seems to working well.

All the result of .NET Framework setup verification tool were success.

Is there a potential problem about this?

PROCESSDATA.TXT

0

Share this post


Link to post
Share on other sites

hi karmatron! seeing your processdata.txt reveals the following:

[font="courier new"]PROCESSDNF20=YES
PROCESSDNF3520=YES

DNF20VC8RUNTIME=
DNF20OFFICE2K3DEBUGGER=

DNF30MSXML6=

DNF35VC9RUNTIME=

DNF35FFCLICKONCEEXT=[/font]

you're processing 2.0 2x ... as for the others, you got those since you left the specific .ini settings blank ... i suppose you have other sources/addons for those ... cheers!

Edited by Kiki Burgh
0

Share this post


Link to post
Share on other sites

Pasha_ZZZ

Don't work that way, /qn could be used instead but I don't think it is a good idea to completely hide progress.

Karmatron

Checking...

Seems I forgot to change codepage to neutral for the changes I made in 20100104 in the transform files. I'll fix in the next minutes...

Kiki Burgh

PROCESSDNF20=YES and PROCESSDNF3520=YES are not a problem unless you have both packets in the work folder, and in that case the scripts gives an error.

Edited by strel
0

Share this post


Link to post
Share on other sites
Hi strel, thank you for updating always. :hello:

20100104_SNMsynth

Some errors occurred while _SNMsynth.cmd integration process.

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

NOTE: Visual C 8 runtime libraries from 2.0 SP2 framework will be removed.
Use another source to install them. See guide.

NOTE: Office 2K3 debugger from 2.0 SP2 framework will be removed. See guide.

NOTE: MSXML6 will be removed from 3.0 SP2 framework.
Use another source to install it 3.0 SP2 framework. See guide.

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

NOTE: Visual C 9 runtime libraries will be removed from 3.5 SP1 framework.
Use another source to install them. See guide.

NOTE: NDP35SP1-KB963707-x86.exe won't be used as ClickOnce is being removed.


** 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 dotnetfx35langpack_x86ja.exe...
** Processing .NET 2.0 SP2 ja language portion...
E:\SNM20-35\TMP\TRANSFORMDB.VBS(5, 1) Msi API Error: ApplyTransform,TransformFile,ErrorConditions

** Processing .NET 3.0 SP2 ja language portion...
E:\SNM20-35\TMP\TRANSFORMDB.VBS(5, 1) Msi API Error: ApplyTransform,TransformFile,ErrorConditions

E:\SNM20-35\TMP\TRANSFORMDB.VBS(5, 1) Msi API Error: ApplyTransform,TransformFile,ErrorConditions

** Processing .NET 3.5 SP1 ja language portion...
E:\SNM20-35\TMP\TRANSFORMDB.VBS(5, 1) Msi API Error: ApplyTransform,TransformFile,ErrorConditions


Creating merged .NET 2.0 SP2 ja, .NET 3.0 SP2 ja,
.NET 3.5 SP1 ja XP passive installer....
Creating merged .NET 2.0 SP2 ja, .NET 3.0 SP2 ja,
.NET 3.5 SP1 ja XP passive T-13 add-on...


DONE!

But, T13XPDNF20SP2ja30SP2ja35SP1ja.7z addon seems to working well.

All the result of .NET Framework setup verification tool were success.

Is there a potential problem about this?

Me too…

0

Share this post


Link to post
Share on other sites

Silent .NET Maker synthesized 20100104

PROCESSDNF11=YES

PROCESSDNF20=YES

PROCESSDNF3520=YES

PROCESSDNF3530=YES

PROCESSDNF3535=YES

DNF20VC8RUNTIME=

DNF20OFFICE2K3DEBUGGER=YES

DNF30RGBRASTERIZER=YES

DNF30WIC=

DNF30MSXML6=YES

DNF30XPS=YES

DNF35VC9RUNTIME=

DNF35FFXBAPPLUGIN=YES

DNF35FFCLICKONCEEXT=YES

PROCESSLNGDNF11=YES

PROCESSLNGDNF20=YES

PROCESSLNGDNF3520=YES

PROCESSLNGDNF3530=YES

PROCESSLNGDNF3535=YES

TARGETOS=XP

T13ADDONS=YES

ROEADDONS=

ALSOINSTALLERS=

MERGEFXS=YES

SILENT=YES

COMPRATIO=HIGHER

NDP35SP1-KB958484-x86:

not allowing hotfixes to apply its updated files to my custom installers/addons containing 3.5 SP# framework

KB958484.gif

THANKS!! :thumbup:thumbup

0

Share this post


Link to post
Share on other sites

20100105_SNMsynth

No errors, perfect! :thumbup

_SNMsynth.cmd messages

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

NOTE: Visual C 8 runtime libraries from 2.0 SP2 framework will be removed.
Use another source to install them. See guide.

NOTE: Office 2K3 debugger from 2.0 SP2 framework will be removed. See guide.

NOTE: MSXML6 will be removed from 3.0 SP2 framework.
Use another source to install it 3.0 SP2 framework. See guide.

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

NOTE: Visual C 9 runtime libraries will be removed from 3.5 SP1 framework.
Use another source to install them. See guide.

NOTE: NDP35SP1-KB963707-x86.exe won't be used as ClickOnce is being removed.


** 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 dotnetfx35langpack_x86ja.exe...
** Processing .NET 2.0 SP2 ja language portion...
** Processing .NET 3.0 SP2 ja language portion...
** Processing .NET 3.5 SP1 ja language portion...

Creating merged .NET 2.0 SP2 ja, .NET 3.0 SP2 ja,
.NET 3.5 SP1 ja XP passive installer....
Creating merged .NET 2.0 SP2 ja, .NET 3.0 SP2 ja,
.NET 3.5 SP1 ja XP passive T-13 add-on...


DONE!

Thank you!1

PROCESSDATA.TXT

0

Share this post


Link to post
Share on other sites

Hi strel.

Using 20100105, no more errors at the uninstall time. Thank you for the update

I have the usual errors, no harming i think:

100105042145447926.png

0

Share this post


Link to post
Share on other sites
Don't work that way, /qn could be used instead but I don't think it is a good idea to completely hide progress.
Maybe /qn as an option is not so bad idea. I wrote VBS launcher, it can process error codes returned by installer. And I have description of each error from MSDN. If there will be any errors - VBS can write this to log + warn user via console message & "Press any key to continue..." or display message box.

We cant see progress for each individual update only...

0

Share this post


Link to post
Share on other sites

Hi strel,

I'm having the same problem as user My2GirlsDad on HFSLIPped W2K Pro CD (English version).

Used SNMSynth 20100104 to build the installers. Tests were done in VMware Workstation 6.5.3.

The screenshots say it all.

I tried at HFSVCPACK, T-12 and T-9: results are the same.

(the old SNM versions did just fine @ T-9).

Manual install on operational W2K Pro system works just fine, so it seems the OS version check is not functioning as it should be. Is it possible to fix this? Or just eliminate the OS version check?

Thx in advance.

post-272856-1262705869_thumb.jpg

post-272856-1262705889_thumb.jpg

PROCESSDATA.TXT

0

Share this post


Link to post
Share on other sites

Strel, about WaitNet:

When you do install .NET 2.0 it creates the service and starts the service, launching a single instance of the process. When the install is finished, and this is the important part, msiexec.exe returns a "complete" state (whether it be successful or error). So for an installer, it is now considered "done" and svcpack will move on to the next installer. The problem is that when it reports "complete" it then begins the optimization process and this is where the long list of "excessive transient errors" in the event log comes in. All of the other installers and Windows setup processes are trampling all over the optimization. Furthermore, until the optimization is complete you cannot install some .NET 2.0 dependent applications. Even worse, the optimization will resume upon next reboot and these problems crop again because, presumably, we're running all sorts of RunOnceEx stuff and Windows is creating the first real user profile for the first time, etc.

If i understand this correctly it make the system wait for the .net runtime optimization to finish, so we can do the optimization @T-13 with no errors* instead of doing this at the first boot.

I insist on this because i already have some programs that run on first boot like the driverpacks finisher, an antivirus installer and a script to optimize/clean-up things, and it will be worse for those who use apps like WPI.

Beside, an user may don't understand why the system is so unresponsive (mscorsvw.exe take 100% of a monocore CPU for a relative long time).

It's not a problem if it make the install last longer @T-13 because no user interaction is needed/possible.

* Even if mscorsvw.exe is now executed at GuiRunOnce (or RunOnceEx? don't know) I always have this error 1111 in the event viewer:

NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Service reached limit of transient errors. Will shut down. Last error returned from Service Manager: 0x800736b1.

Thank you for taking this into account!

0

Share this post


Link to post
Share on other sites

After this message

_SNMsynth.ini not present, using default settings to build installers.

ECHO command with default settings not working. Current ECHO flag state putted into console.

0

Share this post


Link to post
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.