RDodson
03-06-2006, 11:30 AM
We noticed that when running the Setup Factor (7) in silent mode, it can take an *.inf file for setting parameters. The problem we are having is that it looks like we always have to provide the full path to the *.inf file on the command line. Is this correct? Is there anyway to tell the installer, from the command line, to use the *.inf file from same directory as the installer executable is located?
This may sound like a odd problem, so let me explain a little of the background. We have a product that using Setup Factory for installation. We have a customer that needs to deploy many, many computer, and they have an uber-installer which then installs a bunch of other installers including ours. They want the procedure to be full proof (i.e. no user interaction). There goal is to stick one CD in the PC and have the installer put everything needed on to the target computer. Setup Factory's silent mode is perfect, but there are some parameters that need to be configured, and the *.inf file is perfect for this. The problem is that they don't know what drive the CD-ROM is going to be on a given computer.
For example, they can do this:
setup.exe /S:d:\settings.inf
But this won't work if the CD-ROM drive is "E:".
What would be nice is if this worked:
setup.exe /S:settings.inf
and then the Setup Factory would look in the executable's folder for the *.inf file.
Any suggestions on how to get around this problem would be greatly appreciated.
Thanks.
This may sound like a odd problem, so let me explain a little of the background. We have a product that using Setup Factory for installation. We have a customer that needs to deploy many, many computer, and they have an uber-installer which then installs a bunch of other installers including ours. They want the procedure to be full proof (i.e. no user interaction). There goal is to stick one CD in the PC and have the installer put everything needed on to the target computer. Setup Factory's silent mode is perfect, but there are some parameters that need to be configured, and the *.inf file is perfect for this. The problem is that they don't know what drive the CD-ROM is going to be on a given computer.
For example, they can do this:
setup.exe /S:d:\settings.inf
But this won't work if the CD-ROM drive is "E:".
What would be nice is if this worked:
setup.exe /S:settings.inf
and then the Setup Factory would look in the executable's folder for the *.inf file.
Any suggestions on how to get around this problem would be greatly appreciated.
Thanks.