Jump to content

strel

Member
  • Posts

    625
  • Joined

  • Last visited

  • Donations

    $0.00 
  • Country

    Spain

Everything posted by strel

  1. Try with: FOR %%f IN (*.exe) DO start "" /wait "%%f" /passive /integrate:%~dp0Source EDIT: Fixed title.
  2. I suppose can you use it through HFAAO folder.
  3. If you're asking if you can slipstream post SP4 hotfixes you want with HFSLIP, obviously yes.
  4. As you posted in this subforum I suppose you're referring to 2003 SP2 server. See this and this.
  5. You have to edit a profile for your program before using it. Then select that program and then apply its profile.
  6. If you followed that tutorial, O2K.exe should be a SFX file and you should have used the following in the SFX settings file: Setup=PRO11.MSI /QN So "silent install command" should be O2K.exe
  7. Haven't played with MKV but when I played with OGM some years ago (also a rich feature container no longer developed), I finally prefered to use simple avi as it also support more than one audio stream muxed, and you can add subtitles in .srt (editable text) in the same folder. Easier. I'd only use MKV if I were looking for compact neat results or for streaming capabilities, and in that case I'd keep an eye on the possible incompatibilities of the format on some hardware or software player, though it seems MKV is more widely adopted than OGM was.
  8. 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??
  9. First you need to know the route to your xpsource folder, x: (unit letter) \folder\folder\xpsource\... Go to the command line and type: cd /d x:\folder\folder\xpsource\i386 Then follow the intructions above exactly.
  10. Check event viewer for errors.
  11. It's compressed you have to expand it previously, follow the instructions exactly, when I say run I mean from the command line.
  12. 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.
  13. Sorry the link I posted is only to uninstall the feature not to remove it from the list. And you have it uninstalled. If you want remove the feature permanently in your XP source do: - Run ..\XPSOURCE\I386>expand -r netoc.in_ - Edit netoc.inf and remove "BEACON" under "[Optional Components]" section. - I suppose the sections and strings referring to the components you're removing can also be removed though nLite don't do it. So not sure of this point. - Save and run ..\XPSOURCE\I386>makecab netoc.inf - Run ..\XPSOURCE\I386>del netoc.inf netbeac.in_
  14. Special Edition including a big format photo of Chris programming nude! Good luck with your new product.
  15. strel

    net framework

    karthiga, that doesn't help. b-man read about that error in Silent .NET Maker synthesized guide.
  16. Not sure but I'd try removing SNMP from services section for Management and Monitoring tools and for Networking Services, Aplication Layer Gateway from Services section and Peer to peer from Network section. Check dependencies.
  17. Kurt states that add-ons added at nLite hotfix stage doesn't fit with XP x64 causing file association problems. So, I'm not sure, but I suppose he is only referring to T-13 add-ons, and if that's correct, it would be possible to make working RunOnce add-ons for both that would work with RVMI and HFSLIP, and as long as you don't use conflictive entries.ini settings, with nLite.
  18. 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?
  19. There's a bit of confusion here, what Kurt call add-ons are not add-ons in nLite, RVMI or HFSLIP terms (compressed and with an entries.ini file), furthermore Kurt don't recommend this kind of add-ons for x64, but what Kurt call add-ons in the first post goes in the \Addons folder. Kurt_Aust I've never heard of that file associations problem with XP x64 add-ons (apparently, from what I read here, it seems to affect only to T-13 add-ons), but apparently there seemed to be some x64 add-ons around working. What's exactly happens? Is it only on some apps? x64 RunOnce or RunOnceEx add-ons works right? Apparently working x64 add-ons around are not T-13 add-ons?
  20. Having the installer you don't need to build an add-on. you can schedule the installer execution manually with the install method you want. But if you want to schedule it automatically with an add-on (not hotfix add-on, nLite process add-ons in the hotfix section because nLite was designed to use T-13 add-ons, using the same install method that many hotfixes), then for a .NET 2.0 only add-on, I recommend you to try to build a T-13 add-on, it's easier. You should read this to understand what T-13 install method do. You can pick any T-13 add-on you find, and see its structure, specially the entries.ini file, to have a model. You have the link to the entries.ini documentation in my first post above.


×
×
  • Create New...