Arie

DriverPacks should go last.

Nothing really, as everything you need to know can be found in the Unattended Guide. Have a look there at the various types of installers for example. Also, search the forum for parameters to install your applications silently. If you run in to problems with specific applications and the Unattended Guide and the search function on this forum doesn't help you any further, let us know what the problem is which you encounter.

You seem to be somewhat confused. To keep it as simple as possible, when you normally install an application you click for example "Next", "Next", mark a few checkboxes, et cetera and click "Finish". You can automate this process using AutoIT, that's all. If you would automate an installation using AutoIT and you would like to have a silent installer, you would still need to package your application. But please note that you hardly need to use AutoIT for automating any installations. Most applications allow command line parameters to configure their installation, so instead of automating the installation using AutoIT, you could simply run the installation like this for example: setup.exe /silent /components:main (this is of course just an example which I made up myself). You can then create self-extracting, silent installer packages using for example 7ZIP or WinRAR which automatically launches the installation with the required parameters. I personally need to use AutoIT for only two applications: DNL Reader and GMail Drive (and perhaps even those could have been via other means, but I haven't found out how anyway ). For all my other applications I created my own self-extracting, silent installer packages. All applications which can be installed via SVCPACK are installed via SVCPACK. Applications which cannot be installed via SVCPACK are installed via RunOnceEx, straight from DVD.

Thank you for your posting Currently having a look at all this. Very interesting. Haven't tested all this yet, but I have followed your posting in regards to the $WIN_NT$.~BT folder for a start. I was wondering though if I could do the same in regards to the $WIN_NT$.~LS folder; expanding the files and placing those in the I386 folder to speed up the installation process?

Be honest, you didn't search, did you? Click here (or here) and here for a start.

Yes, there is a way. How you wonder now? I can't answer as you give too little information in your posting It depends on the applications for example. Certain applications allow parameters which lets you decide on where the application should be installed. Other applications could be repackaged to install to your required folder.

Not quite sure if I understand your problem, as I don't know if you rebooted after the installation process was done? Always reboot after the installation process is done before doing anything else, such as checking for updates.

If I'm not mistaken you cannot use OEM installation discs with nLite, such as those from Gateway, Dell, et cetera.

The file "execbat.dll" doesn't sound like a default Windows XP installation file, so apperantly you're adding other software, which might be the reason why you're experiencing this problem. You give too little information to be of more service I'm afraid.

If you would have looked, you would have noticed that there is a special nLite section on this forum, where you should have asked your question.

Did you perhaps modify your installation using nLite?

Click here for a list of all post-SP2 hotfixes compiled by Tomcat76.

There are too many users around who honestly don't search before asking. Ah well, here goes again... Microsoft .NET Framework 3.5 includes version 3.0 SP1 and 2.0 SP1. Microsoft .NET Framework 3.0 SP1 includes version 2.0 SP1. Microsoft .NET Framework 2.0 SP1 does not include version 1.1 SP1. For applications which require Microsoft .NET Framework 1.x, you will still need to install Microsoft .NET Framework 1.1 SP1 separately from the other versions of Microsoft .NET Framework. If would like to include all versions of Microsoft .NET Framework, you would therefore only have to install version 1.1 SP1 and version 3.5 of Microsoft .NET Framework. Note however that there are quite a few applications which state that they require Microsoft .NET Framework 1.x to properly function, also work when Microsoft .NET Framework 2.0 SP1 is installed instead, however this does not count for all applications which require Microsoft .NET Framework 1.x and not installing Microsoft .NET Framework 1.1 SP1 prior to installing any applications which depend on this version might result in error messages during installation of certain applications. To be on the safe side it would therefore be better to still install Microsoft .NET Framework 1.1 SP1 if you are using any applications which specifically depend on this version of Microsoft .NET Framework. RogueSpear offers switchless, silent installation packages of all versions of Microsoft .NET Framework via his forum. Please note that you will need to register to have access to these files. For the next procedure I advise you to use RogueSpear's packages. If you would like to install as many applications via SVCPACK.INF as possible, it's best to install version 1.1 SP1 and version 2.0 SP1 of Microsoft .NET Framework via SVCPACK.INF first, followed by any applications which depend on these. You can next install RogueSpear's Lite version of Microsoft .NET Framework 3.5 via RunOnceEx for example, once again followed by any applications which depend on either version 3.0 SP1 or version 3.5 of Microsoft .NET Framework. Some keywords for others who use the search function: Microsoft .NET Framework, DOTNET, 1, 1.0, 1.1, 2, 2.0, 3, 3.0, 3.5, SP1, SP, Service Pack, version, install, unattended, silent, package, RogueSpear, Rogue Spear, download, switchless, switch, switches, nLite, HFSLIP, installation, Arie, Lite, SVCPACK, SVCPACK.INF, RunOnce, RunOnceEx, applications, error, packages, pack, 7ZIP, 7, ZIP, command, MSI, help, hotfix, hotfixes, dotnetfx, integrate, dotnetfx.exe, ISO

