hi all

This is my first post on this site, so sorry if this is the wrong place.
I am currently trying to create a .iss file for the deployment of Sage Accounts 2011 using the following cmd
C:\>c:\SageInstall\install\setup.exe -r -f1e:\responsefile.iss

I have copied the install files from the cd to the following folder c:\SageInstall and creating the .iss file to the e: drive (usb)

When i run the above cmd the Sage install takes place however no .iss file is created. Not sure what i'm doing wrong.

All help would be greatfull

Thanks
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
try this command line.
C:\>c:\SageInstall\install\setup.exe /r /f1"e:\responsefile.iss"

also take a look in windows\system32
I think that is where it will drop a setup.iss by default if no switches are used.
Answered 08/30/2011 by: Foleymon
Orange Senior Belt

Please log in to comment
0
Hi Thank you for your reply, i have tried replacing the - with \ however i have the same response, not sure if this would make a differnce i am using Windows 7 32bit OS
Answered 08/30/2011 by: sumit601
Senior Yellow Belt

Please log in to comment
0
I hope you have used "/" not this "\".

Try following

C:\SageInstall\install:\>setup.exe /r /f1"e:\responsefile.iss"

It is a installshield package?

Following link will be helpful :
Link1
Look for article section of appdeploy.com - Installshield Setup Parameters
Answered 08/30/2011 by: rock_star
Black Belt

Please log in to comment
0
Morning all, i have also tried the above with no luck, the reason i am looking at InstallSheild is i found the following info in this web page ;

http://www.appdeploy.com/packages/detail.asp?id=2141

sorry to be a pain but really would help if i could get the .iss file
Answered 08/31/2011 by: sumit601
Senior Yellow Belt

Please log in to comment
0
Every Sage product I've dealt with so far extracts and executes one or MSIs. Use that/those. True, they are a vision to behold - some an object lesson in how NOT to package - but you'll be able to custimise with transform, apply whatever arguments you want and so on.
Answered 08/31/2011 by: VBScab
Red Belt

Please log in to comment
0
Takes for the reply VBScab, but i do not understand ur comment, please can you expand? Thanks
Answered 08/31/2011 by: sumit601
Senior Yellow Belt

Please log in to comment
0
i have also checked the windows\system32 folder and no file has been created! havnt got a clue where we're going wrong with this one
Answered 08/31/2011 by: sumit601
Senior Yellow Belt

Please log in to comment
0
On your packaging VM:

- clear out your %TEMP% and %SystemRoot%\TEMP folders
- start Setup.EXE with no arguments.
- when you see the first screen - normally a 'Welcome' screen - look for an MSI in %TEMP%, %SystemRoot%\TEMP or a new folder beneath %AppData%
- use the resulting MSI (copied - and renamed something sensible if necessary)
Answered 08/31/2011 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity