Page 1 of 3
Installation to wrong user account
Posted: Thu Jan 09, 2020 11:20 pm
by lumpy
When I installed FAH, from my Windows 10 user account, it said it installed fine, it started up after installation and completed a couple units. It didn't create a shortcut on my desktop, but I thought maybe I had selected that as an option. When I restarted the computer the next day, FAH did not start, and when I looked through the start menu it wasn't there. I logged into the administrator account and there was the desktop icon, and FAH started automatically. I deinstalled it, logged out of the administrator account, logged back into my user account, reinstalled and got the same result. This is with client 7.5.1
Here's what I saw when I did the second installation.
First I got a Windows popup window asking for administrator privilege to install; I clicked yes.
I selected custom or advanced install. It installed the program to the default directory, but for the data it selected the administrator account. I manually changed that to the non-administrator account and finished the installation. I got the same result as the first time, meaning it started up immediately after installation, but when I restarted the computer it was only there for the administrator account.
FAH 7.5.1
Windows 10
I5 6400
GTX 1060
Re: Installation to wrong user account
Posted: Fri Jan 10, 2020 5:38 am
by bruce
FAH runs on a single account ... whichever is logged on during the install. As you discovered, Installing FAH on the Administrator account is not a useful process unless you always run your computer on that account (and I hope you don't).
After removing it, you installed it a second time and it asked you for install permissions. This is the expected way to do it correctly. That would NOT install it under the admin account, although your previous installation might not have been completely uninstalled. FAH installs using two directories. One directory is in one of the program directories where windows puts ALL software. That is independent of who does the installation. It also creates a working directory where it puts it's work files and where it puts your personal configuration files. That should depend ONLY on what user is logged on. ... and by Microsoft's standards, it's a hidden directory. All programs are supposed to use this site for their working files. (Actually, there's a third directory where it puts the shortcut which is assumed to be used to start the client)
If you fail to use the shortcut or if you changed things manually, you've created a non-standard installation and you're responsible for keeping everything straight. I recommend you uninstall again, logon as yourself, and reinstall. Either allow FAH to start automatically or use the shortcut provided to start it manually.
Since the hidden working directory for the admin user is in a different location than the hidden working directory for your regular user, you may not have installed both of them.
Re: Installation to wrong user account
Posted: Tue Jan 14, 2020 10:17 pm
by lumpy
You misread my message. I installed each time while NOT logged into my admin account.
Just to make sure, I deinstalled again, rebooted into my user (non-admin) account, and reinstalled without making any changes to the install options. I got the exact same result described in my original post.
I did not make any manual changes.
Re: Installation to wrong user account
Posted: Wed Jan 15, 2020 3:54 am
by bruce
How are you determining to which account FAH has been installed?
Post the log which is found in %APPDATA%\fahclient per the instructions referenced from the signature block of my previous post. The environment variable %APPDATA% points to a hidden directory belonging to the user who was logged on during the installation and which must be used when running FAHClient. Note: As an environmental variable, %APPDATA% changes depending on who is logged on.
If you previously created data files while logged on as administrator, there may be other copies of the applicable files but they will NOT be referenced when you start FAHClient automatically from your non-admin user or by using the shortcut belonging to that user. If you're trying to start FAHClient by opening the executable file FAHClient.exe found in the windows directory, you are NOT using the shortcut provided by FAH and it will not run because you have not opened the proper work directory. Microsoft prohibits Work files from being created in the Windows directory as part of their anti-virus protection policies.
Re: Installation to wrong user account
Posted: Wed Jan 15, 2020 2:59 pm
by lumpy
Code: Select all
*********************** Log Started 2020-01-15T14:27:33Z ***********************
14:27:33:************************* Folding@home Client *************************
14:27:33: Website: https://foldingathome.org/
14:27:33: Copyright: (c) 2009-2018 foldingathome.org
14:27:33: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
14:27:33: Args:
14:27:33: Config: C:\Users\usr\AppData\Roaming\FAHClient\config.xml
14:27:33:******************************** Build ********************************
14:27:33: Version: 7.5.1
14:27:33: Date: May 11 2018
14:27:33: Time: 13:06:32
14:27:33: Repository: Git
14:27:33: Revision: 4705bf53c635f88b8fe85af7675557e15d491ff0
14:27:33: Branch: master
14:27:33: Compiler: Visual C++ 2008
14:27:33: Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
14:27:33: Platform: win32 10
14:27:33: Bits: 32
14:27:33: Mode: Release
14:27:33:******************************* System ********************************
14:27:33: CPU: Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz
14:27:33: CPU ID: GenuineIntel Family 6 Model 94 Stepping 3
14:27:33: CPUs: 4
14:27:33: Memory: 15.94GiB
14:27:33: Free Memory: 10.43GiB
14:27:33: Threads: WINDOWS_THREADS
14:27:33: OS Version: 6.2
14:27:33: Has Battery: false
14:27:33: On Battery: false
14:27:33: UTC Offset: -8
14:27:33: PID: 6800
14:27:33: CWD: C:\Users\usr\AppData\Roaming\FAHClient
14:27:33: OS: Windows 10 Home
14:27:33: OS Arch: AMD64
14:27:33: GPUs: 1
14:27:33: GPU 0: Bus:2 Slot:0 Func:0 NVIDIA:7 GP106 [GeForce GTX 1060 3GB] 3935
14:27:33: CUDA Device 0: Platform:0 Device:0 Bus:2 Slot:0 Compute:6.1 Driver:10.1
14:27:33:OpenCL Device 0: Platform:0 Device:0 Bus:2 Slot:0 Compute:1.2 Driver:432.0
14:27:33: Win32 Service: false
14:27:33:***********************************************************************
14:27:35:<config>
14:27:35: <!-- Folding Slots -->
14:27:35: <slot id='0' type='CPU'/>
14:27:35: <slot id='1' type='GPU'/>
14:27:35:</config>
14:27:35:Trying to access database...
14:27:36:Successfully acquired database lock
14:27:36:Enabled folding slot 00: READY cpu:2
14:27:36:Enabled folding slot 01: READY gpu:0:GP106 [GeForce GTX 1060 3GB] 3935
14:27:36:WU00:FS00:Starting
14:27:36:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\Users\usr\AppData\Roaming\FAHClient\cores/cores.foldingathome.org/v7/win/64bit/avx/Core_a7.fah/FahCore_a7.exe -dir 00 -suffix 01 -version 705 -lifeline 6800 -checkpoint 15 -np 2
14:27:36:WU00:FS00:Started FahCore on PID 15276
14:27:36:WU00:FS00:Core PID:14568
14:27:36:WU00:FS00:FahCore 0xa7 started
14:27:36:WU01:FS01:Starting
14:27:36:WU01:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\Users\usr\AppData\Roaming\FAHClient\cores/cores.foldingathome.org/v7/win/64bit/nvidia/Core_21.fah/FahCore_21.exe -dir 01 -suffix 01 -version 705 -lifeline 6800 -checkpoint 15 -gpu-vendor nvidia -opencl-platform 0 -opencl-device 0 -cuda-device 0 -gpu 0
14:27:36:WU01:FS01:Started FahCore on PID 14640
14:27:38:WU01:FS01:Core PID:14924
14:27:38:WU01:FS01:FahCore 0x21 started
14:27:38:WU00:FS00:0xa7:*********************** Log Started 2020-01-15T14:27:38Z ***********************
14:27:38:WU00:FS00:0xa7:************************** Gromacs Folding@home Core ***************************
14:27:38:WU00:FS00:0xa7: Type: 0xa7
14:27:38:WU00:FS00:0xa7: Core: Gromacs
14:27:38:WU00:FS00:0xa7: Args: -dir 00 -suffix 01 -version 705 -lifeline 15276 -checkpoint 15 -np
14:27:38:WU00:FS00:0xa7: 2
14:27:38:WU00:FS00:0xa7:************************************ CBang *************************************
14:27:38:WU00:FS00:0xa7: Date: Oct 26 2019
14:27:38:WU00:FS00:0xa7: Time: 01:38:25
14:27:38:WU00:FS00:0xa7: Revision: c46a1a011a24143739ac7218c5a435f66777f62f
14:27:38:WU00:FS00:0xa7: Branch: master
14:27:38:WU00:FS00:0xa7: Compiler: Visual C++ 2008
14:27:38:WU00:FS00:0xa7: Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
14:27:38:WU00:FS00:0xa7: Platform: win32 10
14:27:38:WU00:FS00:0xa7: Bits: 64
14:27:38:WU00:FS00:0xa7: Mode: Release
14:27:38:WU00:FS00:0xa7:************************************ System ************************************
14:27:38:WU00:FS00:0xa7: CPU: Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz
14:27:38:WU00:FS00:0xa7: CPU ID: GenuineIntel Family 6 Model 94 Stepping 3
14:27:38:WU00:FS00:0xa7: CPUs: 4
14:27:38:WU00:FS00:0xa7: Memory: 15.94GiB
14:27:38:WU00:FS00:0xa7:Free Memory: 9.84GiB
14:27:38:WU00:FS00:0xa7: Threads: WINDOWS_THREADS
14:27:38:WU00:FS00:0xa7: OS Version: 6.2
14:27:38:WU00:FS00:0xa7:Has Battery: false
14:27:38:WU00:FS00:0xa7: On Battery: false
14:27:38:WU00:FS00:0xa7: UTC Offset: -8
14:27:38:WU00:FS00:0xa7: PID: 14568
14:27:38:WU00:FS00:0xa7: CWD: C:\Users\usr\AppData\Roaming\FAHClient\work
14:27:38:WU00:FS00:0xa7:******************************** Build - libFAH ********************************
14:27:38:WU00:FS00:0xa7: Version: 0.0.18
14:27:38:WU00:FS00:0xa7: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
14:27:38:WU00:FS00:0xa7: Copyright: 2019 foldingathome.org
14:27:38:WU00:FS00:0xa7: Homepage: https://foldingathome.org/
14:27:38:WU00:FS00:0xa7: Date: Oct 26 2019
14:27:38:WU00:FS00:0xa7: Time: 01:52:30
14:27:38:WU00:FS00:0xa7: Revision: c1e3513b1bc0c16013668f2173ee969e5995b38e
14:27:38:WU00:FS00:0xa7: Branch: master
14:27:38:WU00:FS00:0xa7: Compiler: Visual C++ 2008
14:27:38:WU00:FS00:0xa7: Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
14:27:38:WU00:FS00:0xa7: Platform: win32 10
14:27:38:WU00:FS00:0xa7: Bits: 64
14:27:38:WU00:FS00:0xa7: Mode: Release
14:27:38:WU00:FS00:0xa7:************************************ Build *************************************
14:27:38:WU00:FS00:0xa7: SIMD: avx_256
14:27:38:WU00:FS00:0xa7:********************************************************************************
14:27:38:WU00:FS00:0xa7:Project: 13829 (Run 880, Clone 0, Gen 81)
14:27:38:WU00:FS00:0xa7:Unit: 0x0000006780fccb095d66d2d95463989b
14:27:38:WU00:FS00:0xa7:Digital signatures verified
14:27:38:WU00:FS00:0xa7:Calling: mdrun -s frame81.tpr -o frame81.trr -x frame81.xtc -cpt 15 -nt 2
14:27:38:WU00:FS00:0xa7:Steps: first=10125000 total=125000
14:27:38:WU01:FS01:0x21:*********************** Log Started 2020-01-15T14:27:38Z ***********************
14:27:38:WU01:FS01:0x21:Project: 11714 (Run 0, Clone 6590, Gen 77)
14:27:38:WU01:FS01:0x21:Unit: 0x000000728ca304f15b21ad2748deba91
14:27:38:WU01:FS01:0x21:CPU: 0x00000000000000000000000000000000
14:27:38:WU01:FS01:0x21:Machine: 1
14:27:38:WU01:FS01:0x21:Digital signatures verified
14:27:38:WU01:FS01:0x21:Folding@home GPU Core21 Folding@home Core
14:27:38:WU01:FS01:0x21:Version 0.0.20
14:27:46:WU01:FS01:0x21:Completed 0 out of 7500000 steps (0%)
14:27:46:WU01:FS01:0x21:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
14:27:47:WU00:FS00:0xa7:Completed 1 out of 125000 steps (0%)
14:31:44:WU01:FS01:0x21:Completed 75000 out of 7500000 steps (1%)
14:32:17:WU00:FS00:0xa7:Completed 1250 out of 125000 steps (1%)
14:35:41:WU01:FS01:0x21:Completed 150000 out of 7500000 steps (2%)
14:36:44:WU00:FS00:0xa7:Completed 2500 out of 125000 steps (2%)
14:39:43:WU01:FS01:0x21:Completed 225000 out of 7500000 steps (3%)
14:41:07:WU00:FS00:0xa7:Completed 3750 out of 125000 steps (3%)
14:43:42:WU01:FS01:0x21:Completed 300000 out of 7500000 steps (4%)
14:45:24:WU00:FS00:0xa7:Completed 5000 out of 125000 steps (4%)
14:47:41:WU01:FS01:0x21:Completed 375000 out of 7500000 steps (5%)
14:49:29:WU00:FS00:0xa7:Completed 6250 out of 125000 steps (5%)
14:51:36:WU01:FS01:0x21:Completed 450000 out of 7500000 steps (6%)
14:53:37:WU00:FS00:0xa7:Completed 7500 out of 125000 steps (6%)
14:54:36:FS00:Paused
14:54:36:FS01:Paused
14:54:36:FS00:Shutting core down
14:54:36:FS01:Shutting core down
14:54:36:WU01:FS01:0x21:WARNING:Console control signal 1 on PID 14924
14:54:36:WU00:FS00:0xa7:WARNING:Console control signal 1 on PID 14568
14:54:36:WU01:FS01:0x21:Exiting, please wait. . .
14:54:36:WU00:FS00:0xa7:Exiting, please wait. . .
14:54:36:WU01:FS01:0x21:Folding@home Core Shutdown: INTERRUPTED
14:54:36:WU01:FS01:FahCore returned: INTERRUPTED (102 = 0x66)
14:54:42:WU00:FS00:0xa7:Folding@home Core Shutdown: INTERRUPTED
14:54:42:WU00:FS00:FahCore returned: INTERRUPTED (102 = 0x66)
14:55:03:Saving configuration to config.xml
14:55:03:<config>
14:55:03: <!-- Folding Slots -->
14:55:03: <slot id='0' type='CPU'>
14:55:03: <paused v='true'/>
14:55:03: </slot>
14:55:03: <slot id='1' type='GPU'>
14:55:03: <paused v='true'/>
14:55:03: </slot>
14:55:03:</config>
Re: Installation to wrong user account
Posted: Wed Jan 15, 2020 3:13 pm
by lumpy
The account "usr" is the admin account.
I don't ever start FAH manually. It starts automatically if I sign in to my admin account (which I rarely do)
The latest installation selected \usr\AppData for data even though it's the admin account, and I was not signed in to the admin account.
I also tried to install on a different computer as a test to see if it's something strange with this computer. I selected the custom install option and the data directory it selected on the second computer was the admin account user directory. I cancelled the installation on that computer at that point.
Re: Installation to wrong user account
Posted: Wed Jan 15, 2020 5:12 pm
by bruce
lOpen the Console text window (aka "command prompt") and type echo %APPDATA%. What does it say? Now log on to the other WINDOWS account and repeat those steps.
Where did you download this version of FAH's software and which version is it that you're installing?
Are you installing as a Windows service?
Re: Installation to wrong user account
Posted: Wed Jan 15, 2020 6:39 pm
by lumpy
Logged into my non-admin account "bik"
>echo %APPDATA%
C:\Users\bik\AppData\Roaming
When logged into my admin account I get:
C:\Users\usr\AppData\Roaming
I downloaded the Windows installer from the Foldingathome.org website, filename:
fah-installer_7.5.1_x86.exe
I don't understand the windows as a service question. I just tried to do a plain, default installation.
Re: Installation to wrong user account
Posted: Wed Jan 15, 2020 7:08 pm
by bruce
So please confirm that you removed the files in User/usr/Appdata/roaming/fahclientwere have been removed and that the installation while logged on as bik recreats files in one of the two places. They should be created in /user/bik/Appdata/roaming/fahclient
Re: Installation to wrong user account
Posted: Wed Jan 15, 2020 7:39 pm
by lumpy
I deinstalled again, then confirmed that the directory:
user/usr/Appdata/roaming/fahclient
was removed and also that there was no fahclient directory for user/bik
I reinstalled with the same results:
I logged out of the admin account (usr), and while logged into the non-admin account (bik), installed FAH again.
As before it installed the appdata under the admin username (usr).
user/usr/appdata/roaming/fahclient has a timestamp matching when I just installed FAH.
There is still no fahclient folder under the corresponding bik directory.
Re: Installation to wrong user account
Posted: Wed Jan 15, 2020 9:25 pm
by bruce
And at the time you did that FAH installation, what was the value of %APPDATA%?
Re: Installation to wrong user account
Posted: Wed Jan 15, 2020 10:42 pm
by lumpy
I did a quick deinstall, reboot, reinstall to verify
I checked via command prompt before install
>echo %APPDATA%
C:|Users\bik\AppData\Roaming (bik is the non-admin account)
During the installation it selected
C:|Users\usr\AppData\Roaming for the data location (usr is the admin account)
After installation I checked again:
>echo %APPDATA%
C:|Users\bik\AppData\Roaming
Re: Installation to wrong user account
Posted: Wed Jan 15, 2020 11:10 pm
by bruce
Strange. Apparently it has changed in the latest version. I don't remember testing this feature during client beta testing.
The fundamental question, though, is whether the properties of the shortcut match the properties of the installation.
You say there is no shortcut. That would cause a problem. How are you starting FAHClient from "blk"? Does it work?
Re: Installation to wrong user account
Posted: Wed Jan 15, 2020 11:18 pm
by lumpy
I cannot start it from bik. It will start automatically if I log into my admin account, but since I don't want to do that on a regular basis it's not running at all. There is a shortcut if I log into the admin account.
Re: Installation to wrong user account
Posted: Wed Jan 15, 2020 11:28 pm
by bruce
I understand your concern. I need to do some additional research.