Your posting contains too little information. Do you want to rip your CD's as fast as possible without any concern regarding the quality of your rip, or do you want to rip them as accurate as possible? Do you want to rip your CD's lossless or can it be lossy? Do you have a format in mind and if so, which and why? Do you want to rip your CD's directly into this specific format or rip them to your hard disk first as WAV-file and then later convert them into the final format of your choice (in case WAV-file is not the final format which you prefer)? I personally use Exact Audio Copy (EAC for short) to rip my CD's to WAV-files on my hard disk, afterwhich I use dBpowerAMP to convert the WAV-files to both FLAC-files (highest compression) as well as MP3-files (highest bitrate). I use my FLAC-copies as backups of my original CD's. The MP3-files are simply meant for my MP3-player, home cinema set, et cetera. EAC is freeware. dBpowerAMP is not, but it's worth the small fee which it costs in my humble opinion. You don't need to use dBpowerAMP though, as it uses LAME to encode to MP3-files for example and you can obtain LAME free of charge.

It's a simple MSI-file, so what's the problem?

Glad that you solved the issue. Just a small advice, why not simply install Office XP straight from CD-ROM instead of copying the installation files to your hard disk first and then installing it? Instead of using $OEM$-folders, you could use RunOnceEx to install Office XP straight from CD-ROM.

Will this mean that there will be a new SDK soon too?

An empty ZIP-file?

Since it's not connected to the network, you will have to physically be at the machine to solve this issue. Log in using a local account with administrative rights or by using a domain account which has administrative rights on the machine in question, but this last option will only work if the credentials are cached locally as the machine is not connected to the network. You could for example also simply connect the machine to the network (wired) and log in with a domain account which has administrative rights. If you want to solve this issue without connecting to the network via wire, then see the posting by "cluberti" above on how to reset the local administrator password offline. The method he suggests however will not show you the currect password, it simply allows you to change the password. If you need to know the current password, you could use rainbow tables for example to find out.

What is an "ime"? Assuming it's an application of some sort, you could have it install via SVCPACK.INF for example. You can use SVCPACK.INF for copy processes too, as well as applying Registry scripts.

Will have a look at this to see if I can put this to good use. I would like to redirect the folder My Documents to another drive. I could use this script for this purpose perhaps. Nice, thank you!

Old news, it was posted in the stickied Windows XP update thread already at the top of the HFSLIP section of this forum. This link always points at the latest update.

You obviously didn't perform any searching yourself, as there are plenty of topics regarding Microsoft .NET Framework on this forum which would have answered all your questions. I'm in a good mood however and I'll give you a short answer: the .NET folder in the root of your installation disc has nothing to do with the installation process; it doesn't get installed, it's not used by the installation process at all, you can compare it to the SUPPORT folder for example, it's safe to delete. Version 2.0 SP1 does not include version 1.1 SP1. Version 3.0 SP1 contains version 2.0 SP1. Version 3.5 contains version 3.0 SP1 and 2.0 SP1. If you want version 1.1 SP1 installed you'll need to install it seperately therefore. The version on your installation disc however is most likely an old version, so simply download the latest release of version 1 from the Microsoft web site. If you want the latest release of version 2, either install the latest release of version 2 as downloaded from the Microsoft web site or install the latest release of version 3 or 3.5, also as downloaded from the Microsoft web site. But you could have found all this easily yourself, so next time please search.

Remove Directory="" from your config.txt and try again.

Clean up your machine: temporary files, bad registry entries, uninstall unused applications, et cetera. Disable all visual effects: no effects, no fancy background, no fancy screensaver, no expanding menu's, et cetera. Configure your machine: disable all unnecessary services, disable all unnecessary start up items, remove all unnecessary tray icons and desktop icons, et cetera. Update your machine: install all required updates, scan your machine for adware and virusses, et cetera. This should give you a good start.