From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Monday, January 15, 2007 11:52 PM
Quinton Tormanen wrote: I've just switched from our own custom action (calling a DLL function) to using DIFxApp with WiX. I've found that I have to leave the DriverPlugAndPlayPrompt set to "yes", or the install will fail on Vista if my USB device isn't plugged in when the install runs. However, almost as bad, I've found that on Vista, with this prompt enabled, the prompt shows up entirely hidden behind the Windows Installer UI, which leaves the user with only the Cancel button enabled and a hidden prompt. This is definitely going to mess up a lot of our customers. I realize that this question is on the fine line between DIFx and WiX, but I'm hoping that there is a workaround in WiX, or perhaps someone with experience with using DIFx in WiX that can help with this issue: How do I make the DriverPlugAndPlayPrompt either display in FRONT of my UI, or not at all on Windows Vista? That's usually caused by using the wrong parent window. There's nothing WiX can do about it but it might be a bug in DifxApp they can fix by getting the right parent window. I have a problem in the same general area, and this sounds like a clue to it. For historical reasons I'm doing driver installation from deferred custom actions (written in C) using the SetupAPI on Windows 2000 and 2003. I have a similar problem in that prompts from SetupAPI pop up behind the installer UI, sometimes entirely hidden by it. Several SetupAPI functions have a 'handle' parameter described as Optional pointer to the window handle to the window that owns any dialog boxes that are generated during installation, such as for disk prompting or file copying. If Owner is not specified, these dialog boxes become top-level windows. At the moment I'm setting these SetupAPI parameters to NULL. I'm guessing from Bob's message that I can solve this problem by passing a handle to the Installer UI window instead of NULL. Does this sound right? I know almost nothing about Windows UI programming, so my main question is: how should a C deferred custom action get hold of a handle to the installer UI window for passing to these SetupAPI routines? Thanks for any suggestions, or pointers in the right direction if I've got this all wrong. -- View this message in context: http://www.nabble.com/RE%3A--WiX-users--DIFx-prompt-shows-up-behind-UI-tf3026760.html#a8408778 Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
