Re: [ActiveDir] Using InstallShield in a Startup Script

[Stefano Tufillaro]

Warning! a setup by installShield or alike 'wrapper' installation package has a internal logic. Normally it appears as a file driver but it's not sure thal ALL the logic is trasparent or simple. The rule to indicate the full path is mandatory but not sufficient. In some case you'd need of a fullpath by a redirect drive (not alike pipe Es: \\mycomp\share) If the operations that the file driver has broke the rules you must use the kit (SDK) of installshield to view the real operation. If you use to create a temp directory in the runtime you must be sure that what you make to have (the entire process with ALL the final results and side effects (log on file, and/or on registry, modify file, system exceptions  etc.) live in a coeherent environment. It's not full right think that if you have a right and/or an access in the first process  automatically inherit the correct right process and access in the child operations. If an operation is a parallel process with specifically threads or like situations you loss this constraint. The rules (or the know how) are sured if you use the kit (SDK). In other case you will have never a complete result Good Luke ----- Original Message ----- From: Celone, Mike To: '[EMAIL PROTECTED]' Sent: Wednesday, November 19, 2003 11:41 PM Subject: RE: [ActiveDir] Using InstallShield in a Startup Script I tried this and it does the same thing.  I have a script that lists all processes running on the machine and I can see setup.exe in there but it never does anything.  I'm starting to think you can't use an InstallShield installer until you are logged in.  I can see it copy the files down and the install starts but that's it.  Also InstallShield never creates the log file either.  Here's an example of the batch file: md c:\temp md c:\temp\V5R2 copy \\server\iseries\*.* c:\temp\v5r2 c:\temp\v5r2\setup -s -f1z:\iseriesv5r2.iss -f2c:\v5r2.log -SMS   Mike From: Douglas M. Long [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2003 4:41 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] Using InstallShield in a Startup Script If you are able to get to the share, but the script is not executing the .exe, try copying the file from the share to the local machine (in your script) and then running setup.exe. Just make sure to use full paths in all instances -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Celone, Mike Sent: Wednesday, November 19, 2003 4:12 PM To: '[EMAIL PROTECTED]' Subject: [ActiveDir] Using InstallShield in a Startup Script Has anyone ever called an InstallShield setup from a startup script before?  I have a simple batch file that calls an InstallShield setup.exe file from a startup script but it never seems to run.  The setup.exe file is on a server with a Null Share.  I've verified that the script is able to reach the file but the setup does not seem to run.  The machine I'm testing it on says "Running startup scripts" when it boots up for about 15 minutes but the setup program is never run.  If I login to the machine and run the file it works without any problems.    Mike Celone Systems Specialist Radio Frequency Systems v 203-630-3311 x1031 f 203-634-2027 m 203-537-2406