prior to running your install of WPI i tested 5 individual installs of office, project, visio, onenote and frontpage. all were successful. All of my codes end with /noreboot so this should set the installer not to reboot but it does on the second instance of an office instalation or something tricks WPI into thinking it should reboot. I dont know coding but i do know logic. I only use one line of code per instalation, as shown below. %cdrom%\office2003\office\setup.exe TRANSFORMS=Unattended.MST /qb- /noreboot %cdrom%\office2003\frontpage\setunext instalation p.exe TRANSFORMS=Unattended.MST /qb- /noreboot %cdrom%\office2003\visio\setup.exe TRANSFORMS=Unattended.MST /qb- /noreboot %cdrom%\office2003\project\setup.exe TRANSFORMS=Unattended.MST /qb- /noreboot %cdrom%\office2003\onenote\setup.exe TRANSFORMS=Unattended.MST /qb- /noreboot none of that should be new to you of course but if i were to add a second comand line per install which was noreboot would WPI look at that and not reboot? How could i code that into the second command line or is it a non starter. another option would be to try and delay the start of the ofending instalation by some sort of time loop How could i code that into the second command line or is it a non starter as well. I am just thinking out loud it might help or on the other hand i might be talking drivel.