Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

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

- - - - -

  • Please log in to reply
1003 replies to this topic

#701
mooms

mooms

    Hello world !

  • Member
  • PipPipPip
  • 303 posts
  • OS:Windows 7 x64
  • Country: Country Flag
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:
Posted Image


How to remove advertisement from MSFN

#702
Pasha_ZZZ

Pasha_ZZZ

    Newbie

  • Member
  • 42 posts
  • OS:XP Pro x86
  • Country: Country Flag

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

#703
BugsBunny

BugsBunny
  • Member
  • 2 posts
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.

Attached Files



#704
mooms

mooms

    Hello world !

  • Member
  • PipPipPip
  • 303 posts
  • OS:Windows 7 x64
  • Country: Country Flag
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!

#705
Pasha_ZZZ

Pasha_ZZZ

    Newbie

  • Member
  • 42 posts
  • OS:XP Pro x86
  • Country: Country Flag
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.

#706
Pasha_ZZZ

Pasha_ZZZ

    Newbie

  • Member
  • 42 posts
  • OS:XP Pro x86
  • Country: Country Flag
Hi Strel.
I wrote VBS script, which add ANSI color codes to your SNMs, makes new file _SNMsynthColor.cmd. For using this place ANSICON.EXE and ANSI.DLL from this archive to the SNMs folder.

3 types of messages highlighted now:
NOTE: yellow on blue
WARNING: black on yellow
ERROR: white on red

Edit: _SNMsynth.cmd correction not needed since 20100116 version!

And finally, run this VBS only via WScript! CScript sometimes runs it incorrectly. Resulting _SNMsynthColor.cmd size must be ~2Kb bigger than _SNMsynth.cmd

Attached Files


Edited by Pasha_ZZZ, 17 January 2010 - 06:36 AM.


#707
BugsBunny

BugsBunny
  • Member
  • 2 posts
Hi strel,

I found the problem and the solution for the installers not recognizing the W2K OS (and probably XP too!) when run from a HFSLIPped CD. The :INSTBASE section of the _SNMsynth.cmd contains 2 times the word REGEDIT. Change both instances to "%%SYSTEMROOT%%\REGEDIT.EXE" (including the double-quotes!). After that everything works just fine. Both MBSA v2.1 and .NET Setup Verifier Tool give a clean bill of health.

Strel, can you add this to the next official release of _SNMsynth.cmd ?
Thx.

#708
Kiki Burgh

Kiki Burgh

    MSFN Expert

  • Member
  • PipPipPipPipPipPip
  • 1,426 posts
hi strel! just a couple of inquiries:

i got this in my latest run:
[font="Courier New"]NOTE: WIC will be removed from 3.0 SP2 framework.Use another source to install it before 3.0 SP2 framework. See guide.[color="#0000FF"]Environment variable ECHO[/color] NOTE: msxml6.msi will be used instead of any not definedeven if it has not the lastest files.NOTE: XPS print driver will be removed from 3.0 SP2 framework.Use another source to install it. See guide.[/font]
should Environment variable ECHO appear as opposed to prior & succeeding lines which do not have it?

if i have Update for MSXML Core Services 6.0 Service Pack 2 (KB973686) - msxml6-KB973686-enu-x86.exe, i don't need Microsoft Core XML Services (MSXML) 6.0 - msxml6.msi, correct?

compared the files when extracted but here are the details i got:
msxml6.msi
msxml6.dll.86F857F6_A743_463D_B2FE_98CB5F727E09
MSXML6.dll
6.20.1102.0
msxml6r.dll.86F857F6_A743_463D_B2FE_98CB5F727E09
MSXML6R.dll
6.00.3883.0


VS

msxml6-KB973686-enu-x86.exe
msxml6.dll.86F857F6_A743_463D_B2FE_98CB5F727E09
MSXML6.dll
6.20.2003.0
msxml6r.dll.86F857F6_A743_463D_B2FE_98CB5F727E09
MSXML6R.dll
6.00.3883.0


on 1 hand, Update for Windows XP (KB973687) - WindowsXP-KB973687-x86-ENU.exe has
MSXML6.dll
6.20.1103.0


thanks!

Edited by Kiki Burgh, 09 January 2010 - 11:08 PM.

Posted Image

#709
Pasha_ZZZ

Pasha_ZZZ

    Newbie

  • Member
  • 42 posts
  • OS:XP Pro x86
  • Country: Country Flag

