Justin-Credible

@Cobyjones: Ahh I see. I will look into this. @Lost Soul: Thanks!

NikLoK: I'm not sure If I understand what your question is. If you are asking if different versions of Windows files can be included on the disc... the answer is no. cobyjones: I was able to add 6 parameters into the box (see attachment). What three are you trying to add, and in what order?

Wow, didn't expect to see so many posts here! Lets see... Bilou_Gateux-- I haven't messed with MUI packs or different languages of Windows. All I can say is... give it a try I would suggest using VirtualPC or VMWare to test your disc before you burn it. Let me clarify something here... The "Windows Installation Source CD" is the path to the files of the version of Windows you want to install on the target computers. The "Windows XP or Windows 2003 Server" is the path to a version of Windows (XP or 2003) that you will use to build the CD and its graphic interface (this has nothing to do with the OS that is installed, it simply makes the interface). The only combination of the two that will have problems is if you are using a Windows XP SP2 or Windows 2003 Server SP1 disc as the "Windows XP or Windows 2003 Server" with Windows PE 1.2. This causes the Disk Partitioning feature to not work because of a bug in Windows PE 1.2. I did see the Q/A about the DComLaunch Service from BartPE, but I didn't have time to get this to work in Windows PE. I do plan to fix this in the next version. As far as files that are used from the Windows PE CD; only the files under the WINPE folder are used. I did plan on doing a version that would allow you to use either WinPE or BartPE to build the disc, but again due to time limitations I didn't get to include that feature in this version. As for the drivers question; The "Drivers to Install with Windows" are driver sets (.INFs with a bunch of additional files such as .SYS, .VXD, .DLL, etc). These are the drivers you normally download from the web or get from a motherboard CD. These drivers are copied to the root of the hard drive, are are added to the unattended answer file (WINNT.SIF) so during Windows PnP hardware detection, the drivers will be automatically installed. These drivers are stored in the \AI\SOURCE\i386\$OEM$\Drivers folder on the CD. "Drivers Used During Install (Mass Storage Drivers)" are drivers (.SYS) that you normally nload by pressing F6 during a normal install of Windows. This is a driver file that allows you to access a hard drive that may be on a SATA or SCSI controller that WinPE doesn't include by default. This gives you access to the hard drive during bootup and will allow you to install files to the HDD. These drivers are added to the TXTSETUP.SIF file and are placed in \i386\SYSTEM32\DRIVERS directory on the CD. So if you need a mass storage driver, yes, I do believe you will also need the drivers for the "Drivers to Install with Windows" section. Here is what I have planned for the next version: Windows 2003 Small Banner Option Fix spelling errors Support for BartPE Ability to use the /noguiboot switch Include XCOPY for those systems that do not have it

oops. Thanks for letting me know. I had a hard time getting those drop down boxes to work, I guess I was so tired of working on them I never came back to check them after they were working.

Cool tool. In my CD building tool I have similar functionallity for the unattended file. The parameters you choose will be requested at the beginning of the installation process (right after the CD has booted up). Screenshot here In this case the ComputerName value is requested before the process begins. When it is entered, it is merged into the unattended answer file.

I took a look at WPI, and I have to say I was quite impressed with it being a HTA and all. I don't think I will be adding it into AutoInstall CD-ROM Builder because it is a bit more advanced to setup and get working for a normal user. However my program does have an option to add additional files before the ISO is finalized, so you can add it manually.

We use Active Directory where I work so all the applications and settings are pushed out when the computer reboots after the install. For the next version (if I have time ) will be to add more customization (for RUNONCE and other things that will let you install applications after reboot). Any other suggestions would be appreciated!

I've been developing an application off and on for a year or so. Its basically a front end for building a bootable CD that automatically installs Windows. You can add drivers, customize the unattended answer file, specify how the hard drive should be formatted etc. Then you burn the ISO to disc and you have a fully automated Windows (2000 or XP) install disc. I originally designed this for my co-workers to use after I leave (I'm the only one who was able to create automated installation discs for them), so it should be easy enough for anyone to use. It does make use of Windows PE, so you will need a WinPE disc to build your ISO. I used a lot of information from the Windows PE board here (great forum!!) and I thought someone might find this tool useful. You can download it here: AutoInstall CD-ROM Builder And some screenshots: Click Here