Stop Windows XP Shutdown, perform action, then restart shutdown.

http://www.planet-source-code.com/vb/scripts/ShowCode.asp?txtCodeId=4228&lngWId=3

This code was made with Microsoft Visual C++ 6.0, and it detects a shutdown and asks for the user to confirm if he wants to shutdown or not. I did not check if it uses specific msvs libraries but you can tweak this code to perform what you want.

as for dcsbeemer's suggestion.

once you detect a shutdown you would do:

system("shutdown -a");

windows.h directory would need to be included.
---------------------------------------------------------------------------------------------------------
Also, you may want to put a 20 point pointer in the Programming C++ section if you find difficulties later on.
---------------------------------------------------------------------------------------------------------

If you need help modifying the code i could try to help

Good Luck!
-Sof

By The Way, Welcome To Experts Exchange!

dcsbeemer "try running "shutdown -a"" would involve starting a new process. in which case I would get a "process could not start because the workstation is shutting down" message.

sof_combat: AFAICT the link to http://www.planet-source-code.com/vb/scripts/ShowCode.asp?txtCodeId=4228&lngWId=3 does not contain any code to determine what type of shutdown was first initiated IE restart, reboot, poweroff etc. Maybe I should be using something other than WM_QUERYENDSESSION . I am sure that I am replying to the suggestions in the right way ??????

sof_combat I have added the 20 point pointer question. How do I assign the 20 points, does the winner of this question get them ??

Can't you perhaps create a batch file (*.bat) containing "shutdown -a" and have your application just query the batch file? (I'm not betting a lot on this working)

Again, I'm shooting in the dark here, but you never know when a guess can turn out to be a good guess.


I found this, might be of some help:

http://www.codeproject.com/system/AbortSystemShutdown.asp


and this:

http://www.codeproject.com/macro/winver_macros.asp



Good luck.

With regards to dcsbeemer's comment, AbortSystemShutdown only works on shutdowns started with InitiateSystemShutdown, which is different from ExitWindowsEx, and won't work after the shutdown has been started.

"AFAICT the link to http://www.planet-source-code.com/vb/scripts/ShowCode.asp?txtCodeId=4228&lngWId=3 does not contain any code to determine what type of shutdown was first initiated IE restart, reboot, poweroff etc. Maybe I should be using something other than WM_QUERYENDSESSION ."

As griffin36 also stated:

lParam
    This parameter can be one of the following values.
    Value       Meaning
    0       The system is shutting down or restarting (it is not possible to determine which event is occurring).
- Taken From http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shutdown/base/wm_queryendsession.asp

--------------------------------------------------------------------------------------------------------------------------------------
"I am sure that I am replying to the suggestions in the right way ??????"
Yes, there is no wrong response as long as you have a question or comment reguarding the issue.
--------------------------------------------------------------------------------------------------------------------------------------

"I have added the 20 point pointer question. How do I assign the 20 points, does the winner of this question get them ??"

In order for the person who answers this question to recieve points from your pointer: http://www.experts-exchange.com/Programming/Programming_Languages/Cplusplus_Builder/Q_21705930.html they would need to post a message there and you would need to accept it. I haven't made a pointer myself, so I dont know if you can ask for the pointer to  be deleted. If it can be deleted you would post a message in the Community Support area: http://www.experts-exchange.com/Community_Support/

Oops, forgot one thing, if no one posts in your pointer question, you can delete it yourself.

griffin36

That is such a pain in the butt not being able to determine if a system is restarting or shutting down!! Whilst you can't get it from the WM_QUERYENDSESSION or WindowProc() maybe there is some other way to tell if it is a restart or a shutdown????? I mean, if the system knows, maybe there is some way to query it? This part was kinda crucial cause I was thinking of making this a configurable releasable applcation. Now I know why none of the existing ones are able to offer this functionality :(.

What my external program does is start and stop Winlirc (A program that sends Infra Red signals through a Serial Port and out through an IR emitter) and then send messages to winlirc to turn off or adjust certain Home Theatre components. In between the starting and stopping of Winlirc the app changes Winlirc's comm port registry setting so that I can send the commands down a seperate serial port each time, and this allows me to access different components in the Home Theatre. I can do all the registry and sending of stuff to winlirc from within my program but I am still gonna need to start and stop Winlirc a few times.

