Failed to Install and Startup
Moderators: Site Moderators, FAHC Science Team
Re: Failed to Install and Startup
I will uninstall completely and reinstall without administrator level.
-
- Site Admin
- Posts: 8002
- Joined: Tue Apr 21, 2009 4:41 pm
- Hardware configuration: Mac Studio M1 Max 32 GB smp6
Mac Hack i7-7700K 48 GB smp4 - Location: W. MA
Re: Failed to Install and Startup
Not Bruce, but yes that is what is recommended. The folding client should be installed using the Windows account that will be used to fold under . The installer will prompt for admin privileges as needed. Otherwise the permissions and paths are going to be all messed up.
Re: Failed to Install and Startup
I have uninstalled, and reinstalled. It does not open with Chrome, yes with MS Edge and Firefox. Will see what happens.
Thanks
Thanks
Re: Failed to Install and Startup
Yes. Specifically, the Windows FAH install works painlessly when the userid doing the installation is the same as the one who will be logged on running FAH. After all, FAH is designed to run @home.
If you plan to run on a remote server, use the Linux install.
If you plan to run on MacOS, unfortunately there is no plan to support the COVAID19 research on the Mac.
Edit: Correction. MacOS can run the COVAID CPU projects which have been released since I originally posted this message. At the time, only GPU projects were available.
If you plan to run on a remote server, use the Linux install.
If you plan to run on MacOS, unfortunately there is no plan to support the COVAID19 research on the Mac.
Edit: Correction. MacOS can run the COVAID CPU projects which have been released since I originally posted this message. At the time, only GPU projects were available.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
-
- Site Admin
- Posts: 8002
- Joined: Tue Apr 21, 2009 4:41 pm
- Hardware configuration: Mac Studio M1 Max 32 GB smp6
Mac Hack i7-7700K 48 GB smp4 - Location: W. MA
Re: Failed to Install and Startup
The problem with Chrome is a known issue, recent updates by Google to Chrome introduced an incompatibility that causes the web app to not connect to the FAHClient process running in the background.