Good to know. I'll pass the information along to them. I know they have tried using some windows on top functions in WinBatch, but it looks like the Auto-it command _WinAPI_SetWindowPos which has more features.
Thank you for the help! On Tue, Aug 27, 2013 at 2:07 PM, Johan Arwidmark < [email protected]> wrote: > I haven’t tried WinBatch, but I have seen similar issues with other > frontends. Try to use an AutoIt script that’s sets the Z-order of windows > (sets the WinBatch window in focus).**** > > ** ** > > / Johan**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Ryan > *Sent:* den 27 augusti 2013 20:50 > *To:* [email protected] > *Subject:* [mssms] OSD custom script**** > > ** ** > > So, our OSD guys have tried opening a ticket with Microsoft and that > hasn't gotten them anywhere. **** > > ** ** > > We have an OSD interview screen that is written and compiled in WinBatch. > When the Winbatch script is kicked off in a task sequence in WinPE (so we > use MS dialogs to select the TS, and then this interview is kicked off), it > isn't shown until you hover the mouse over the blue bar on the task > sequence progress window. We are able to launch this manually right when > WinPE starts, before we select a Task Sequence, but right after the task > sequence is started this happens. **** > > ** ** > > So, has anyone else encountered this? I'm working on getting them away > from WinBatch (so please, no speeches), but I can't explain why this custom > dialog isn't displaying. Once it is displayed, everything runs just as it > should. Our problem is in showing it to the user. I haven't seen anything > like this before.**** > > ** ** > >