And when you say:

// Put in your window procedure
case WM_QUERYENDSESSION:
PostMessage(hWnd, WM_PRESHUTDOWN, 0, 0);

Where do I put that in a New C++ Builder application that has a simple dialog form as a window ? In the OnCreate                                                              event for the form ??

BTW did you come to this question through the message pointer that I left in the C Builder section ??

OK, found this on the web:

VB:

Private Sub Form1_QueryUnload(Cancel As Integer, UnloadMode As Integer)

    If UnloadMode = vbAppWindows Then
        MsgBox "Windows is telling me to unload"
    End If

End Sub


If it works, you need to thank a person called 00100b



You can also try this one:

VB:

Private Sub Form_QueryUnload(Cancel As Integer, UnloadMode As Integer)
 
   If UnloadMode = vbAppWindows Then   'vbAppWindows is 2
      MsgBox "Windows is shutting down"
   End If
   
End Sub


Credits goes to jjStinger72




That's all I could get.

MusicBuddha-

The part that I mentioned putting in your window procedure is standard windows API stuff. It goes into the function
LRESULT CALLBACK WindowProc(HWND, UINT, WPARAM, LPARAM);
that you define. If your C++ builder project is not a windows API project, then you trap the message as you put it and execute the code there. If you need help trapping the message, give me an example of what a message trap normally looks like for C++ builder and I'll help you out.

Also, when I was investigating the problem just now, I made a sample program and had no problem starting a process from the WM_QUERYENDSESSION message. The ideal way for you to do this is to use the function system("yourprogram.exe parameters") because this will automatically not return until the process you start exits. That way you know Winlirc has done what it's supposed to before you exit.

When you trap WM_QUERYENDSESSION, be sure to return true.

I found this thread through the OS section, not through your pointer.

If you need anything else, let me know.

griffin36

"""The part that I mentioned putting in your window procedure is standard windows API stuff. It goes into the function
LRESULT CALLBACK WindowProc(HWND, UINT, WPARAM, LPARAM);
that you define. If your C++ builder project is not a windows API project, then you trap the message as you put it and execute the code there. If you need help trapping the message, give me an example of what a message trap normally looks like for C++ builder and I'll help you out."""

I have uploaded a bare, new, non API application created from C Builder 5 to http://www.harmonycentral.com.au/downloads/11.rar.

I am guessing that your code will probably go into WINAPI WinMain(HINSTANCE, HINSTANCE, LPSTR, int) inside the project1.cpp file.

dcsbeemer

Thanks for trying to help me out with this!!, but I can't use any VB Code :(. It needs to be in either C or C++.

Thanks again.

I know you stated that "the shutdown process needs to be stopped not just halted. "

Maybe we can eliminate the problem of having to detect if it is a reboot, shutdown etc... by detecting the shutdown and only delaying it until your cleanup is complete? or is that not possible?

sof_combat

"Maybe we can eliminate the problem of having to detect if it is a reboot, shutdown etc... by detecting the shutdown and only delaying it until your cleanup is complete? or is that not possible?"

Eventually you would initially get the "Window Not Responding" Dialog box with a "Close Now" button and eventually this would change to having the "close now" button and a "cancel" button at which time you would have stopped the restart/shutdown completely. It's a good idea though, but I can't think of a tidy way of doing it without running into that dialog box.

Ah, sorry about that MusicBuddha

I don't know programming, but even I know VB & C++ isn't the same thing.

I'll keep looking though.

Hello MusicBuddha,,,

Maybe it will help you out if you post a new question to the cummunity support so they can move this question to the programming Topic Area so most programmers can see your question, or you can open a new question with 20 points in the programming T.A directed with this one 2.

Good Luck
Moh10ly

MusicBuddha-

The part that I mentioned actually doesn't go into WinMain, the place it should go is not there, things seem to be handled differently in your application.

From what I can gather, your application uses something called Visual Component Library (VCL) that is usually used with Delphi, a completely different programming language. In fact, I couldn't find any information at all on using VCL with C++, however, I did find a helpful article using Delphi that hopefully should help: http://www.howtodothings.com/viewarticle.aspx?article=424

