Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

  • Country


Everything posted by strel

  1. nLite process add-ons ONLY at hotfix stage, hence every add-on created with SNMsynth goes there, but with SNMsynth you can make installers also that don't go there. Anyway SNMsynth is 32-bit only so doesn't fit your requirements. For x64 you should better try this or this or this
  2. strel

    net framework

    At least for the error at line 73 position 3, the net.exe command is used and you're removing "Command-line tools" from "Operating System Options" at "Components" stage.
  3. If it applies any 3.5 SP1 hotfix you better rebuild this one with SNMsynth latest version as there was a bug applying 3.5 SP# hotfixes on that dates.
  4. 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 My2GirlsDad Don't know why this is happening to you but 2.0 should install properly at T-13. I'll make tests tomorrow.
  5. You should read this, this and this. Use $OEM$ folders to copy your installers for RunOnce to the HD, and then write your RunOnce commands pointing to that destinations.
  6. 3rd time, if you're going to use add-ons do it in the hotfix stage despite the type of add-on, but if they don't work don't be surprised because you simply don't want to learn that nLite may won't do everything you want it to do, and you don't want to learn how to overcome that. About what's an add-on and what is not, add-ons usually are compresed in a packet .zip .rar .7z or .cab, and has an entries.ini file built-in. But better to read the info about it from the site you downloaded it. Don't you think so? About nlite RunOnce stage, you'd need to read some extras about unattended installs, but you don't want to go deep. So good luck. In case you change your mind there's a link above to the unattended guide, RTFM. I hope this makes sense also.
  7. What I usually do is a "save image as" of the flag not completing it to see the file name, and then google for "xx country code". Don't work with all codes, for example Chad flag is cd but first level domain is td an nomal country code around too, and furthermore his flag is almost equal to Romania, Andorra and Moldavia flags so it has been the most difficult flag I identified, precisely today.
  8. No, but with such short lines I had to increase font size a lot in FF to notice.
  9. Here, with firefox, when I increase text size. (XP 1600x1200 with taskbar at one side), also in IE6 but not in opera 10.
  10. Actually nLite uses an RVMI software portion to apply the add-ons, an outdated one as nLite seems to be no longer developed. The recommendation to only use nLite once per image it's a nice one generally speaking, specially when touching the system (removing features, changing settings, making it unattended, tweaking...) but it is not a rule that can not be broken if you know what you're doing. You can use nLite to set, trim and tweak your image, and later use RVMI to apply all add-ons. If you use nLite you should apply add-ons at hotfix stage despite the type of add-on (even if it is a RunOnce add-on), but being aware that non T-13 add-ons could contain settings not compatible with nLite making them fail. But otherwise, if there's no T-13 add-on applied, nLite will build the basic T-13 structure for nothing. RunOnce nLite stage is not for add-ons but for installers, I told you in my previous post.1. You can directly install .NET from RunOnce, setting it manually. You can use Silent .NET Maker synthesized to build feature rich custom .NET add-ons (RunOnceEx included). 2. Again if you're talking about add-ons and nLite, they have to be applied in the hotfix stage.
  11. I still cannot recreate your errors, and my ADMIN35 folder is being created as usual. May you have a problem with installer service, try restarting it; or may you have some issue with installed .NET frameworks in bad state, I'd try reinstalling them if the error persists, maybe using .NET framework cleanup tool.
  12. 1. Add-ons automate an install method at one time mark of the win setup. Though they were concieved to automate T-13 (SVCPACK.INF) method that is the easier one for add-ons, other advanced add-on methods like RunOnce, RunOnceEx, T-28 (Optional Components (OC)) or even text setup can be achived with them with the new add-on features available, but they are harder to build. In nLite you have to apply add-ons in the hotfixes stage, despite the type of add-on. nLite was conceived to manage only T-13 add-ons so it builds a basic T-13 install structure even if the add-on is not a T-13 one, but it can process other types correctly though it has some limitations with the new features. Other software capable to handle add-ons are RVMI (recommended for non T-13 add-ons) and HFSLIP. When to use one or the other type of add-on?, asking this is equivalent to ask what install method better adapt to your needs, depending on the characteristics of the application, you're going to be able to install at one setup time mark or another. Then you choose, among viable methods, the one that best fit to your needs, or the easier one, or so. 2. I don't fully understand what are you referring to but you can fit your installers in the add-ons as long as they can be run at the time mark you're scheduling. Each application has its own tricks, check the "applications install" subforum to get help. Other active add-on building forum is ryanvm.net/forum Entries.ini is the key to understand how add-ons work. You'll probably need to read extra documentation to understand advanced install methods.
  13. But it's working fine for me, and unless you give me enough data to recreate your error, what you can do by simply attaching your PROCESSDATA.TXT file, I tend to think that something is wrong with the steps you're following... maybe something is wrong with your color patch... do some checkings.
  14. coords Your custom installers will remove the cancel button for passive install. You don't need to change anything as Pasha_ZZZ proposes, unless what you want to remove is the cancel button during the building process. Pasha_ZZZ I could not recreate your errors, it's working fine for me. I'd need more data.
  15. 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. 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.
  16. 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.
  17. 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.
  18. 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.
  19. 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!
  20. 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.
  21. This messages come from the install script "error boxes for wrong switches" part of the code, so I'd like to discard you'd were using switches to run your custom installers at T-13 (or may you have repacked T-13 add-ons applying switches to change default behavior). But if you're using switches at T-13, what's exactly the command with switches you're running? Is that exact command generating that broken error box only on T-13?
  22. Not sure what's happening, I'm not an HFSLIP user, you may need to post in HFSLIP subforum giving further details. As long as you apparently seem to be using AIO custom installer (so intall priorities are handled by install script), what you did seems OK to me selecting only one of the folders (hence install method) to drop your custom installers. I'd check the windows source to see whether or not HFSLIP applied the installers correctly using the install method selected. You can test the custom installers on your system or apply them to you win source manually to discard a problem with them. I just discovered you can use add-ons also with HFSLIP using HFAAO folder (see guidelines/extras in hfslip.org), didn't know it and don't think it makes any difference, but it's an extra option to apply them.
  23. Pasha_ZZZ, I really think /qb! is not needed, I don't think there's a real risk with the user running the building process pressing the cancel button mistakenly, specially if I add /MIN switch as an option, and I prefer not close options. Also the building process is not supposed to be run by a user in a managed environment, but by the administrator, so doesn't seem to be an issue. All this make me think /qb! in the building process is not a good idea, and in addition everyone can change the script to their needs. And obviously I was referring to use the cancel button after closing the command line window or after aborting building process with CTRL+C (or double one) waiting for started subprocess to end, period that can be shortened by pressing the cancel button.
  24. Pasha_ZZZ, I'll include minimize option for building process .NET admin install launch in the next version, it's a good idea. I fixed version # for the current files. And about /qb!, you're referring to the building process, but it's not my to intention to ocult it there, is useful in case process is aborted. Thx for your suggestions.

  • Create New...