| Author |
Message |
Kevin
Guest
|
 Posted:
Thu Dec 30, 2004 1:45 am Post subject:
How to know when DUAgent is done processing *.dup file |
|
|
My shell has a button click on it to initiate updates. When pressed,
the shell app starts DUAgent,waits a little while, then commits the EWF
and reboots. Right now I use a hardcode timer event for waiting, but
would rather key off of DUAgent being finished. Can I assume that when
the dup gets deleted, the Agent is finished, or is there something better?
kevin |
|
| Back to top |
|
 |
KM
Guest
|
| Posted:
Thu Dec 30, 2004 2:13 am Post subject:
Re: How to know when DUAgent is done processing *.dup file |
|
|
Kevin,
Why not issue the reboot from the DUP file itself? (as well as the ewfmgr -commit)
Then you don't need to have any related timers in your shell app.
KM
| Quote: | My shell has a button click on it to initiate updates. When pressed, the shell app starts DUAgent,waits a little while, then
commits the EWF and reboots. Right now I use a hardcode timer event for waiting, but would rather key off of DUAgent being
finished. Can I assume that when the dup gets deleted, the Agent is finished, or is there something better?
kevin |
|
|
| Back to top |
|
|
Kevin
Guest
|
| Posted:
Thu Dec 30, 2004 2:31 am Post subject:
Re: How to know when DUAgent is done processing *.dup file |
|
|
KM wrote:
| Quote: | Kevin,
Why not issue the reboot from the DUP file itself? (as well as the ewfmgr -commit)
Then you don't need to have any related timers in your shell app.
|
to issue the commit from DUA, I need to issue an EXUCUTE , which I have
never gotten to work. May be you see a problem
EXECUTE,,DAYES,,c:\windows\system32\ewfmgr.exe,,c:\windows\system32\ewfmgr.exe
c: -commit,DAYES,,,administrator,,JobPro,,admin,,,,,,
kevin
| Quote: |
KM
My shell has a button click on it to initiate updates. When pressed, the shell app starts DUAgent,waits a little while, then
commits the EWF and reboots. Right now I use a hardcode timer event for waiting, but would rather key off of DUAgent being
finished. Can I assume that when the dup gets deleted, the Agent is finished, or is there something better?
kevin
|
|
|
| Back to top |
|
|
KM
Guest
|
| Posted:
Thu Dec 30, 2004 3:11 am Post subject:
Re: How to know when DUAgent is done processing *.dup file |
|
|
Kevin,
| Quote: | KM wrote:
Kevin,
Why not issue the reboot from the DUP file itself? (as well as the ewfmgr -commit)
Then you don't need to have any related timers in your shell app.
to issue the commit from DUA, I need to issue an EXUCUTE , which I have never gotten to work. May be you see a problem
EXECUTE,,DAYES,,c:\windows\system32\ewfmgr.exe,,c:\windows\system32\ewfmgr.exe
c: -commit,DAYES,,,administrator,,JobPro,,admin,,,,,,
kevin
|
Did you see this thread:
http://groups-beta.google.com/group/microsoft.public.windowsxp.embedded/browse_frm/thread/2f7eb54ca20266d3#f9b5c813e62dc9a3 ?
| Quote: | My shell has a button click on it to initiate updates. When pressed, the shell app starts DUAgent,waits a little while, then
commits the EWF and reboots. Right now I use a hardcode timer event for waiting, but would rather key off of DUAgent being
finished. Can I assume that when the dup gets deleted, the Agent is finished, or is there something better?
kevin
|
Anyway, you can have an instruction at the end of the DUP file (e.g., deleling a file or setitng up a registry flag) that will
indicate that the script has been processed.
But launching EWFMGR and reboot from the script would be better. Or, if you fix EXECUTE/EXECUTEPROCESS command in your build, you
could launch another exe file that sets a named kernel object (event, mutex, etc.) to communicate to the shell app.
KM |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in