strel

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

1,004 posts in this topic

clarkg888

You should have this value in the registry:

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\9E0DE89293FE9BB33898F24ED18CCF08\State 1 DWORD

Thanks strel for your quick reply.

Yes, that value is set.

However, the problem install was done on a Virtual PC machine. I ran the install on a partition on my real machine and it worked fine: Windows updates did *not* ask to install KB974417! One difference was that the LAN drivers weren't integrated, but were installed after the system was restarted, so Windows update didn't do its thing until then.

I'll have to make a build with the drivers integrated (Driverpacks) and try again to test that hypothesis.

0

Share this post


Link to post
Share on other sites

My2GirlsDad, clarckg888, what I did: I built passive merged installer with 1.1 SP1, 2.0 SP2, 3.0 SP2, 3.5 SP1, with regular hotfixes and langpacks and not removing any subcomponent; I used HFSLIP 1.7.10 beta D over a vanilla XP SP3 applying the former installer in the HFSVCPACK folder, the process worked well except a couple of file not found messages not stopping the process and not while applying custom .NET installer, that I suppose has to do with some kind of error with HFSLIP beta itself. Nothing more. I went through the install process on a Virtual PC 2007 and ALL frameworks and langpacks installed correctly (HFSLIP Total Slipstream entry in Add/Remove Programs). Then I run windows update and no KB974417 nor any .NET hotfix were listed.

So I think these issues has nothing to do with SNMsynth but with something about your methods to build your custom win sources, but I'm out of ideas. I'm not an HFSLIP user so in case it has something to do with it maybe other expertise HFSLIP users may have more precise ideas about what could be happening.

Is there anybody else with those issues?

0

Share this post


Link to post
Share on other sites

Slightly, yes, I observed that also. I suppose it's something with the way the compression algorithm works, but don't know exactly why.

EDIT: Making some tests with compression parameters I could check that the different output sizes for sequential runs with the same settigns are not caused by 7-zip compression, differences seems to arise during the admin install creation or patching stage.

Edited by strel
0

Share this post


Link to post
Share on other sites
My2GirlsDad, clarckg888, what I did: I built passive merged installer with 1.1 SP1, 2.0 SP2, 3.0 SP2, 3.5 SP1, with regular hotfixes and langpacks and not removing any subcomponent; I used HFSLIP 1.7.10 beta D over a vanilla XP SP3 applying the former installer in the HFSVCPACK folder, the process worked well except a couple of file not found messages not stopping the process and not while applying custom .NET installer, that I suppose has to do with some kind of error with HFSLIP beta itself. Nothing more. I went through the install process on a Virtual PC 2007 and ALL frameworks and langpacks installed correctly (HFSLIP Total Slipstream entry in Add/Remove Programs). Then I run windows update and no KB974417 nor any .NET hotfix were listed.

Strel,

I am totally confused now. I did the same thing you did... XP Home SP2 in source, SP3 hotfix in HF, and installer in HFSVCPACK, nothing else, using 1.7.10 beta D. I went through the install process on a Virtual PC 2007 as you did. Still only 1.1 SP1 is installed but not 2.0 SP2 or 3.0 SP2 or 3.5 SP1. What am I doing wrong?

Please check my entries and help me figure this out.

Thank you.

M2GD

0

Share this post


Link to post
Share on other sites

Some ideas:

- You should check your SVCPACK.INF file after running HFSLIP. Maybe there's some kind of error with HFSLIP beta.

- Look for %SYSTEMROOT%\DNF20install.log file and check for any error. Check also the event viewer.

- You say you're using SP2 version and updating to SP3. I'd try doing it in 2 different steps, the first for applying the SP3 and the second for applying SP3 hotfixes+.NET custom installers.

- You say you used XP home, I used pro, don't know if there might be some limitation at T-13 in the home version not present in the pro. Anybody any comment on this??

Edited by strel
0

Share this post


Link to post
Share on other sites
Why each time makes a compression package of size is dissimilar?
Size may vary depends of free RAM amount. For compression you must have Dictionary_Size * 11 of free RAM
0

Share this post


Link to post
Share on other sites

Thanks for this new version. I really like the features to remove MSXML and the older VC Redistributables :thumbup

BTW I don't install .NET 1.1 as almost all software runs as .NET 2.0. To get less problems I now install both .NET Framework 2.0, 3.0 and 3.5 at first logon. This also requires that all software depending on .NET have to installed last. I do configure any registry settings at T13 though to apply them to the default user account.

Keep in mind Microsoft will also release .NET Framework 4.0 in a few months. You can download .NET Framework 4.0 beta 2 here.

Edited by Acheron
0

Share this post


Link to post
Share on other sites

Use Silent .NET Maker synthesized 20100118, WinXP install AutoCAD 2006 cannot be detected Net 1.1 Langpacks and they could not be installed, you need to manually remove Net 1.1 Langpacks before installing

0

Share this post


Link to post
Share on other sites

AutoCAD 2006 not installing if .NET 1.1 langpack from custom SNMsynth is installed? Are you meaning that? Don't know what the problem is, I supposse it is something with that software, or maybe with your install sequence or timming. What I can tell you is that the .NET 1.1 langpack component in your custom SNMsynth installer(s)/add-on(s), is the administrative install of that langpack without further modifications.

0

Share this post


Link to post
Share on other sites

I clearly need to be a tech wizard to understand this stuff.. I have problems reading through the OP and understanding what it is exactly that I need to do, to get all the .NET packages slipstreamed/integrated into the unattended XP disc. This guide isn't meant for those of us with "intermediate" knowledge of this stuff.. I have no clue how to make this work for me :P

Edited by Zaitzev
0

Share this post


Link to post
Share on other sites

I have used SNMsynth script and in the OUT1 folder i have three files:

ROEXPDNF11SP1el20SP2el30SP2el35SP1el.7z

T13XPDNF11SP1el20SP2el30SP2el35SP1el.7z

XPDNF11SP1el20SP2el30SP2el35SP1el.exe

How can i slipstream these files to make an unattended XP disc?

can somebody help me????

0

Share this post


Link to post
Share on other sites

The second is for use with nLite, and the third (.exe) is for use with RunOnce.

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.