From the article, it appears you need a private method HookProc in your TForm (the name HookProc isn't important, you can change it if necessary). I've posted below my best translation of the Delphi into C++.

bool YourMainForm::HookProc(TMessage Message) { // Change YourMainForm to the actual name
if (Message.Msg == WM_QueryEndSession) { // If WM_QueryEndSession doesn't work try WM_QUERYENDSESSION
/*
Do what you want with winlirc here by using system() to run it how you want. It will still run because Windows hasn't begun shutting down.
*/
}
}

void YourMainForm::FormCreate(TObject Sender) {
  Application.HookMainWindow(HookProc);
}

Be sure to place the definition of HookProc into the private section of your TForm, and I guess FormCreate goes into the public section.

I am not a Delphi developer, nor a VCL developer, but I've done my best to adapt the article's suggestions.

By the way, how long does it take to run your winlirc commands? It sounds like it takes several seconds, by your description.

> // Put in your window procedure
> case WM_QUERYENDSESSION:
> PostMessage(hWnd, WM_PRESHUTDOWN, 0, 0);
>
> Where do I put that in a New C++ Builder application that has a simple dialog form as a window ?

You have two options;

1. override WndProd in your mainform. In the .h:

class TMainForm : public TForm
{
    ...
  public:
    typedef TForm inherited;
    virtual void __fastcall WndProc(TMessage &Msg);

in your cpp:

void __fastcall TMainForm::WndProc(TMessage &Msg)
{
    switch ( Msg.Msg )
    {
        case WM_QUERYENDSESSION:
            ...
            return;

        // you can also trap other messages here:
        case WM_ENDSESSION:
            ...
            return;// or break;

        default:
            break;
    }
    inherited::WndProc( Msg);
}

2. use a message map;

in the .h:

protected:
  BEGIN_MESSAGE_MAP
     VCL_MESSAGE_HANDLER(WM_QUERYENDSESSION, TMessage, OnQueryEndSession)
  END_MESSAGE_MAP(TForm)
  void __fastcall OnQueryEndSession(TMessage & Msg);

in the .cpp:

void __fastcall TForm1::OnQueryEndSession(TMessage &Msg)
{
    ....
 
    TForm::Dispatch(&Msg);
}

It looks like cwwkie is more familiar with C++ VLC than I am. Try his suggestions.

Also, I noticed that my HookProc function doesn't return a value (but should). Have it return true inside the if statement and return false outside.

> From the article, it appears you need a private method HookProc in your TForm (the name HookProc isn't
> important, you can change it if necessary). I've posted below my best translation of the Delphi into C++.

I do not often use Delphi, but afaik it is much simpler in delphi:

  ....
private
  procedure WMQueryEndSession (var Msg : TWMQueryEndSession); message WM_QueryEndSession;
end;

Implementation

procedure TForm1.WMQueryEndSession (var Msg : TWMQueryEndSession);
begin
  if MessageDlg('Close Windows now?',
                            mtConfirmation,
                            [mbYes,mbNo], 0) = mrNo then
      Msg.Result := 0
   else
      Msg.Result := 1;
end;

> It looks like cwwkie is more familiar with C++ VLC than I am. Try his suggestions.
I came here through the pointer in the c++builder ta, but on the other hand, I have never done anything with the QueryEndSession message before. But together we can help MusicBuddha...

cwwkie

Where in option 1 and 2 do I perform my own functions ?.

To Everybody.

It looks to me like I am gonna have to split the points between griffin36 and cwwkie with 250 points each, and once I accept that as the solution I will raise the points on the pointer message that sof_combat suggested to 250 (which he can claim by replying to that message after I accept the solution in here)  because not only was his suggestion of a pointer message something that I would never have thought of, but it turns out that without it cwwkie may never have given his contribution to the solution.

Is everybody happy with that splitup of the points?

I would also like to thank everybody for their contributions and can only say what an excellent place this is!

cwwkie,

I forgot to ask in my last post

You wouldn't happen to know of a way to determine if a system is shutting down or restarting would you?

SOF contributed this:

  0      The system is shutting down or restarting (it is not possible to determine which event is occurring).
- Taken From http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shutdown/base/wm_queryendsession.asp

I'm happy with that decision, MusicBuddha. Did we solve your problem, though? I'm guessing we did (because you're giving out the points) but I just want to be sure.

Good luck with your program!

griffin36,

Yeah the problem is solved although I haven't had time to actually check that the code works, but what cwwkie came up with looks pretty close to some examples I found in the help files, I just didn't know how to implement it in the project.

I was gonna hold off on accepting the solution until cwwkie has answered my last question which was:

Where abouts in his Exmaple 1) and 2) do I put my own code to do the processing I need to do. I will probably use Example 1) because it looks the most familiar to me.

