ZoSTeR

Most of the extensions create/modify several files in the profile folders. Just copying the extensions folder is not enough. There doesn't seem to be an elegant way to distribute extensions with firefox. Mozilla has a command line switch to install extensions but that's missing in firefox afaik.

edited: too slow

It seems that the standard api command for a shutdown doesn't work in BartPE. Look here for a workaround.

This works for all Inno Setups if the author specified the components.

You could use AutoIt to get rid of the wizard window. But the main question is why does the wizard appear in the first place? Do you use nLite or some registry tweaks to remove files/drivers? Have you tried it on a pure unattended installation with just the Daemon Tools installer?

You have to add an escape character: " becomes \"

The keyboard shortcut is stored in the shortcut .lnk file. You could use AutoIt's FileCreateShortcut function to create a new .lnk file with the desired keyboard combination. Or use this program to create one.

Are the file names correct on your cd? Maybe you turned off Joliet file names while burning the cd/creating the iso?

I found two programs that allow you to convert the Visual Basic setup.lst into an Inno Setup script. The first is the well known ISTool. The second is InnoScript. It's your decision if it's worth the effort. But it really isn't that difficult.

I guess it asked you whether to overwrite some files or not. You'll have to edit the setup.lst manually to remove the offending files and try if your application still works. Look here for an explanation of the Visual Basic Setup files.

Try setup.exe /s c:\logfile.txt

You can download a trial version of Registrar unless your setup takes longer than 21 days

Registrar CL is a powerful command line based registry editor.

The command line tools for formating and partitioning are FORMAT.com and DISKPART.exe in system32. Here's an example. If you want to create a boot disk have a look at BartPE.

The script above is not complete. It's an example of how to manipulate controls with AutoIt. Sometimes AutoIt is a little fast with clicking the controls. Try adding a Sleep (500) before each command and see if that works. Use the AutoIt Spy to get the rest of the control names and follow the scheme in the script.

Or is that a typo?

If you know the name of the Program Files folder and it's partition beforehand the easiest way is to add this to the winnt.sif: [Unattended] ProgramFilesDir="D:\My Program Files" CommonProgramFilesDir="D:\My Program Files\My Common Files" If you want to change it after setup has begun you can modify the registry as mapoupier mentioned but this will f*ck up IE/OE because they use the variable %ProgramFiles% in their paths. Look at this thread for a solution.

To call a vbs script from batch files use: start myscript.vbs or cscript.exe myscript.vbs PS You should run another .cmd /.bat file from cmdlines.txt. Start everything else from that file.

That's because there are no spaces in their file paths. Is your Batch_file.cmd being started at all?

Nope. GetRight is the best

Seem's like uncle Norton is eating all your memory Try installing NAV at the end or get a leaner anti virus app. And what app are you installing at that moment? The name is obfuscated in the screenshot. How much physical memory do you have?

A little debugging advice: Remove the @ECHO OFF and add a PAUSE after every start command. This way you see what going wrong in your batch. And you must add quotes around paths with blanks in them or better yet remove the blanks all together. start /wait %systemdrive%\install\Applications\Deamon Tools\daemon343.exe /S /Wshould become start "" /wait "%systemdrive%\install\Applications\Deamon Tools\daemon343.exe" /S /W

Well there are several automation/macro programs out there: Automate, WinBatch, EZ Macros... Look here. The problem is that most of them don't compile stand alone exes. Try AutoIt. If you read the help file you'll see that programming ain't that hard. At least when it's no C syntax

Try: Setup.exe -r -f1"c:\setup.iss" -f2"c:\logfile.txt"

It's a self extracting cab file. Extract the content to a folder and run dunsetup.exe from there. Dunno if it works, I'm running XP