Location of running processes

[mattg2k4]

I'm having some problems with the Folding at Home client, there are more cores running than should be, and I want to find out where they are loaded from. That is, I want to know what directory FAHCore_79.exe was loaded from, because it's not supposed to be running.

I know that with some program that I think came with Visual Studio could do this, but I don't have visual studio up here. Is there any way I can find this out?

[WhatsThisBoxFor?]

I don't know how to find out where the location of the processes are but...
It sounds like you have more than one instance of folding running, is your P4 hyperthreaded (I don't think it is, but I can't remember exactly when they started doing HT)? If it is running one instance on each 'virtual processor' is what should be happening. Overwise look in your startup folder (in the start menu), on the startup tab of msconfig, and in services.msc, also do you have EMIII running at startup? EM can be set up to run folding on startup, and if you have folding set up as a service then doing that could cause two instances to run.

[mattg2k4]

Yeah it's an HT processor and I have two processes of FAH running, but for reasons I'm currently investigating, I see three cores running in the processes menu of the Task Manager. Because I've only installed two clients with Machine ID's 1 and 2 respectively, I think the existence of a third running core could be what's been causing some reliability issues of late, and I want to find out why it's starting and that involves finding out which directory it was loaded from.

I have EM3 starting up the clients, the clients run normally with just the -local command, they're not running as services.

Even if I can fix the problem with the FAH client another way, I'm still interested if there's some way I can figue out where programs are running from.

Edit: I checked services.msc like you suggested and it turns out that there was a client set to start in there, although I really don't remember installing it Anyway, that problem is fixed, but I'm still interested in finding out where processes were loaded from.