abort

henri1.5524917514316418E12 asked a question.

November 12, 2008 at 11:22 AM

abort

In my basic msi project I use "abort" in the script. But whatever the setup does, it does not abort!. I also tried Do(EXIT).\

Under certain circumstances I want the script and setup to abort (for example, when the vista version doesn't have SP1 or when XP doesn't have the windows installer 3.1 installed).

How do I force the setup to abort??

Henri

InstallShield

Community Manager (Flexera Software)
18 years ago
To test system requirements in a Basic MSI project, you might consider an Install Condition (or launch condition), which you can define in the Product Properties view.

In general, to exit an installer from an InstallScript (or MSI DLL) action, your function should return ERROR_INSTALL_FAILURE. Another approach is to set a property (ACTION1FAILED, say) in your action, and then, follow your action with an Error custom action that's conditioned with ACTION1FAILED, and which displays a custom message.
Expand Post
henri1.5524917514316418E12
18 years ago
Thanks for the answer. (I do have one of your books ;-)) .

I cannot use the settings of the project because this message isn't for all users. Only for the users of winXP/2000 without the windows installer 3.1 and for Vista users without servicepack 1., BUT not for all of them. Only for those who are going to silently install Pervasive 10.1!!

I will try to see if your other suggestions are possible for me...

henri
Expand Post
henri1.5524917514316418E12
18 years ago
The problem is, that it is in the middle of the script. I don't understand where the commands Do(EXIT) or abort are for, if not for aborting the script. The script does not do anything with those commands(??)

Could anyone please explain how to do that?
Expand Post
Community Manager (Flexera Software)
18 years ago
I gather abort and Do(EXIT) are for InstallScript projects (and perhaps InstallScript MSI projects), where InstallScript custom actions in a Basic MSI project expect functions to return ERROR_SUCCESS on success and ERROR_INSTALL_FAILURE otherwise...
Expand Post
henri1.5524917514316418E12
18 years ago
ok. But how can I return an ERROR_INSTALL_FAILURE from the function then as you suggested. I tried to call a function in the middle of the script that returned such an error, but the setup just went on installing ;-)

How should such a function look like?
Expand Post
Community Manager (Flexera Software)
18 years ago
The help topic "Writing Entry-Point Functions" has an example; the general idea is:

export prototype ExitInstaller(HWND);

function ExitInstaller(hInstall)

begin

// decide you want to exit...

return ERROR_INSTALL_FAILURE;

end;
Expand Post
henri1.5524917514316418E12
18 years ago
allright. I will try to build in such a function, but i will do it before entering the very long script. Thanks. I will let you know how I will end up. But that will be next monday. Thank you very much....

henri
Expand Post

Related Questions

Nothing found

Are you sure you want to cancel the case creation?

Case closed successfully

Action performed successfully

Upload Attachment

Maximum file size allowed is 3 MB.

File type not supported.

Supported file types:

Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files (.csv) Speadsheets (.xlsx, .xls)

Are you sure you want to close this case

Get Hotline support

Products	Region	Phone Numbers
FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield	North America *	+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America)
	Europe *	+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe)
	Japan *	+81 3-4540-5335 (select option 2)
	Australia *	+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia)
Usage Intelligence (formerly Revulytics) Compliance Intelligence	Please use the Case Portal to submit your support ticket or reach out to your Revenera contact.

Revenera Assistant

Related Questions

Trending Articles

Please wait...

Case id: 00001065