C / C++ / MFC

31-Mar-09 12:56

Alright, I'm trying to incorporate TerminateProcess() into my progrms. I have two programs running at the same time, the first program opens the second via system("") and then continues to run a series of GetAsyncKeyState()checks that blocks input when certain keys are pressed. The second program is an annoying little game that runs through a random array of MessageBoxes. The issue I've hit is that when the second program finishes, the first program is still going--which means the BlockInput code is still ready to set off. What I'm trying to do is incorporate TerminateProcess() at the very end of the second program so that right before the second program finishes it closes the first, does anyone know how to do this?

Joe Woodbury31-Mar-09 13:04

31-Mar-09 13:04

Why not have the first program start the second using CreateProcess() and then wait on the process handle?

An alternative is to use a globally named event and have the first application wait on it (which is pretty much what my first suggestion is doing.)

Anyone who thinks he has a better idea of what's good for people than people do is a swine.
- P.J. O'Rourke

gamefreak229131-Mar-09 13:12

31-Mar-09 13:12

Because I'm attending a High School that offers no programming class at all and thus I have no prior instructed knowledge and have no idea how to do that. I've attempted via examples from searching around but I couldn't get them to work because I just don't have enough knowledge at this point.

Joe Woodbury31-Mar-09 13:38

31-Mar-09 13:38

DWORD ExecuteProcess(LPCTSTR pCommandLine, LPCTSTR pDirectory = NULL, DWORD millisecondsTimeout = INFINITE)
{
	// _alloca allocates the memory on the stack, so I don't need to worry about cleaning it up
	// You could use new and then delete the buffer later
	TCHAR* pCmdLine = (TCHAR*) _alloca((lstrlen(pCommandLine) + 1) * sizeof(TCHAR));
	lstrcpy(pCmdLine, pCommandLine);

	STARTUPINFO startupInfo;
	memset(&startupInfo, 0, sizeof(startupInfo));
	startupInfo.cb = sizeof(startupInfo);

	PROCESS_INFORMATION processInfo;
	memset(&processInfo, 0, sizeof(processInfo));

	DWORD rval;

	if (CreateProcess(NULL, pCmdLine, NULL, NULL, FALSE, CREATE_DEFAULT_ERROR_MODE, NULL, pDirectory, &startupInfo, &processInfo))
	{
		rval = WaitForSingleObject(processInfo.hProcess, millisecondsTimeout);
	}
	else
	{
		rval = GetLastError();
	}

	CloseHandle(processInfo.hProcess);
	CloseHandle(processInfo.hThread);

	return rval;
}

Anyone who thinks he has a better idea of what's good for people than people do is a swine.
- P.J. O'Rourke

gamefreak229131-Mar-09 20:14

31-Mar-09 20:14

okay, thanks for the tidbit of code but I still dont know where to insert it or how to tell it what to open

Iain Clarke, Warrior Programmer

Iain Clarke, Warrior Programmer31-Mar-09 22:50

31-Mar-09 22:50

You call this function in the first program instead of the system function.
It runs the second program (given in one of the parameters), waits for the second program to finish, then the function returns, so you can carry on doing whatever the first program should do.

Iain.

In the process of moving to Sweden for love (awwww).
If you're in Scandinavia and want an MVP on the payroll (or happy with a remote worker), give me a job!

Joe Woodbury1-Apr-09 5:28

1-Apr-09 5:28

You call ExecuteProcess with the same command line you would use at a command prompt. The directory is what the current directory should be set to.

For example, ExecuteProcess(_T("C:\\Windows\\System32\\Notepad.exe win.ini"), _T("C:\\Windows"));

This is very simple code, but it illustrates the basic principles. Go to MSDN and read up on CreateProcess() and WaitForSingleObject(). Read up on multi-threading and synchronization. Experiment. Step through the code. Until you fully understand this code, you will not be qualified to write any code.

Anyone who thinks he has a better idea of what's good for people than people do is a swine.
- P.J. O'Rourke

gamefreak229131-Mar-09 20:20

31-Mar-09 20:20

I never did get an answer to my initial question

Stuart Dootson31-Mar-09 20:29

Stuart Dootson

31-Mar-09 20:29

You can't do what you want. system doesn't give you back the identity of your process, so you have no way to (later) control it. You have to use some other mechanism to create the process, like (as Joe suggested) CreateProcess, which does give you the process identity (through the PID and a process handle in the case of CreateProcess).

Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p

Iain Clarke, Warrior Programmer

Iain Clarke, Warrior Programmer31-Mar-09 22:58

31-Mar-09 22:58

gamefreak2291 wrote:
I never did get an answer to my initial question

Your original question was posted when Europe had just gone to bed, India was debating getting to eat its breakfast Bhaji, and the Americas were having their after work beer. Or in your case, doing their homework.

1/ You don't pay us - we'll answer if / when we feel like.
2/ I'll give you credit for not putting "URGENTZ" in your subject line!

Anyway, Joe has given you a very good answer - if you need details, functions like CreateProcess have very long documentation to read.

I wish you success with your course,

Iain.

In the process of moving to Sweden for love (awwww).
If you're in Scandinavia and want an MVP on the payroll (or happy with a remote worker), give me a job!

tapi

Member 47646831-Mar-09 8:38

Member 476468

31-Mar-09 8:38

I am upgrading from an older version of Visual Studio to Visual Studio Express 9.0. In my code I have #include tapi.h. This causes an error. Does anyone know how to solve this?

Joe Woodbury31-Mar-09 9:47

31-Mar-09 9:47

It's in the platform SDK.

Anyone who thinks he has a better idea of what's good for people than people do is a swine.
- P.J. O'Rourke

Member 4764681-Apr-09 6:45

Member 476468

1-Apr-09 6:45

Windows SDK will not load with Visual Studio 2008. In the Platform SDK the dialer example uses tapi.h and does not comiple with VS2008. Do you have the dialer example from the Windows SDK?

Joe Woodbury1-Apr-09 8:38

1-Apr-09 8:38

Member 476468 wrote:
Windows SDK will not load with Visual Studio 2008

That makes no sense. Windows SDK doesn't "load" it simply is. Since the latest Windows SDK included the Visual Studio 2008 compiler, I'm pretty damn sure it works with Visual Studio 2008.

Did you download this:

http://www.microsoft.com/downloads/details.aspx?familyid=E6E1C3DF-A74F-4207-8586-711EBE331CDC&displaylang=en[^]

And search because IT'S THERE!

Anyone who thinks he has a better idea of what's good for people than people do is a swine.
- P.J. O'Rourke