Arie

Asking your question once is enough, instead of asking the same question three times: one, two, three

Click here and also see all subcatagories.

... should be changed in: RunProgram="hidcon:Exec.cmd"

I didn't mean my reply rude, hence I included a smiley in my message. Written text can always "sound" different than how it's intended. Smilies can therefore be used to show that something isn't meant in a bad way. I was in fact trying to help. It took me less than five minutes to download QT Lite 2.3.0 and to create a silent installer package for it and by creating it myself I'm not dependent on anyone. Once again I don't mean all this in a bad way, I'm only trying to be of service. My reaction was almost correct; the following is the correct command: qtlite230.exe /VERYSILENT I hope that you'll see that I'm trying to help, not trying to rude. My apologies if I did sound rude, but please note the smiley in my previous message.

If you need to import your registry keys before or after the installation of this application is something which you can only find out by testing it. My experience is that most applications don't mind which order you choose, but personally I prefer to import registry keys after the installation of an application, as it could be perhaps that an application changes the keys which you import before the installation. Importing the keys after installation is therefore in my humble opinion "safer". I don't know "Registry Ripper". You can export keys from your registry simply by using REGEDIT. If you don't quite know what keys to export, you can use Regshot, which is a small, freeware registry monitoring tool, which lets you see what keys get changed, afterwhich you can choose which of these keys you would like to export using REGEDIT. Once you have exported the keys which you believe that you need, test your unattended application installation process to see if the application installs silently and if it's configured as you wish.

Attach your last session information. According to the nLite FAQ.

You're welcome

Google could have answered your question easily in my humble opinion

No, just run the installation file of this application with it's parameters, or run your AutoIT script.

Yes, simply run your file.

During the textmode copy process it can't find the file SP2.CAB. I'm a bit puzzled why it doesn't work as I don't believe that I've done anything wrong. Everything went fine in the recent past. I don't recall what I've changed since, but now this error pops up. If I have a look at the SOURCESS folder, SP2.CAB is indeed missing there. It is located in my SOURCE folder however. It seems like it just isn't copied over. I tested with both version 1.7.3 as well as 1.7.4 RC2 (80123b); same problem. HFSLIP.zip

You cannot use batch scripting for that I'm afraid. You could use Visual Basic for example, or AutoIT, et cetera.

Simply set the NTFS rights the way you want.

What exactly are you trying to do? To me it sounds like you could better use AutoIT, but this is only based on the little information which you supply.

I can't answer your question, but the time it has cost you to write your reaction, you could have created a silent, self-extracting package yourself for this application By heart I believe /silent does the trick.

As you didn't include your session information, I can only assume (I'm 99,999999% sure ) that you removed these games from your installation source using nLite. If you would have read the nLite FAQ, you would have read that reinstalling removed components is most of the time not possible or very difficult to do, which would mean that you will need to start over from scratch. But what I wonder is why you or anyone else for that matter would even bother to remove any components at all from your installation source? This can only cause troubles in the future. If I don't want certain applications not to install, such as these games, I simply don't have them install during my unattended setup. Why would I want to remove them from my source? Removing them only causes problems such as yours. Removing them because it gives you more space on your installation disc? I use DVD's, so I've got plenty of space Ah well, enough ranting

I made a mistake in my previous posting, my apologies for that. I've editted my previous posting. I personally prefer HFSLIP over nLite. I have tested nLite in the past, but in my humble opinion it takes away too much control over my unattended project. For people who want a straight forward and easy solution, I have no doubt that nLite is a nice tool. For more control, it's always best to do everything, or as much as possible, yourself. If you do as much as possible yourself, you know exactly what everything does and you're never dependant on others. Integrating hotfixes, creating your own silent, self-extracting application packages and adding those to your project, applying tweaks, et cetera, these are all things for which you basically don't need third-party tools to do all the work for you. Yes, you will need to use tools such as 7ZIP or WinRAR for example to create your own packages, but the end result will be your self-created package of which you know exactly how it works, which you can update or change yourself, et cetera. Using packages made by others as most nLite users to, you make yourself dependant on others. In my case, I would always want to check the packages made by others because I would want to know what their packages do. Who knows, they might contain a backdoor, errors, et cetera? I prefer to be in control HFSLIP is a big script. You can go through it and see what it does. With nLite you have to trust the creator. Not that I don't trust the creator, but still I would like to know what the application does exactly. HFSLIP takes away tasks such as integrating hotfixes for me. Since I can see what HFSLIP does by looking at the source, I let HFSLIP take care of this job instead of doing it myself. There is something that nLite can do which HFSLIP doesn't and that is remove components completely from your source. This however is functionality which I don't use and never want to use. Remove components is in my humble opinion not necessary; if I don't want something to install, I don't let it install, so why would I want to remove it from my source files? Because it takes space on my installation disc? I use a DVD so I have plenty of space And when upgrading to future Service Packs for example, my installation won't complain that certain things are missing from my installation disc and such Anyway, I prefer HFSLIP. Others will prefer nLite. This will generate a whole "fanboy" discussion Give both a try yourself and see what you prefer and stick to that.