Do I put my code in the snippet below before the return? And should I return 0; to stop the shutdown process?

case WM_QUERYENDSESSION:
            ...
            return;

griffin36:

Maybe you know the answer anyway ???

Also is it possible to get you two guys email addresses (griffin36 and cwwkie)  in case I stumble over an unforseen problem after I set this one as solved ?? Or can you contact a member directly through the experts system system ??  It's very likely that I won't get time to try the code out until next week sometime and I'm sure that everybody would be happy to see this one solved and points collected :D

For cwwkie's example one, you need to put your code right after

case WM_QUERYENDSESSION:

and before the return. The function there has return type void so you can't return anything but you can do everything you want without stopping the machine restart.

I'd be happy to give you my email, but I'd rather not post it on a popular public forum. I have a contact page on my site (http://www.enkod.com/contact.php) with an email form, and if you email me there I'll reply immediately so we have each other's email addresses. If this doesn't sound like something you want to do, I'll post my email address here; I was just hoping to avoid that.

griffin36

"For cwwkie's example one, you need to put your code right after
case WM_QUERYENDSESSION:
and before the return. The function there has return type void so you can't return anything but you can do everything you want without stopping the machine restart."

Can you see a way to change the code so that I can stop the shutdown, my process may take longer than 30 seconds which will initiate the "window not responding" dialog box .. I think ?

The only way I can think of for you to stop the shutdown like a return would in Windows API is if maybe TMessage has a method that lets you set what the return value should be. I really have no idea if this is the case, I'm just guessing.

Maybe cwwkie can help on this one.

griffin36

*****The only way I can think of for you to stop the shutdown like a return would in Windows API is if maybe TMessage has a method that lets you set what the return value should be. I really have no idea if this is the case, I'm just guessing.*****

No problem, I'll wait for cwwkie and then hopefully I can close this off and send all the points to everybody.

> Where in option 1 and 2 do I perform my own functions ?.
Where I have put the dots, for example

void __fastcall TForm1::OnQueryEndSession(TMessage &Msg)
{
    Your code goes here
    If you still want to perform default processing, call dispatch:
      TForm::Dispatch(&Msg);
}

> You wouldn't happen to know of a way to determine if a system is shutting down or restarting would you?
The only thing I could think of is hooking functions like ExitWindowsEx.

> I will raise the points on the pointer message that sof_combat suggested to 250 (which he can
> claim by replying to that message after I accept the solution in here)
I understand why you want to do that, but it is probably not allowed. The maximum points of a question is 500 points, you would give away 750 points this way.

cwwkie,

Can you show me me how to stop the shutdown after catching the WM_QUERYENDSESSION message?

""The only thing I could think of is hooking functions like ExitWindowsEx.""

Can I open up a seperate 500 point question so that you can give me detailed information (including code examples) on how to perform that ?? AFAICT it is a completely different question from the one that I initially asked in here.

""I understand why you want to do that, but it is probably not allowed. The maximum points of a question is 500 points, you would give away 750 points this way.""

Technically they are two seperate questions, however if it is not allowed, I feel obligated to split the points 3 ways (if possible) because sof_combat contributed more than just the pointer message, there was also the stuff from the microsoft library (which was useful) and we've yet to hear his position on this.

How about 200 points each for cwwkie and griffin36 and 100 points for sof_combat? How does everybody feel about that??

I really want to be fair about this cause you have all helped so much and I really wouldn't have gotten the complete solution until you showed up from the pointer message.

cwwkie,

The line "typedef TForm1 inherited;" in the .h file raises an exception class EAccessViolation blah blah blah at runtime.

I am about to try option 2 to see if it works any better.

cwwkie,

I just commented out the line above that was causing the problem and both option 1) and 2) trap the message properly. However, one of the things that my program needs to do is to start another program, and since the shutodwn has not been stopped, it errors with "The application failed to initialize because the window station is shutting down".

