Arie

Tip: For drivers, add those from DriverPacks, but make sure to add those last to your installation.

Can you remove some of the silent installers and add them one by one or two at once for example to find out which installer is causing the problem? Can you post the content of your SVCPACK file?

Glad I could be of service

I have tried it, but I prefer WMP11 Slipstreamer. Sorry.

Doing it differently now. I've used Silent .NET Maker to pack Microsoft .NET Framework 1.1 and 3.0 into only one file. I will use HFSLIP later on today to cook up a new image after which I will test it. Crossing my fingers...

You can either (1) use a batch file to install all hotfixes or (2) integrate them into your source files. The first option will install a clean copy of the operating system, afterwhich all the hotfixes are applied. This means that your installation media will contain for example 500MB worth of operating system and 200MB worth of hotfixes. Your hard disk will contain in this example an up-to-date operating system worth 1500MB with an uninstall folder for each hotfix, totally worth 500MB. The installation media for the second option will contain the operating system, with all the hotfixes integrated. This means that the old and/or no longer needed files are deleted and/or replaced by the updated files. The operating system will not be 500MB anymore, but 600MB. However, you will no longer have all the hotfixes seperately on the installation media, so in this example you will have gained 100MB on the installation media. Your hard disk will contain in this example an up-to-date operating system worth 1500MB. However, you will no longer have an uninstall folder for each hotfix, gaining you 500MB. The choice is simple I think Microsoft has included an /INTEGRATE option for all recent hotfixes by the way, so you don't need nLite or HFSLIP to update your source files necessarily. Hope this helps!

Your question is put either too simple (b) or the answer to your question is simple (a). I'll start with the last option. (a) You simply want to add a folder to your ISO-file in which you want to put some applications and perhaps some installation files for later use. Extract the ISO-file to a folder on your hard disk. Create the desired folder and place the applications which you want to include in this folder. Use an application such as BBIE to extract the boot sector of your CD; you'll need to burn the ISO-file first or mount it on a virtual drive. Burn the whole folder from your hard disk using for example Nero, adding the extracted boot image to make your CD bootable. (b) You want to create an unattended installation CD, based on an ISO-file, and add several applications to the CD, which should all install automatically during setup. You cannot simply add a "Program Files" folder to your CD; it will not install your applications automatically. Download HFSLIP and/or nLite. Extract the ISO-file to a folder on your hard disk. Read the manual for both before mentioned applications and spend hours and hours to create an installation CD which is completely of your liking. Read through the HFSLIP and nLite sections of this forum. A good starting point for creating your own unattended installation CD can be found here. ... or © Neither (a) or (b) are what you're after. If so, please clarify your question. Hope this helped!

First of all, are you sure that the file name is correct: wmp11-windowsxp-x86-FR-FR.exe? But to answer your question, I believe that you have placed the above mentioned file in the wrong folder. I believe that you have placed it in your HFSVCPACK folder, whereas you should have placed it in your HFSVCPACK_SW1 folder. Can you please check this? If you have placed the file in the wrong folder, move it to the correct folder, cook up another image and it should work.

Just posting a few lines to say hi to everyone I'm fairly new in the world of unattended installations, but I've been enjoying myself for the past few days trying to cook up an unattended Microsoft Windows XP Professional installation disc, which will install fully up-to-date and pre-configured. It's not going completely smooth yet and this forum has been a great help already getting some of the problems which I encountered solved up till now. I hope to learn from other people on this forum who have done this already and I hope that I can contribute and help others in return. Hope to see you around

Integrating Tweak UI can be done very easily. Download Tweak UI from here. Extract the file TweakUI.exe from the self-extracting EXE-file using for instance WinRAR. This is the only file you will need from the package. If you are using HFSLIP, move the file TweakUI.exe to the following folder: HFEXPERT\WIN\system32. If you are not using HFSLIP, you will have to use $OEM$ Distribution Folders. Move the file TweakUI.exe to the following folder in this case: $OEM$\$$\system32. When you would install Windows XP now, TweakUI.exe will be in your WINDOWS\system32 directory. It will however not be linked from the Start Menu for instance. Personally, I always delete the Start Menu entries for Tweak UI when installing manually and instead add a shortcut to Tweak UI in the Control Panel. To do this automatically during installation, add the following REG-file to your installation: Windows Registry Editor Version 5.00 ; Add Tweak UI to Control Panel [HKEY_CLASSES_ROOT\CLSID\{D14ED2E1-C75B-443c-BD7C-FC03B2F08C17}] @="Tweak UI" "InfoTip"="Customize Windows from one location" Hope this helps!

I've used Silent .NET Maker to pack Microsoft .NET Framework 1.1, 2.0 and 3.0 to use with HFSLIP 1.6.2. I placed all three files (DNF11.exe, DNF20.exe and DNF30.exe) in my HFSVCPACK folder. The installation of Microsoft Windows XP Professional with Service Pack 2 goes fine until the T-13 mark. Microsoft .NET Framework 1.1 is installing fine, followed by 2.0, however once installing Microsoft .NET Framework 3.0 it returns an error code: Windows Communication Foundation -- Error 1304.Error writing to file: Microsoft.Transactions.Bridge.dll. Verify that you have access to that directory. There is already a topic regarding this error message, but it concerns the above error code when you install Microsoft .NET Framework 3.0 via RunOnceEx. What can I do to solve this problem and have it properly install at the T-13 mark as both Microsoft .NET Framework 1.1 and 2.0 do?