Aaron

Installshield is supposed to be the easiest one. When you create the setup.iss file you can define a destination drive and directory to install to. But... if your test system for creating setup.iss files doesn't have a secondary drive/partition, then install it to the C:\ drive. Afterwards, open up the setup.iss file and edit the path. Example: [InstallShield Silent] Version=v6.00.000 File=Response File [File Transfer] OverwrittenReadOnly=NoToAll [{51C8741C-4A91-42A6-B6A2-CB891F7398A1}-DlgOrder] Dlg0={51C8741C-4A91-42A6-B6A2-CB891F7398A1}-SdWelcome-0 Count=4 Dlg1={51C8741C-4A91-42A6-B6A2-CB891F7398A1}-SdAskDestPath-0 Dlg2={51C8741C-4A91-42A6-B6A2-CB891F7398A1}-MessageBox-0 Dlg3={51C8741C-4A91-42A6-B6A2-CB891F7398A1}-SdFinishReboot-0 [{51C8741C-4A91-42A6-B6A2-CB891F7398A1}-SdWelcome-0] Result=1 [{51C8741C-4A91-42A6-B6A2-CB891F7398A1}-SdAskDestPath-0] szDir=D:\Program Files\Kerio\Personal Firewall Result=1 [{51C8741C-4A91-42A6-B6A2-CB891F7398A1}-MessageBox-0] Result=1 [{51C8741C-4A91-42A6-B6A2-CB891F7398A1}-SdFinishReboot-0] Result=1 BootOption=0 (if you're wondering how to create setup.iss files, see this page

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce] "NameOfApplication"="C:\\Program Files\\example\\example.exe" Since you want to execute a reg key, you will be prompted when XP boots up if the reg key path is in RunOnce, so put a path to the batch file instead that will use REGEGIT /S You probably will see a quick flash of the command prompt box on boot up P.S. you do need to use double backslashes for a path in a registry import.

Change it to what exactly?

I can see the problem. Assuming your CD directory layout is set as: X:\$OEM$\$1\install\Tools\ and that both files are in the Tools folder, then: COPY "psshutdown.exe" "%systemroot%" should be COPY "%systemdrive%\Install\Tools\psshutdown.exe" "%systemroot%\" and COPY "deluser.exe" "%systemroot%\" should be COPY "%systemdrive%\Install\Tools\deluser.exe" "%systemroot%\"

No, I didn't have any luck installing SB Live! drivers using OemPnPDrivers, since it requires that Setup should be run instead of using the INF files. That is what I meant on the bottom of the drivers page. See if Setup on the Audigy 2 CD can run silently, then install the updated drivers silently afterwards. Looking at my extracted drivers, it appears to be using Installsheild, (should be the same for your CD too) so you can customize your setup options. good luck!

http://www.snpsoftware.com/

I've looked at Macromedia Dreamweaver, Extract and create a setup.iss file All of the Macromedia apps appear to be using Installshield.

I never needed to install apps on a different partition so I don't know. I will research it though!

Backup is probably a feature for XP Professional Only

Audigy 2 drivers for the CD-ROM? huh...? Audigy 2 is a sound card... or were you calling the external audigy 2 device a CD-ROM? Anyway, most drivers shouldn't really need the CD first before updating. See if the Soundblaster.com site has a latest copy of audigy drivers

Control Panel > Add/Remove > Repair Internet Explorer 6. Reboot.

Do you mean the area in the red marked box is missing?

Ok I managed to find out where Windows set the driver signing policy option in the registry using an app called regmon. Use this registry key: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Driver Signing] "Policy"=hex:00 This will tell to ignore driver signing.

Great work, will look into it properly tomorrow, getting late here in the UK now

For example, if your own user account is called JohnDoe with a password of 66487 on the first PC, then make the same identical account on the other PC - JohnDoe with a password of 66487.

I find that quite risky... several setup applications running at the same time are bound to conflict into each other

Program Name : Daemon Tools Program Version : 3.33 Switch : /QB or /QN Full : daemon.msi /QB Extraction : Yes Registration : No

I couldn't find much in the Knowledge base for issues regarding DriverSigningPolicy=Ignore These is all I could find: http://support.microsoft.com/default.aspx?...kb;en-us;293765 http://support.microsoft.com/default.aspx?...kb;en-us;314479 -- UnattendSwitch Specifies whether Setup skips Windows Welcome or Mini-Setup when preinstalling Windows XP Home Edition or Windows XP Professional using the CD Boot method. Syntax UnattendSwitch = Yes | No Yes Instructs Setup to skip Windows Welcome. No Instructs Setup not to skip Windows Welcome I used no so I could create a user account to log into for the batch to install my specific reg entries into.

This appears to be a problem with the user account permissions - Make sure that both machines have the same username and password. You might also want to check the permissions of the shared printer and allow Administrators to access it. If no avail, then add "Everyone" to it.

What Operating System?

Yeah I remember now, its hard to keep track of what everyone's doing.

Ogre's answered them, for the rest - its left me stumped!

When you say that applications.cmd stops, does the system restart? It looks like Winfast TV Tuner Apps is causing the problem, a bad setup.iss file is most likely.

Find out what installer McAfee uses, then work your way from there from the three links at the bottom of the Applications page at: http://www.MSFN.org/unattended/xp/applications.htm McAfee is bound to be using Windows Installer, or Installshield for a popular program. :-)

Nope, you only need this line in [unattended] DriverSigningPolicy=Ignore Have you fully read the Drivers page or are you reading it very briefly? Using an older version of WinRAR? I tested this switch again on WinRAR 3.20 (killing explorer.exe and running it from command prompt) nothing opened at all. Was the psshutdown.exe file copied over earlier to %systemroot% in the batch? If there's still a problem then use %systemroot%\psshutdown.exe instead