I had opened something right as it was starting, so it was only getting like 10% cpu... I closed everything and started it again, it'll be done at 1AM.... Celeron 900 on that machine.

OK, much better :D

Is there a way to get the F@H DOS window to not show up period?

http://folding.stanford.edu/cgi-bin/...name=VUG-Death

WOOOT!!

Are you using EMIII? If so, close the folding DOS window (CNTL+C) check the box in the option that says start FAH3 automatically and check the box that says Hide FAH3 window in the EMIII options. That's all there is to it.

Then you just start EMIII to fold.

I noticed that if i run the DOS console and EM3, that it takes longer to complete a frame. WTF is up with that?

It shouldn't. Could just be that its a harder WU.

harder?? that doesn't make sense. I've had the same WU be working at about 5 mins a frame, then open up em3 and have the frame jump up to about 12-15 mins. I've tried opening em3 with the console at the same time, over 30 mins per frame... this is al within the same WU... So i guess i'm just going to run the console by itself...

If you have EMIII set to open FAH automatically, it might open an additional instance. Either start the console, leave it showing (not minimized), and start EMIII. This will have EMIII just hide it (assuming you've checked those options). EMIII doesn't impact frame times, it just reads the log file. Something else is wrong.

ahh it doesn't matter. I've tried opening them at different times, it still slows it down... I don' care though.

Well if you have a check mark next to the path (ie - c:\F@H\) it will start F@H again. This is the area that you set up your "Box".
Make sure that you either uncheck this or do not have F@H previous to starting EMIII.

Dude, you don't need to open them separately. Open EMIII, goto options, click 'start FAH automatically'. Look on your main options page where it lists your computer name, make sure there's a check in the box by your computer (tells EMIII its local and not networked). Then just start EMIII to start FAH.

Yeah, I know what you mean. I only have one window (instance) running at one time. I've checked in the device manager and i can see the F@H, and it's using 100% cpu usage.

So how many computers are you guys running this on??

I have three going.

http://folding.stanford.edu/cgi-bin/...name=VUG-Death

I have 6 computers running it. Stats are below....

I'm running 3 full time and 1 part time. The 3 full time are AMD systems, and they beat intels in folding times by a good amount.

http://folding.stanford.edu/cgi-bin/userpage?q=OSUmaxx

Woohoo!
 

Got my dual Xeon back up & running.
Current Progress
Kinda neat what EM does. Don't know how to work the 'All Stats' option. Seems to just make a blank page.
All Stats

I'll somehow add the others at work to the list.

Re: Woohoo!
 

That's pretty cool. Are you using the EM web server, or are you using your own?

Re: Re: Woohoo!
 

My own. Sorry, but I can't trust or rely on something that is unproven. Gotta stick to what works.

I jsut added al my work machines. They should all show up now.

Re: Re: Re: Woohoo!
 

The last one gives me a big red x

Re: Re: Re: Re: Woohoo!
 

Yeah I saw that. I think its a bug. Not sure.

OMG I currently have a WU with 6000 frames in it.. is that even possible?

What protein is it? Look in the FAHlog.txt in your FAH folder, or check EMIII if you're still using it.

It might be a genome@home (protein 99x) unit. If the servers are clogged, you are sometimes redirected, though I've never had it happen to me.

1tst/pdb 1tst.xyz ??

Hmm.... there's nothing like P182, p206, etc?

Check here for protein info:
http://folding.stanford.edu/psummary.html

Nope, nothing like that.

Here's a sample log.

[03:09:59] - Ask before connecting: No
[03:09:59] - User name: OSUmaxx (Team 32)
[03:09:59] - User ID = EC0C4353BBFEF93
[03:09:59] - Machine ID: 1
[03:09:59]
[03:09:59] Loaded queue successfully.
[03:09:59] + Benchmarking ...
[03:10:02] The benchmark result is 6056
[03:10:02]
[03:10:02] - Autosending finished units...
[03:10:02] Trying to send all finished work units
[03:10:02] + Processing work unit
[03:10:02] Core required: FahCore_65.exe
[03:10:02] Core found.
[03:10:02] + Sent 0 completed units to the server
[03:10:02] - Autosend completed
[03:10:02] Working on Unit 02 [December 19 03:10:02]
[03:10:02] + Working ...
[03:10:02] - Calling 'FahCore_65.exe -dir work/ -suffix 02 -lifeline 1388
'

[03:10:02] Folding@Home Client Core Version 2.47 (June 14, 2002)
[03:10:02]
[03:10:02] Proj: work/wudata_02
[03:10:02] nsteps: 1000000 dt: 2.000000 dt_dump: 200.000000 temperature: 300.000000
[03:10:02] xyzfile:
[03:10:02] " 392 p202
[03:10:02] 1 CH3 -11.161591 -17.520088 86.104242 7 2
[03:10:02] 2 ..."
[03:10:02] keyfile:
[03:10:02] "NOVERSION
[03:10:02] ARCHIVE
[03:10:02]
[03:10:02]
[03:10:02] printout 1000
[03:10:02] writeout 1000
[03:10:02]
[03:10:02] integrate ..."
[03:10:02]
[03:10:02] Hashes matched on file work/wudata_02.dyn
[03:10:02] ARC file integrity verified
[03:10:02] Restarting from checkpointed files.
[03:10:02]
[03:10:02] Protein: p202
[03:10:02] - Run: 8 (Clone 15, Gen 12)
[03:10:02] - Frames Completed: 73, Remaining: 27
[03:10:02] - Dynamic steps required: 270000
[03:10:02]
[03:10:02] Writing local files:
[03:10:02]
[03:10:02] parameters work/wudata_02.prm
[03:10:02] - Writing "work/wudata_02.key": (overwrite) successful.
[03:10:02] - Writing "work/wudata_02.xyz": (overwrite) successful.
[03:10:02] - Writing "work/wudata_02.prm": (overwrite) successful.
[03:10:02] - Writing "work/wudata_02.key": (append) successful.
[03:10:02]
[03:10:02] PROJECT="work/wudata_02", NSTEPS=270000, DT=2.0000, DTDUMP=20.000000, TEMP=300.00
[03:10:03] TINKER: Software Tools for Molecular Design
[03:10:03] Version 3.8 October 2000
[03:10:03] Copyright (c) Jay William Ponder 1990-2000
[03:10:03] portions Copyright (c) Michael Shirts 2001
[03:10:03] portions Copyright (c) Vijay S Pande 2001

I'm running the graphical client on that machine. It says protien on the side and had that wierd thing listed. Right after it finished that one it did another like it, then went back to 100 and 400 frame protiens... Nother wierd thing is that it didn't do it frame by frame, it did it in frames of 200. sooooo wierd.