Search found 5 matches

by r0x0t
Mon Mar 16, 2020 7:00 am
Forum: V7.5.1 Public Release Windows/Linux/MacOS X [deprecated]
Topic: Windows 10 compatibility bug
Replies: 7
Views: 1321

Re: Windows 10 compatibility bug

06:59:37:************************* Folding@home Client ************************* 06:59:37: Website: https://foldingathome.org/ 06:59:37: Copyright: (c) 2009-2018 foldingathome.org 06:59:37: Author: Joseph Coffland <joseph@cauldrondevelopment.com> 06:59:37: Args: 06:59:37: Config: <none> 06:59:37:***...
by r0x0t
Mon Mar 16, 2020 6:58 am
Forum: V7.5.1 Public Release Windows/Linux/MacOS X [deprecated]
Topic: Windows 10 compatibility bug
Replies: 7
Views: 1321

Re: Windows 10 compatibility bug

You are correct. From the default install, FAHCore_nn does not seem to run on a Windows 10 platform system. I just see FAHClient which in turn seems to be using CPU.

Not sure if we need this behavior for default installations. Let me know what I can do on my end to resolve this.
by r0x0t
Mon Mar 16, 2020 6:38 am
Forum: V7.5.1 Public Release Windows/Linux/MacOS X [deprecated]
Topic: Windows 10 compatibility bug
Replies: 7
Views: 1321

Re: Windows 10 compatibility bug

Unfortunately, Windows is a graphical friendly platform and this forum does not allow to embed images in the posts otherwise I would have showed you the analysis from Process Hacker as well as Task Manager. I navigated specifically to the FAHClient.exe process running on the system to monitor the re...
by r0x0t
Mon Mar 16, 2020 6:19 am
Forum: V7.5.1 Public Release Windows/Linux/MacOS X [deprecated]
Topic: Windows 10 compatibility bug
Replies: 7
Views: 1321

Re: Windows 10 compatibility bug

PS: NVIDIA drivers are installed on the system for games. Some troubleshooting reveals I/O rate is super high while using the CPU cycles.
by r0x0t
Mon Mar 16, 2020 6:02 am
Forum: V7.5.1 Public Release Windows/Linux/MacOS X [deprecated]
Topic: Windows 10 compatibility bug
Replies: 7
Views: 1321

Windows 10 compatibility bug

I just ran the tool on Windows 10 platform and couldn't see the client using any GPU cycles. On contrary, it seems to be using CPU. Expected behavior?