- fahclient.exe default file path: C:\Program Files (x86)\FAHClient
- This program controls the CPU calculations (folds proteins)
- FAHCoreWrapper.exe default file path: C:\Program Files (x86)\FAHClient
- This program allows GPU to be used for calculations too.
- FAHViewer.exe default file path: C:\Program Files (x86)\FAHClient
- This app visualises the protein folding itself you are undertaking, and renders a map showing the worldwide distribution of donors
- FAHControl.exe default file path: C:\Program Files (x86)\FAHClient
- Instead of using the web control to configure your client's behaviur, login etc, (http://folding.stanford.edu/client/) you can use a local program instead.
If your Nokia Lumia phone, including Nokia 830 and 930 have stopped working properly after a windows 10 mobile update, you will need the Windows Device recover tool from Microsoft to roll back the operating windows 10 mobile operating system back to windows 8.1.
In Australia, on the Nokia 930 the Telstra branded update can break, resulting in microsoft edge not being installed, and you being unable to sign into your microsoft account login.
The store will also be broken, because without being able to log in, you cannot install edge again, but on a cruel catch 22, you cannot log in witout installing the correct app... which require a successful Microsoft account login.
Anyhow, the official Microsoft download link to the Microsoft device recovery tool for Nokia Lumia phones can be found below:
The link is just to a package installer, of 2.3Mb. An obnoxious and convoluted download process may begin after installation of the initial installer from Microsoft.
annnnnd.. an error 0x00000067 (thor2NotResponding) is thrown on my Nokia Lumia 930
eventually, after some trial and error, and at the prompt, hitting power + volume down till the phone vibrated the following screen pops up, offering a download of a suitable windows mobile OS version from the server.
Upon clicking "install software, Microsoft asks you why you are ditching windows 10- performance issues, apps nor working as expected etc etc.. I basically clicked EVERYTHING! and moved on!
The file size for the OS flash of windows 10 / 8.1 mobile is a whopping 1.78BG in size. Quite a chew on my data allocation for the month!
After about half an hour chewing my expensive mobile data, the download finally finished.
The only nice thing about this is that it stores away these installer files on your C: root drive for later use if you need them, or if the download fails halfway though, saving you time, instead of restarting the whole process again.
When complete,the program switches over to trying to get the windows Nokia Lumia phone to switch to flashing mode so the new OS or reinstall will be accepted.
After spinning away for aeons, my first attempt to reinstall windows mobile on my nokia lumia ended in utter failure, and the program crashed badly not long afterwards, requiring the task manager to put it out of its misery.
On research on the net, a lot of people have problems with a nokia lumia phone switching into flashing mode and it just hangs. In my case, I think the problem was that the phone was running, with its OS active at the time, as indicated by its start screen covering the screen. I think it needs to be in an early boot mode to switch successfully.
On a second attempt however, I rebooted the phone with the power+downvolume hold technique, THEN, quickly plugged in the phone immediately when when the screen showed the NOKIA logo, on a black background.
This met with significantly more success, and the windows mobile flashing operation on the Nokia Lumia phone began working.
On the phone side, the Nokia lumia 930 phone screen turned a disturbing BLOOD red colour, with a progress bar that mirrored what was going on on the computer.
As the progress bar came to the end, the Nokia Lumia Microsoft windows device recovery tool displayed a successful flash had been executed.!Read more link text
For those that don't know folding at home is a distributed processing computer network which provides computing power for health research projects in the field of protein science, and is run by Stanford university.
Applications for this science range from cancer research, to alzheimers, and debilitating, terminal genetic diseases such as Motor Neurone Disease (MND) and even mad cow disease.
People all over the world for the last 15 years or so have donated their spare computing power, available on home computers, corporate servers and even gaming devices in some cases.
These generous donations from the general public amount to an incredible amount of money in terms of hardware costs, internet bandwidth, and power consumption costs, plus time and effort of donors to configure and maintain their computers to run the folding at home software in a stable fashion, and make charitable contributions.
Folding at home currently supports both CPU and GPU (graphics card- AMD and NVIDIA) processing of scientific research.
Shortly after installing folding at home, and beginning to compete work units, I noticed a problem with the GPU- the required core file (the application that runs the GPU as a processing unit for folding at home) FahCore_21.exe and FahCore_a4.exe were having an issue shortly after downloading from the Stanford university website. : access is denied.
How to fix??
FIrstly, I looked at the firewall issues that could be stopping the FahClient program communicating with the outside world.
The following list of applications need to be enabled as authorized in the windows 10 firewall to ensure folding at home can run properly: fahclient.exe, FAHCoreWrapper.exe, FAHViewer.exe, FAHControl.exe, Core_21.exe
Its also a good idea to pin these apps to the start menu for easy access too- it doesnt happen by default when undertaking the standard install!
The core file may be different, depending on the age of your system and GPU / graphics card- (mine is an ancient dinosaur by comparison to modern gaming beast rigs) core i5 CPU + NVIDIA fermi GT 430 graphics GPU.
Some of these folding at home client and core files can be a little tricky to find- their default direcotry locations are hidden in the rather hotchpotch file structure of windows 10 or windows 7
The main client and other key applications default file path is fairly easy to find on windows 10:
The core files for the GPU processor are in a couple different possible locations:
Typically only under windows 7 - program data
on WINDOWS 10 - the appdata roaming folder under your user account
The last possible problem stopping the folding at home client from running properly is administrative privileges. Though your account might have administrative privileges, you may need to specify to use them when the F@H client is started- this can be set via the peoperties of the application file.
You will need to navigate to the file's location in the file system and right click on it to change the default running preferences.
Check the box "run this program as administrator" and hit apply.
After all this is done, the access denied error on folding at home should be fixed.
Read more link text