msxml6-KB973686-enu-x86.exe
MSXML6.dll 6.20.2003.0


on 1 hand, Update for Windows XP (KB973687) - WindowsXP-KB973687-x86-ENU.exe has
MSXML6.dll 6.20.1103.0

Unlike MSXML4, same MSXML6 version has different files depending on Windows version they are aimed at. Recent msxml6.dll updates for Win2k-2k3-XPsp2 have different MD5 hashes from the one for XPsp3 and this is also for the latest MSXML6 hotfixes KB973686-973687, both published the same day (so there isn't a older/newer one).

Version: 6.20.2003.0
Knowledge Base (KB) Articles: KB973686
Date Published: 11/23/2009

Version: 973687
Knowledge Base (KB) Articles: KB973687
Date Published: 11/23/2009


Edited by Pasha_ZZZ, 10 January 2010 - 02:55 AM.


#710
Kiki Burgh

Kiki Burgh

    MSFN Expert

  • Member
  • PipPipPipPipPipPip
  • 1,426 posts
hi Pasha_ZZZ! thanks for the additional info though this portion of my post was just a side note. my main concern was validating/confirming i could remove msxml6.msi (which has MSXML6.dll ver 6.20.1102.0) in favor of msxml6-KB973686-enu-x86.exe (which has MSXML6.dll ver 6.20.2003.0)
btw, would you care to point me to where you quoted nonno fabio from. appreciate it.
Posted Image

#711
Pasha_ZZZ

Pasha_ZZZ

    Newbie

  • Member
  • 42 posts
  • OS:XP Pro x86
  • Country: Country Flag

btw, would you care to point me to where you quoted nonno fabio from. appreciate it.

This is from Ryan's forum, but links to other forums here not allowed...

#712
Kiki Burgh

Kiki Burgh

    MSFN Expert

  • Member
  • PipPipPipPipPipPip
  • 1,426 posts

btw, would you care to point me to where you quoted nonno fabio from. appreciate it.

This is from Ryan's forum, but links to other forums here not allowed...

tried looking for it in his addon pack & might have missed it ... perhaps just the topic itself would do & i'll do the seach ... thanks!

edit: appreciate it Pasha_ZZZ!

Edited by Kiki Burgh, 10 January 2010 - 05:30 AM.

Posted Image

#713
My2GirlsDad

My2GirlsDad

    Junior

  • Member
  • Pip
  • 98 posts
  • OS:Vista Home Premium x86
  • Country: Country Flag

Hi strel,

I found the problem and the solution for the installers not recognizing the W2K OS (and probably XP too!) when run from a HFSLIPped CD. The :INSTBASE section of the _SNMsynth.cmd contains 2 times the word REGEDIT. Change both instances to "%%SYSTEMROOT%%\REGEDIT.EXE" (including the double-quotes!). After that everything works just fine. Both MBSA v2.1 and .NET Setup Verifier Tool give a clean bill of health.

Strel, can you add this to the next official release of _SNMsynth.cmd ?
Thx.


Just tried your "fix" Bugs and it worked like a charm in Win2k. Both Nets installed and Verified. Thank you for finding this "bug".

Still having a problem with XP with HFSLIPped CD as only Net 1.1 is installing and verifying. No 2.0, 3.0, or 3.5. This is puzzling. Using all defaults in _SNMsynth.ini except last section which is below:

TARGETOS=XP
T13ADDONS=
ROEADDONS=
ALSOINSTALLERS=
MERGEFXS=YES
SILENT=YES
COMPRATIO=

It was working with the previous version. Am I missing something, peoples?

#714
Kiki Burgh

Kiki Burgh

    MSFN Expert

  • Member
  • PipPipPipPipPipPip
  • 1,426 posts

Still having a problem with XP with HFSLIPped CD as only Net 1.1 is installing and verifying. No 2.0, 3.0, or 3.5. This is puzzling. Using all defaults in _SNMsynth.ini except last section which is below:

TARGETOS=XP
T13ADDONS=
ROEADDONS=
ALSOINSTALLERS=
MERGEFXS=YES
SILENT=YES
COMPRATIO=

It was working with the previous version. Am I missing something, peoples?

hi strel! in this case brought up by My2GirlsDad, would there be a way for us to test the end-product so as to validate if all components have been processed accordingly other than testing it either on vm or live install (we can work with the silent installer but either all .nets must be uninstalled (or thru using .NET FX Cleanup Tool) or have not yet been installed prior to running .NET Framework setup verification tool)? have yet to make my iso so i can't confirm any findings yet. thank you!
Posted Image

#715
strel

strel

    segmentation fault

  • Member
  • PipPipPipPip
  • 629 posts
  • OS:XP Pro x86
  • Country: Country Flag
New version released.

I fixed again major bug processing 3.5 SP# hotfixes, as pointed by shiouliang, thx again man!
I reinserted it when I modified KB963707 applying process to avoid arisen errors in 20100101. Sorry again folks.

I applied BugsBunny's fix for the bug with T-13 (and GUI setup in general) OS detection error boxes. Thx man!

I fixed minor bugs with ...msxml6.msi... and ..._SNMsynth.ini... error messages.


My2GirlsDad
Haven't tested with HFSLIP, but with nLite, T-13 add-ons for XP is not showing any wrong OS detection error message box for me.

Kiki Burgh
Yes, msxml6-KB973686 has the latest files.
Don't know any automated method to verify correct output, even .NET Framework setup verification tool proved to be unable to report the bug with 3.5 SP# not applying the latests files from the hotfixes, fixed in this release.

Pasha_ZZZ
I modified the error messages you pointed to finish with a dot character for your _SNMsynth.cmd color patch can be applied directly.
Can you please modify post #706 to reflect this change is not needed anymore and to add a working link for the ANSI... files like this one, so I can add a link to that post in the guide?

mooms
If you look at what WaitNET do, you'll see all it does is to wait until only one instance of mscorsvw.exe is running. I don't know why is this going to avoid transient errors. Also _SNMsynth custom installers/add-ons does wait for the optimization process to end with or without the transient errors, furthermore in case the transient errors appear, only a portion of the optimization process is executed on next boot, not the whole process.

Edited by strel, 16 January 2010 - 07:06 PM.


#716
Kiki Burgh

Kiki Burgh

    MSFN Expert

  • Member
  • PipPipPipPipPipPip
  • 1,426 posts

New version released.

I fixed minor bugs with ...msxml6.msi... and ..._SNMsynth.ini... error messages.

Kiki Burgh
Yes, msxml6-KB973686 has the latest files.
Don't know any automated method to verify correct output, even NET Framework setup verification tool proved to be unable to report the bug with 3.5 SP# hotfixes not applying the latests files from the hotfixes, fixed in this release.

thank you!
Posted Image

#717
ykchanaed

ykchanaed

    Junior

  • Member
  • Pip
  • 94 posts
in 20100116, I had the following error message in cmd window:

Cleaning work folder...

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

File Not Found
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 langpack.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...
Processing
Invalid switch - "/Q".


Please help!

On searching through Process explorer, the msiexec.exe is looking for "TMP\TMP5\M6" folder.
But only M5 exists!

Attached Files


Edited by ykchanaed, 17 January 2010 - 01:53 AM.


#718
strel

strel

    segmentation fault

  • Member
  • PipPipPipPip
  • 629 posts
  • OS:XP Pro x86
  • Country: Country Flag
New version released.

Bug inserted since 20091224, not checking presence of msxml6-KB*-x86.exe files if no msxml6.msi is present, thus acting as if there were any, was fixed, solving ykchanaed errors.

Edited by strel, 17 January 2010 - 04:09 AM.


#719
Kiki Burgh

Kiki Burgh

    MSFN Expert

  • Member
  • PipPipPipPipPipPip
  • 1,426 posts
hi strel! just a few quick inquiries ... would this XPSEP XP and Server 2003 32 bit.exe have newer file than DNF30XPS? (there's 1 too for 64 bit.) so if i have this update in my UA, would it be better instead to leave this as DNF30XPS= in _SNMsynth.ini? would it be possible to have XPSEP XP and Server 2003 32 bit.exe processed in SNMSynth? thank you!

Edited by Kiki Burgh, 17 January 2010 - 03:02 AM.

Posted Image

#720
Raoul90

Raoul90

    Member

  • Member
  • PipPip
  • 283 posts
Hey Strel,

Thanks for the updates!


But:
I noticed something when the script was bissy, I normally never watch what is happening, but now I did:
Posted Image
It says processing the KB974417 and then says "System cant find the specified file"?


Posted Image
Al those "Bestand niet gevonden" are "File not found"?



Posted Image
My dotNET folder.


Processdata:
--- WORK FOLDER CONTENT:

--- _SNMSYNTH.ini SETTINGS USED:
PROCESSDNF11=YES
PROCESSDNF20=NO
PROCESSDNF3520=YES
PROCESSDNF3530=YES
PROCESSDNF3535=YES
DNF20VC8RUNTIME=YES
DNF20OFFICE2K3DEBUGGER=YES
DNF30RGBRASTERIZER=YES
DNF30WIC=YES
DNF30MSXML6=YES
DNF30XPS=YES
DNF35VC9RUNTIME=YES
DNF35FFXBAPPLUGIN=YES
DNF35FFCLICKONCEEXT=YES
PROCESSLNGDNF11=YES
PROCESSLNGDNF20=NO
PROCESSLNGDNF3520=YES
PROCESSLNGDNF3530=YES
PROCESSLNGDNF3535=YES
TARGETOS=XP
T13ADDONS=
ROEADDONS=
ALSOINSTALLERS=
MERGEFXS=YES
SILENT=YES
COMPRATIO=

--- .\TMP FOLDER CONTENT:


Installer works fine tho. :P

Edited by Raoul90, 17 January 2010 - 06:18 AM.


#721
Pasha_ZZZ

Pasha_ZZZ

    Newbie

  • Member
  • 42 posts
  • OS:XP Pro x86
  • Country: Country Flag

I modified the error messages you pointed to finish with a dot character for your _SNMsynth.cmd color patch can be applied directly.
Can you please modify post #706 to reflect this change is not needed anymore and to add a working link for the ANSI... files like this one, so I can add a link to that post in the guide?

Post modified, direct link to ANSICON added.

#722
strel

strel

    segmentation fault

  • Member
  • PipPipPipPip
  • 629 posts
  • OS:XP Pro x86
  • Country: Country Flag
New version released.

It solves a couple of minor bugs causing file not found errors, as described by Raoul90. Those errors only appeared in some cases if you used restricted hotfixes for 2.0 SP2 or if you used them only on some of the frameworks being processed. Those errors didn't harmed at all as the script was trying to execute files not present because of the bugs mentioned.

hi strel! just a few quick inquiries ... would this XPSEP XP and Server 2003 32 bit.exe have newer file than DNF30XPS? (there's 1 too for 64 bit.) so if i have this update in my UA, would it be better instead to leave this as DNF30XPS= in _SNMsynth.ini? would it be possible to have XPSEP XP and Server 2003 32 bit.exe processed in SNMSynth? thank you!

After some research, that packet installs WIC and MSXML6 in addition to XPS, and you cannot decide to avoid any of them. But though the packet is newer the files contained (or downloaded during install for the case of MSXML) doesn't. You can have more recent files from links in the guide, or from packets like YumeYao's WIC or so.


Pasha_ZZZ, I included a link to your patch.

#723
coords

coords
  • Member
  • 5 posts
Very interesting thread folks...

I have one issue that is annoying me, and hope that you have a solution. Is there a way to get the standard installation to do a passive install (with progress bar) but WITHOUT the dreaded cancel button? Our users just love playing with the cancel button if the installation takes too much time... any ideas/suggestions?

Thanks!

Co-ords

Edited by coords, 18 January 2010 - 03:14 AM.


#724
Pasha_ZZZ

Pasha_ZZZ

    Newbie

  • Member
  • 42 posts
  • OS:XP Pro x86
  • Country: Country Flag

standard installation to do a passive install (with progress bar) but WITHOUT the dreaded cancel button?

In the script file (_SNMsynth.cmd) replace all /qb with /qb!

Edited by Pasha_ZZZ, 18 January 2010 - 03:19 AM.


#725
Pasha_ZZZ

Pasha_ZZZ

    Newbie

  • Member
  • 42 posts
  • OS:XP Pro x86
  • Country: Country Flag
SNMs 20100118,
** Processing .NET 3.5 SP1 portion...
NDP35SP1-KB957661-x86.exe process delayed.
Processing NDP35SP1-KB958484-x86.exe...
& I see message box with error "Unable to open installer package......."
20100117 works w/o errors.

P.S.: All 3.5 sp1 updates give this error too. I think MSIEXEC cannot find MSI package (invalid extraction path?)...

Edited by Pasha_ZZZ, 18 January 2010 - 12:09 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN