The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
SOLVED ALREADY, I've done a small program in C++ that handles that for me.
The problem was not doing the program itself (which is super easy to do) the problem was getting an executable file that would work in Windows XP.
After a good tip from @Daniel_Pfeffer, I've learned how to configure newer versions of Visual Studio to link for Windows XP.
THANK YOU ALL!
I've seen "Clickoff" and "windows closer by Murgee", but the first one seems not to be capable to click on the message box and press enter afterwards, and the second one can't simply run on windows XP.
I've done a super simple small C++ program that would do that search for window handle, send return there. and that should be it.
The problem is that what is output from my Visual Studio is not compatible anymore with windows xp... (that's why I'm searching for a free application that could do that).
Each 2 or 3 years I get a request that implies opening 3 virtual machines and open a set of files... each time I try to open those files it takes between 30 minutes to several hours. And always appears some messageboxes that need to be confirmed for the process to continue. This leaves me in front of the computer waiting for them...
No, I don't know such an application. As far as I understand you tried to do it by yourslef. I also just tried it and for me it works fine (ok, I did it with c++ builder). The main difference to your approach seems to be you send a VK_RETURN while I'm doing SendMessage(xWnd, WM_CLOSE, 0, 0);
I hope it helps
It does not solve my Problem, but it answers my question
i would prefer to do a prorgram targeted approach... and wrap around the MessageBox* function so the messagebox would never appear at all, and all required would be a change from user32.dll to userMy.dll where userMy.dll i would forward all functions to user32.dll minus the MessageBox ones...
altough its also possible to do by injecting a dll on the process and detouring... and even possible with a global hooking for dialog creation (using the MessageBox template), dont know programs for that
as usually i do more targeted than generic approaches... but imo its very easy to do