I need the code to be able to trap the WM_QUERYENDSESSION but also be able to cancel the shutdown! I will restart it after I am finished my processing.

This is also why I would like to find out if it was a shutdown or a restart before I cancel it. This way when I restart it I will know which one to use. However we can resolve that issue in another question, since the scope of this one does not really cover it.

I think the splitup of the points is fair, but I need to get the above issues cleared up before I can accept this solution.

Hopefully you can get back to me on this soon cwwkie.

Hi, I am back.

>> I need the code to be able to trap the WM_QUERYENDSESSION but also be able to cancel the shutdown!

I think setting result to 1 will do that;
void __fastcall TForm1::OnQueryEndSession(TMessage &Msg)
{
     Msg.Result=0;
}

>> However, one of the things that my program needs to do is to start another program, and since the shutodwn has not been stopped, it errors with "The application failed to initialize because the window station is shutting down".

I think you have to wait until windows has processed the result of the OnQueryEndSession. You can post a message to yourself, when it gets executed, you should be able to start another program. I will look for an example and post it here.

cwwkie,

Thanks that is excellent, works perfectly. I am getting the following wanring when I compile though. I am happy to close this off, but it would be nice to get rid of that warning message :D

[C++ Warning] Unit1.h(18): W8027 Functions containing switch are not expanded inline

and it points to the BEGIN_MESSAGE_MAP

I have also setup the question of how to tell if windows is shutting down or restarting.

http://www.experts-exchange.com/Operating_Systems/WinXP/Q_21709076.html

As Far As I Know You Can Give more than 500 points to related questions, but not the same question. You cannot give out points for the sake of giving points either. You must have a reason. (This is from EE rules) So I feel that for what I have done 100 points is MORE than enough points.

I am sorry that I wasn't able to help you further than I did, luckily griffin36 & cwwkie came in.

cwwkie,

My original post on the restart or reboot question has been moved to http://www.experts-exchange.com/Programming/Programming_Languages/Cplusplus/Q_21709076.html


sof_combat,

If it is allowed, I believe that I should raise the points in the pointer message to at LEAST 200 and split the 500 points between griffin36 200 & cwwkie 300. I think cwwkie deserves a little more because whilst I am sure that griffin36 and I would have got there is the end, cwwkie really produced the complete final solution. I hope you are ok with that griffin36.

Apart from your initial contribution from the MS website on the reboot shutdown stuff, cwwkie may never have arrived here had it not been for your suggestion about the pointer message, and since he supplied the final solution it might never have arrived had it not been for your pointer message. So in reality it could be argued that your pointer message actually (although indirectly)  provided the solution.

Maybe we could have an Administrator rule on what is and what is not allowed with regard to adding points to the pointer message in this situation ??.

Sure, when its always best to check with the authorities.

griffin36, cwwkie and sof_combat,

I've spoken to the management and whilst they haven't completely ruled out upping the points on the pointer question, it didn't sound like they were too keen on it either.

So okay then ...... this is how I have decided to divvy up the points. sof_combat = 100; griffin36 = 150; cwwkie = 250; I have given this a lot of thought and I don't think I can do it any fairer without splitting hairs.

So as soon as cwwkie can get back to me about weather he can get rid of that warning message or not (with code if the answer is yes :D) I will accept the solution as stated above.

I sincerely would like to again thank everybody invloved in solving this problem for me, you have all been great, and for me this really is a superb place!

Best Regards,

MusicBuddha

cwwkie,

I have gotten rid of the wanring message, so thankyou all very much again and I will consider this question answered :D

> but it would be nice to get rid of that warning message :D

go to compiler options (Project->Options[Shit+Ctrl+F11]->Compiler tab), click Warnings button, in the warnings list find "W8027 Functions containing..." and uncheck it.

Or put in the sourcecode the following line before the BEGIN_MESSAGE_MAP
#pragma warn -8027
You can enable the warning again after the END_MESSAGE_MAP using
#pragma warn +8027

oops, did not update before posting