EMIII problems

[Codegen]

Well, I have it set up to monitor 2 systems, the P4 (local) and the P233 (network).

I got it to monitor the P233 properly (Samba is a pain in the ass), but I can't get it too monitor this one..

I renamed the file to FAH500_Console.exe and that worked for the P233. Didn't work to well.

BTW, I am using WinXP on the P4

 

[Mayhem33]

You did browse to the folder with F@H in it and point it to the F@H exe.
I have had it say that this is not the right thing....just tell it yes it is and it should work.

 

[Codegen]

Did that. All it does is this:

 

[Mayhem33]

for how long? It takes a bit to figure it out.

 

[Codegen]

It just stays that way.

As i said, the P233 is just fine. P4 (which is the local rig) doesn't want to register.

 

[Mayhem33]

Do you have the F@H folder shared?

 

[Codegen]

Nope.

 

[Mayhem33]

Right click on the folder and click properties....select to share the folder...if you are running XP.
Hope this works for you!

 

[Codegen]

Well, I restarted it, but now it's 1000 frames down the shitter

 

[Codegen]

As I said, it's working now, but probably a good thing it wasn't like I lost a weeks worth a work or anything (it was 2 days).

The 2 machines are on different proteins now (P233 is on 2002 and the P4 got 884). Y

The reason why the P233 is saying it was started in 2006 is because it has a pissy cock on it, (PC-Chips motherboard, never seen that that managed to keep time)

 

[Mayhem33]

Glad it is working for you.

 

[Codegen]

Problem is, is that it's still not updating for the P4. The way to do it with the P233 seems to be to restart the program after EM3 is loaded. This doesn't work with the P4.

The P233 stats update in real time.