Seeking basic instruction.
Posted: Sun Apr 06, 2008 8:30 am
My 1st post. Be gentle.
I have found F@H rather frustrating and from browsing this forum and reading posts on my team (JREF) forum, I see I'm far from alone in having problems.
It's clear there's much info on this forum.
The problem is that there is TOO much, too widely scattered.
I want F@H to be a background operation, not something I need spend time fiddling with. If it gives me problems, I'll dump it and I'm sure others will too.
We need to be able to get it running as well as possible as quickly as possible- ideally first time.
So what I would like to see here is a straightforard explanation of likely problems in one place, aimed at newbies. Maybe it's all here and I missed it- but that's the point; it's no use if it's not found. A table, broken down by OS and processor type perhaps.
Here are a few of my queries:
1. How do I safely stop F@H without losing the data? I thought the 15 minute (or whatever) setting insured that if a pc crashed, only 15 minutes data would be lost, but when this has happened (at 1477 of 1500 frames in one case), the software does not appear to have reloaded the data on restart- it started a new WU, wasting 36 hours of runtime.
2. What (basically) are the differences between the versions? SMP? Console? Service? What do these mean?
3. I have two PCs. Both have Nvidia graphics. I read that F@H does not work with Nvidia. But it does. Sometimes. What is the full story here?
4. I have a (new) quad core pc Intel Q6600 processor. 3GB RAM. Nvidia GeForce 8600GT- 512MB (can use up to 1.2GB of RAM), OS is Vista32 H. Premium (Gaah!). I tried double-installing the SMP client, which would seem to start, but every time I checked after a few hours, it was doing nothing. I reverted to a single installation of the graphic version, which is only using a fraction of the PC's resources.
What is the best way to optimise F@H on this sort of machine?
Again, sorry if I've missed the obvious somewhere, but maybe it can be made MORE obvious?
I have found F@H rather frustrating and from browsing this forum and reading posts on my team (JREF) forum, I see I'm far from alone in having problems.
It's clear there's much info on this forum.
The problem is that there is TOO much, too widely scattered.
I want F@H to be a background operation, not something I need spend time fiddling with. If it gives me problems, I'll dump it and I'm sure others will too.
We need to be able to get it running as well as possible as quickly as possible- ideally first time.
So what I would like to see here is a straightforard explanation of likely problems in one place, aimed at newbies. Maybe it's all here and I missed it- but that's the point; it's no use if it's not found. A table, broken down by OS and processor type perhaps.
Here are a few of my queries:
1. How do I safely stop F@H without losing the data? I thought the 15 minute (or whatever) setting insured that if a pc crashed, only 15 minutes data would be lost, but when this has happened (at 1477 of 1500 frames in one case), the software does not appear to have reloaded the data on restart- it started a new WU, wasting 36 hours of runtime.
2. What (basically) are the differences between the versions? SMP? Console? Service? What do these mean?
3. I have two PCs. Both have Nvidia graphics. I read that F@H does not work with Nvidia. But it does. Sometimes. What is the full story here?
4. I have a (new) quad core pc Intel Q6600 processor. 3GB RAM. Nvidia GeForce 8600GT- 512MB (can use up to 1.2GB of RAM), OS is Vista32 H. Premium (Gaah!). I tried double-installing the SMP client, which would seem to start, but every time I checked after a few hours, it was doing nothing. I reverted to a single installation of the graphic version, which is only using a fraction of the PC's resources.
What is the best way to optimise F@H on this sort of machine?
Again, sorry if I've missed the obvious somewhere, but maybe it can be made MORE obvious?