Re: Restart action required after installing to a non-boot volume
Re: Restart action required after installing to a non-boot volume
- Subject: Re: Restart action required after installing to a non-boot volume
- From: Qi Liu <email@hidden>
- Date: Mon, 22 Feb 2010 16:28:13 +0800
Hi Eli,
I'm just back from my holidays.
Yes, my installer has two things exactly as your thought. I have tried to split them into two packages, the driver one can be only installed in root volume and requiring reboot.
As your suggestion, I create a metapackage to group the two packages, in order to present one installer experience. But I find the package can be only installed in root volume...
I'm not sure if I missed something.
Thanks,
Qi
2010/2/10 Eli Bach
<email@hidden>
On Feb 9, 2010, at 11:52 PM, Qi Liu wrote:
> I found an issue that even I select "Required Restart" in my package maker
> project, if I install the package to a non-boot volume, after the
> installation finishes, the supposed "Restart" button turns out to be a
> "Close" button, and won't restart the OS.
> I would like to know if there is a workaround to solve the problem. And I
> don't want to select the option "Root Volume Only" since my app doesn't have
> to be installed to a root volume.
If it's something along the lines of a kernel extension [or something else that must be installed on the boot volume], and an app that can be installed anywhere, maybe try splitting the two things into separate packages and mark the kernel extension package as requiring reboot. That MIGHT work [as I have not tried it].
Eli
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden