Is forced asm always on?

Not sure if this a bug, as I'm a new user.
I can't seem to alter the forceasm flag anywhere though I've searched the configs and options. Nor can I find an easy to apply oneunit call.This may be intentional so I hesitated to post a bug so early in. [Forcedasm caused a client warning to flag up anyway].
Also , I get an error 127 on shutting down the CPU client, but it seemed to restart an existing WU ok.
I'm using P4 CPU [rarely], GT240 and 8400GS[ near retirement] for Folding on XP SP2.

trev wrote:Not sure if this a bug, as I'm a new user.
I can't seem to alter the forceasm flag anywhere though I've searched the configs and options. Nor can I find an easy to apply oneunit call.This may be intentional so I hesitated to post a bug so early in. [Forcedasm caused a client warning to flag up anyway].
Also , I get an error 127 on shutting down the CPU client, but it seemed to restart an existing WU ok.
I'm using P4 CPU [rarely], GT240 and 8400GS[ near retirement] for Folding on XP SP2.

The -forceasm flag is applied to CPU/SMP clients be default and there is no option to disable it at this time. However, it is completely safe to ignore the warning message in FAHlog.txt that gets displayed. All Intel CPUs newer than and including the P4 and Pentium M have SSE2. IIRC on the AMD side everything from the Athlon 64 and newer supports SSE2. If you are running anything older than that, I don't see any point using the Tracker. (since such a system would only be able to run the single-core CPU client anyway)

I get too many questions regarding -oneunit so please see this:
http://fahtracker.com/manual.html#oneunit

For the error shutting down the CPU client, where is this error appearing? Does it appear in the log window in the main Tracker window? If so, this means there was a problem using the safe ctrl+c method to stop the client. If your WU resumed ok then you should be fine. If this continues to occur please post LOG.txt (located in the Tracker's main folder)

Thanks for info. Please relocate this thread if needed.
I'm posting to help with any issues, as the CPU and GPU.0 [an already running GT240 -not entered into Tracker currently] are working OK, so reply not urgent.

The prog is pretty good, actually,though didn't detect CPU type. See both logs below...

The 127 error came in tracker window and seems to be an hour shifted to the F@H log- is this usual?
[Last logged start @ 1916 on F@H log versus your window info]

The GPU1 eue is normal as only non suitable units are currently available for the 8400GS.

Tracker log [part]:

17:59:31] Updated GPU1 config, restarting client
[17:59:43] Stopped GPU 1
[18:01:27] Applied new config settings
[18:01:31] Applied new config settings
[18:01:40] Starting GPU 1
[18:01:40] Updated GPU1 config, restarting client
[18:01:41] Starting GPU 1
[18:01:41] Started new WU on GPU1
[18:16:17] GPU 1 failed to complete a project 10111 WU (UNSTABLE_MACHINE)
[18:16:17] Deleted WU on GPU1
[18:16:17] OneUnit mode enabled, not restarting GPU1
[18:18:59] Applied new config settings
[18:23:01] Error stopping CPU safely, code=127
[18:23:01] Stopped CPU
[18:23:02] Tracker exiting
[18:25:13] --------------------------------------------------
[18:25:13] FAH GPU Tracker v3.52 Startup
[18:25:13] --------------------------------------------------
[18:25:13] Detected OS: Windows XP
[18:25:13] Detected CPU:
[18:25:13] 0 Cores, 0 Threads, 000 MHz
[18:25:13] CPU detection failed, using defaults
[18:25:43] Starting CPU
[18:25:43] Resumed existing WU on CPU
[18:26:00] Error stopping CPU safely, code=127
[18:26:00] Stopped CPU
[18:26:01] Tracker exiting
[18:26:11] --------------------------------------------------
[18:26:11] FAH GPU Tracker v3.52 Startup
[18:26:11] --------------------------------------------------
[18:26:11] Detected OS: Windows XP
[18:26:11] Detected CPU:
[18:26:11] 0 Cores, 0 Threads, 000 MHz
[18:26:11] CPU detection failed, using defaults
[18:26:26] Starting CPU
[18:26:26] Resumed existing WU on CPU
[19:34:43] Error stopping CPU safely, code=127
[19:34:43] Stopped CPU
[19:51:09] Tracker exiting
[19:57:27] --------------------------------------------------
[19:57:27] FAH GPU Tracker v3.52 Startup
[19:57:27] --------------------------------------------------
[19:57:27] Detected OS: Windows XP
[19:57:27] Detected CPU:
[19:57:27] 0 Cores, 0 Threads, 000 MHz
[19:57:27] CPU detection failed, using defaults
[19:58:31] Tracker exiting
[20:03:30] --------------------------------------------------
[20:03:30] FAH GPU Tracker v3.52 Startup
[20:03:30] --------------------------------------------------
[20:03:30] Detected OS: Windows XP
[20:03:30] Detected CPU:
[20:03:30] 0 Cores, 0 Threads, 000 MHz
[20:03:30] CPU detection failed, using defaults
[20:08:31] Starting CPU
[20:08:31] Resumed existing WU on CPU
[20:09:37] Error stopping CPU safely, code=127
[20:09:37] Stopped CPU
[20:16:03] Starting CPU
** Highlight by user ** >>[20:16:03] Resumed existing WU on CPU
[20:53:42] Refreshed client status
[03:12:22] Refreshed client status


******* F@H log: *********

9:08:38] Resuming from checkpoint
[19:08:38] Verified work/wudata_01.log
[19:08:38] Verified work/wudata_01.trr
[19:08:38] Verified work/wudata_01.xtc
[19:08:38] Verified work/wudata_01.edr
[19:08:38] Completed 63640 out of 2000000 steps (3%)


--- Opening Log file [April 4 19:16:03 UTC]


# Windows CPU Console Edition #################################################
###############################################################################

Folding@Home Client Version 6.34

http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: D:\Downloads\FAH_GPU_Tracker_V2\FAH GPU Tracker V2\CPU
Executable: D:\Downloads\FAH_GPU_Tracker_V2\FAH GPU Tracker V2\FAH.exe
Arguments: -oneunit -forceasm

Warning:
By using the -forceasm flag, you are overriding
safeguards in the program. If you did not intend to
do this, please restart the program without -forceasm.
If work units are not completing fully (and particularly
if your machine is overclocked), then please discontinue
use of the flag.

[19:16:03] - Ask before connecting: No
[19:16:03] - User name: **** (Team ******)
[19:16:03] - User ID: **********
[19:16:03] - Machine ID: 3
[19:16:03]
[19:16:03] Loaded queue successfully.
[19:16:03]
[19:16:03] + Processing work unit
[19:16:03] Core required: FahCore_a4.exe
[19:16:03] Core found.
[19:16:03] Working on queue slot 01 [April 4 19:16:03 UTC]
[19:16:03] + Working ...
[19:16:03]
[19:16:03] *------------------------------*
[19:16:03] Folding@Home Gromacs GB Core
[19:16:03] Version 2.27 (Dec. 15, 2010)
[19:16:03]
[19:16:03] Preparing to commence simulation
[19:16:03] - Assembly optimizations manually forced on.
[19:16:03] - Not checking prior termination.
[19:16:04] - Expanded 255847 -> 397584 (decompressed 155.3 percent)
[19:16:04] Called DecompressByteArray: compressed_data_size=255847 data_size=397584, decompressed_data_size=397584 diff=0
[19:16:04] - Digital signature verified
[19:16:04]
[19:16:04] Project: 10424 (Run 44937, Clone 0, Gen 11)
[19:16:04]
[19:16:04] Assembly optimizations on if available.
[19:16:04] Entering M.D.
[19:16:10] Using Gromacs checkpoints
[19:16:10] Mapping NT from 1 to 1
[19:16:10] Resuming from checkpoint
[19:16:10] Verified work/wudata_01.log
[19:16:10] Verified work/wudata_01.trr
[19:16:10] Verified work/wudata_01.xtc
[19:16:10] Verified work/wudata_01.edr
[19:16:10] Completed 63640 out of 2000000 steps (3%)
[19:43:44] Completed 80000 out of 2000000 steps (4%)
[20:17:55] Completed 100000 out of 2000000 steps (5%)
[20:51:01] Completed 120000 out of 2000000 steps (6%)
[21:23:54] Completed 140000 out of 2000000 steps (7%)
[22:00:54] Completed 160000 out of 2000000 steps (8%)
[22:37:13] Completed 180000 out of 2000000 steps (9%)
[23:10:25] Completed 200000 out of 2000000

The CPU detection not working consistently is a known problem with Windows XP.

The Tracker's logfile uses local time, so it's normal for it not to match up with FAHlog.txt (which uses UTC)

I have a dual core P4 to drop in my m/c if and when needed -plus the work for the 8400GS [if it comes back, that is] so coould end up running 4 clients.
Tracker seems well up to the job- the issues raised don't alter the workings, simply a good idea to highlight experiences and queries so others can see them in passing.
One big pain running multiple clients was stopping the wrong one, usually!
Also, for people starting fresh a simple autoload for clients is useful, and good to have all the levers in one place.
Now, about that project graphics question PG never got sorted... :~)