Jump to content

Chax0

Member
  • Posts

    4
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About Chax0

Contact Methods

  • Website URL
    http://

Chax0's Achievements

0

Reputation

  1. I am using nLite 1.4.9.1 on a Windows 2003 box to modify a Windows 2003 source and am having the following issues in the Entries.ini file of an addon I am trying to create. This seems to work, because nLite does add the section headers to the appropriate files: [AddDirective] WINNT.SIF, AlphaSection SVCPACK.INF, BravoSection However these do not seem to work: [EditFile] WINNT.SIF, AlphaSection, AlphaEntries SVCPACK.INF, BravoSection, BravoEntries [AlphaEntries] AlphaKeyOne=AlphaValueOne [BravoEntries] BravoKeyOne=BravoValueOne Are these known issues with nLite or with nLite on Windows 2003, or is this an understanding issue on my part? If it is the latter, how can I fix the error? The nliteos web site is very thin on details on entries.ini syntax, and even MSFN does not seem to turn up too much info on the subject. Also, what does [ExtraFileEdits] do? From what I can gather, it is a means to replace/substitute entries in INI/SIF files rather than to add entries, yes? Finally, how can I create an Addon that adds files to some place under $OEM$ rather than under I386?
  2. OK, can someone confirm for me that I am not doing anything blatantly wrong in creating my addon in the fashion described. When I was using msistub.exe (with arguments), I would get a dialog box in the middle of my install (at T-12 actually), that would make it appear that I had not supplied any arguments to msistub at all. With msiexec.exe, I see no dialog box nor any progress bar, and there is no installation either. I have noticed that some other AddOn publishers recommend that their addons be run during the RunOnce stage, but have not been able to understand what distinguishes an addon to be a T-12 vs a RunOnce candidate. Maybe someone can explain that to me?
  3. I would like to request for help in creating a nLite addon for TortoiseSVN addon for version 1.5.5.14361. This is an MSI installer that can be found at http://downloads.sourceforge.net/tortoises....4.msi?download. I tried creating the addon as a CAB file myself but do not seem to be having any luck in installing it with my W2k3 installation. The command file I use to create the CAB file is as follows: @makecab /f TortoiseSVN.ddf My DDF file looks like this: .set RptFileName=nul .set InfFileName=nul .set MaxDiskSize=cdrom .set CompressionType=LZX .set CompressionMemory=21 .set DiskDirectory1=.. .set CabinetName1="TortoiseSVN.cab" .set DestinationDir= .set SourceDir=..\TortoiseSVN entries_TortoiseSVN.ini .set DestinationDir=svcpack .set SourceDir=. msiexec.exe .set SourceDir=..\TortoiseSVN\svcpack TortoiseSVN-1.5.5.14361-win32-svn-1.5.4.msi and my entries_TortoiseSVN.ini file looks like this: [general] builddate=11/30/2008 description=TortoiseSVN language=English title=Subversion Client version=1.5.5.14361 website=http://tortoisesvn.net/about [EditFile] I386\SVCPACK.INF,SetupHotfixesToRun,AddProgram [AddProgram] msiexec.exe /i TortoiseSVN-1.5.5.14361-win32-svn-1.5.4.msi /qb /norestart I have also tried using msistub.exe instead of msiexec.exe, and have even tried using the msiexec.exe that is built into the Windows being installed, rather than providing my own copy inside the CAB file but nothing seems to work. I'd appreciate some help from the installer addon gurus out there!
×
×
  • Create New...