clarkg888

Member
  • Content count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About clarkg888

  1. I've only seen the XPSP2.EXT. I don't recall there ever being a XPSP3.EXT. Clark.
  2. Yes, it turned out not to be a problem with HFSLIP. There is some problem with my main Windows XP machine that causes the SNMsynth builder to produce an installer that doesn't install the integrated patches. I was able to build a good installer on a Windows XP VMWare machine fine. I didn't keep proper track of the various changes I made when troubleshooting this issue, so I jumped to the wrong conclusion. My apologies! During my testing, I wasn't running the SNMsynth installer during the Windows install. I was rebooting after complete Windows install, then installing SNMsynth like a normal install. Now to figure out what is wrong with my main machine... Clark.
  3. Hello All, I've solved a problem I ran into with HFSLIP and I'd like to share so nobody else needs to suffer my misery! Problem: I use SNMSynth to create an all-in-one .NET installer. When this is installed on an HFSLIP'd installation of Windows XP, none of the hotfixes that were included in SNMSynth get installed. That is, Windows update reports that KB951847 (the service pack for .net 2.0, 3.0, and 3.5) needs to be installed, even though the patched files from KB951847 are in the installer. There were no errors running SNMSynth and the installation logs (e.g. DNF20install.log) indicate the patched files are being copied, but in fact they aren't: the unpatched files are copied. Other software installs work fine. I am using HFSLIP 1.7.10 beta K v4 and Windows XP generic OEM SP3 source. There are no errors reported during HFSLIP creation. I'm running the SNMSynth installer after Windows is installed: it is not part of the HFSLIP-created XP iso. Cause: In HFSLIP, I am slipstreaming Windows Installer 4.5 KB942288 and its hotfix KB981669. If I remove KB981669, or I move it from the HF folder to HFSVCPACK_SW1 folder, then the SNMSynth installer works fine. It's probably caused by the fact the KB981669 is applied before KB942288 in the HFSLIP script. However, the older files in KB942288 are *not* overwriting those from KB981669: the script is working properly there. But something else in Windows Installer 4.5 is being messed up. Solution: Move KB981669 to to the HFSVCPACK_SW1 folder. Mim0: perhaps you could update your site to recommend this change. I am thinking of modifying the script so that KB981669 is applied after KB942288 and see if that resolves the issue as well. I suspect this bug might also rear its head when installing from an administrative install point that has had patches applied. This is basically what SNMSynth does. Clark.
  4. Wow, thanks rockets4kids for your post! It was so timely. The last time I used snmsynth was 2 years ago, but I am just about to create a new slipstreamed XP disk and needed an updated .net installer. Using my 2 year old installer, WU reported 13 updates for me to figure out. You just saved me a lot of time. Thanks!
  5. Hello ghostdlr, I don't think you can use this for Vista or windows 7 (from reading the first post in this thread). The supported OS are 2K, XP and 2k3. The TARGET_OS option in the .ini lets you build on an OS different than the build machine (e.g. build for install on 2K using an XP box.). Also, I suspect 64-bit would require a different installer and is not supported by .net maker. I'm no expert: I've just used this for creating a fully patched XP install disk along with HFSLIP. The last time I used it was March 2010. Whether it can integrate any subsequent .net patches I don't know. You know that dotnet35.exe supports silent install itself, right? (/q /norestart switches) I hope this helps, Clark.
  6. 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.
  7. Items in SVCPACK are installed at T-13 (before the 2'nd reboot), while items in HFGUIRUNONCE are installed on the first GUI login after the 2'nd reboot. So, SVCPACK installs are done before HFGUIRUNONCE. There is less Windows 'infrastructure' available at T-13, so some things won't install then. When I used SNM before the all-in-one installer feature was added, I would put the 2.0 installer in SVCPACK, and the 3.0 and 1.1 installers in HFGUIRUNONCE. Now, I'm just putting the all-in-one installer in HFGUIRUNONCE. I might try putting in SVCPACK and test (after I've got the other issue I posted about resolved). Clark.
  8. Hello, I would first like to thank the developers of this great tool. I've used SNM in the past, and I'm just coming back to it to build a new XP install disk. My trouble is that after install Microsoft Update wants to install KB974417. I'm creating the disk using the latest HFSLIP (1.7.10 beta D), and I'm using SNMsynth 20100118 to build an all-in-one passive installer that gets put in the GUIRUNONCE folder in HFSLIP. SNMsynth builds without errors, and the installer works without any errors that I can see. I've checked the files 974417 updates: mscordacwks.dll, mscorlib.dll and mscorwks.dll: they are supposed to be version 2.0.50727.3603 and the installed system has this version. Where should I look to find the cause of this? By the way, I made a couple of small changes to _SNMsynth.cmd. It would not list the work or tmp directories in PROCESSDATA.TXT because I use the '-' as a date separator instead of '/'. For example: ECHO>PROCESSDATA.TXT --- WORK FOLDER CONTENT: REM fix by Clark REM DIR /-C/ON|FINDSTR /R "../.*">>PROCESSDATA.TXT DIR /-C/ON|FINDSTR /R /C:"^[^ ]">>PROCESSDATA.TXT Thanks in advance, Clark PROCESSDATA.TXT process.txt