I honestly have no idea what you're on about in regards to "the article"?! See the top post in this thread in regards to the $WIN_NT$.~BT folder. As for expanding the files in $WIN_NT$.~LS and adding those to my installation source, this is something which I'm figuring out myself. I hope though that "gosh" can answer my questions as it will save me the work of testing; there is no need to reinvent the wheel of course

Thank you for the link, but I don't want to use any scripts others have written when I can do the same myself fine as well I only use HFSLIP and RogueSpear's Microsoft .NET Framework packages, everything else is done by myself and I would like to keep it that way

1. There is a separate nLite section on this forum. Please ask a moderator to move your question there. 2. You give too little information for any nLite user to answer your question. You will need to supply information on which packages you used and how and the error message which you receive. It might also be useful to attach your last session information to your posting. Personally I don't use nLite, so I can't be of service. I prefer to use HFSLIP as it gives me greater control over my project. Integrating the latest DirectX 9c components and all versions of Microsoft .NET Framework don't give me any problems using HFSLIP.

Having a quick look it seems like you're killing the installer tasks themselves, but by the time your kill command runs, the installer will always be done already. I believe what you would like is that once the installation process is done, if the application auto-starts straight away, you would like to kill it. This means that you need to replace those wrong installer executable names with the names of the files which start as soon as the installation process is done. An example: say you run BLAHSETUP.EXE first, currently you kill this process as a second step, but this won't do anything as the installation process will have already completed. Instead of killing BLAHSETUP.EXE, you need to kill RUNBLAH.EXE. Hope this makes it a bit clear. I'm not that good in explaining these things as to me this is all clear and I never even think about it, so explaining is somewhat difficult

Here's an excerpt from my one of my own scripts. REM DELETE SHORTCUTS DEL /F /Q "%AllUsersProfile%\Start Menu\Set Program Access and Defaults.lnk">NUL DEL /F /Q "%AllUsersProfile%\Start Menu\Windows Catalog.lnk">NUL DEL /F /Q "%AllUsersProfile%\Start Menu\Windows Update.lnk">NUL DEL /F /Q "%UserProfile%\Start Menu\Programs\Accessories\Tour Windows XP.lnk">NUL REM DELETE FOLDERS RD /S /Q "%AllUsersProfile%\Start Menu\Programs\Powertoys for Windows XP">NUL RD /S /Q "%UserProfile%\Start Menu\Programs\Powertoys for Windows XP">NUL RD /S /Q "%ProgramFiles%\Common Files\Services">NUL RD /S /Q "%ProgramFiles%\Online Services">NUL RD /S /Q "%SystemRoot%\$Nt*$">NUL RD /S /Q "%SystemRoot%\setup.pss">NUL REM DELETE SAMPLE CONTENT DEL /F /S /Q "%UserProfile%\My Documents\My Music">NUL DEL /F /S /Q "%UserProfile%\My Documents\My Pictures">NUL DEL /F /S /Q "%UserProfile%\My Documents\My Videos">NUL REM DELETE FAVORITES DEL /F /S /Q "%SystemDrive%\Documents and Settings\Default User\Favorites">NUL DEL /F /S /Q "%UserProfile%\Favorites">NUL REM DELETE FILES DEL /F /S /Q "%SystemDrive%\clock.avi">NUL DEL /F /S /Q "%SystemDrive%\swtchbrd.bmp">NUL DEL /F /S /Q "%SystemDrive%\yahoo.bmp">NUL REM DELETE TEMPORARY FILES DEL /F /S /Q %SystemDrive%\~*.*>NUL DEL /F /S /Q %SystemDrive%\*.~~~>NUL DEL /F /S /Q %SystemDrive%\*.~m~>NUL DEL /F /S /Q %SystemDrive%\*.###>NUL DEL /F /S /Q %SystemDrive%\*.$$$>NUL DEL /F /S /Q %SystemDrive%\*.--->NUL DEL /F /S /Q %SystemDrive%\*._mp>NUL DEL /F /S /Q %SystemDrive%\*.bk!>NUL DEL /F /S /Q %SystemDrive%\*.tmp>NUL DEL /F /S /Q %SystemRoot%\*.bak>NUL DEL /F /S /Q %SystemRoot%\*.log>NUL DEL /F /S /Q %SystemRoot%\TEMP>NUL Hope this gives you good start

Why not simply do everything from scratch yourself? It sounds like a lot of work, but trust me, it isn't. Using HFSLIP it's a piece of cake.

Instead of using your current method, why not simply use HFSLIP instead? It seems to me like you're only using nLite partly, so why even bother using it at all? Using HFSLIP I encounter none of the problems which you mentioned in your first posting. /EDIT "Using nLite I encounter" -> "Using HFSLIP I encounter"; I do not use nLite.

1. There is a special section for these kinds of questions here. Please ask a moderator to move your topic. 2. To me it sounds like you simply installed the Yahoo! Toolbar. Have you checked your machine for suspicious processes using Process Explorer for example and HijackThis?