Windows SMP Beta goes Open

babyface uk · 20 Mar 2007 at 15:40

BillytheImpaler said:
Well there goes my theory. I thought it might have something to do with switching on or off battery power.

it is connected to a UPS but has had no power outages since F@H being installed

Babyface

growse · 20 Mar 2007 at 16:19

Ok, so I install it as a service on a windows 2k box, with two HT xeons in it, and mpiexec has been sitting here at 17% the whole time. What's the reason for this? Does it even work as a service?

BillytheImpaler · 20 Mar 2007 at 16:21

growse said:
Does it even work as a service?

As is indicated by the documentation and numerous posts in this thread, the service function is disabled and will not work. You have to run it in an open command window.

Cob · 20 Mar 2007 at 16:34

Having a nightmare here atm.

The first WU ran and uploaded fine. But since it finished at ~2am I've had the 'CoreStatus = FFFFFFFF (-1) Client-core communications error: ERROR 0xffffffff' loop.

Reinstalling it has no effect.

*edit*

Now getting

[16:40:25] Could not open Sas file
[16:40:25] LE_IO_ERROR
[16:40:25]
[16:40:25] Folding@home Core Shutdown: FILE_IO_ERROR

x64 Vista btw.

growse · 20 Mar 2007 at 16:46

BillytheImpaler said:
As is indicated by the documentation and numerous posts in this thread, the service function is disabled and will not work. You have to run it in an open command window.

/slaps self.

I wish I could read

Berserker · 20 Mar 2007 at 17:57

While manual persuasion is required (as in changing service options), and there are bugs, it can be 'convinced' to work. In other words, your mileage may vary.

PS - I have it working on the borged box. Just as well - didn't want that console sat around too long.

VeNT · 20 Mar 2007 at 19:45

Cob said:
Having a nightmare here atm.

The first WU ran and uploaded fine. But since it finished at ~2am I've had the 'CoreStatus = FFFFFFFF (-1) Client-core communications error: ERROR 0xffffffff' loop.

Reinstalling it has no effect.

*edit*

Now getting

x64 Vista btw.

use the administrator account
make sure you've all the windows updates

VeNT · 20 Mar 2007 at 19:46

Snapshot said:
Something a lot faster than a stock E6300 which is averaging 26" 32' per frame for a 2610.

3.2GHz E6300 will get you 22min/frame

shadowscotland · 20 Mar 2007 at 20:16

just had same problem as Cob - (why didn't I check it this morning

) that's 20h lost

mine got to 3rd step and stoped.

stoped client - closed both exe's and restarted - but so far no joy....

...off to read peoples answers

BillytheImpaler · 20 Mar 2007 at 20:27

growse said:
/slaps self.

I wish I could read

It's all good, we all do it from time to time. I'm guilty of many crimes of n00bishness.

Cob · 20 Mar 2007 at 21:07

shadowscotland said:
just had same problem as Cob - (why didn't I check it this morning ) that's 20h lost mine got to 3rd step and stoped.

stoped client - closed both exe's and restarted - but so far no joy....

...off to read peoples answers

I just dropped my new RAM back to 1:1 and it's started to run fine again.

It seems that the client may be very very sensitive. Orthos blend stable and have been linux SMP folding in VMWare for the past week with it, but the Windows SMP client don't like it.

Looks like I've some more tweaking to do.

rincinDub · 20 Mar 2007 at 21:56

Anyone here using dual core Amd. If so post some times for me. Thanks

rich99million · 20 Mar 2007 at 22:14

rincinDub said:
Anyone here using dual core Amd. If so post some times for me. Thanks

[21:58:09] Project: 2651 (Run 0, Clone 20, Gen 5)

[21:58:20] Completed 0 out of 500000 steps (0 percent)

[20:14:43] Completed 500000 out of 500000 steps (100 percent)

Total time - 1day 22hrs 16mins 23secs - roughly 27mins 45secs a frame

That's a 1760 point WU on my [email protected] - averaging out to 912PPD if my calculations are correct (hmmm that's higher than I remember the other WUs getting)

edit: here's a whole thread full of times - http://forum.folding-community.org/ftopic18565.html

shadowscotland · 21 Mar 2007 at 00:01

Cob said:
I just dropped my new RAM back to 1:1 and it's started to run fine again.

Looks like I've some more tweaking to do.

sorry - I never got the errors, just stoped at 3rd step :confused:

trying again with Ubuntu/VM

Edit: linux smp up and running at home - winSMP at work

lucifersam · 21 Mar 2007 at 00:31

Good to see this new client since linux + VMware can only use 2 CPUs, will be getting my core 2 quaddie down to some crunching tomorrow I hope.

BillytheImpaler · 21 Mar 2007 at 00:32

lucifersam said:
Good to see this new client since linux + VMware can only use 2 CPUs

Really? I hadn't heard this. :confused:

lucifersam · 21 Mar 2007 at 00:37

Well each instance of VMware can only be set up to use 2 cores I did not want two instances of Linux running ontop of my normal windows to use all 4 cores. (this could be a lot of rubbish of course, I just could not find a way of getting VMware to use more than 2 cores for each VMachine)

Mattus · 21 Mar 2007 at 03:24

BillytheImpaler said:
Really? I hadn't heard this.

lucifersam said:
(this could be a lot of rubbish of course, I just could not find a way of getting VMware to use more than 2 cores for each VMachine)

'tis true:

VMware Server does not support guests with more than two virtual processors. You can, however, power on and run multiple dual-processor virtual machines concurrently.

dunc · 21 Mar 2007 at 03:28

Be careful if on a domain when running as a service that the folder under which you have installed the smp client has explicit write permissions for the user you have installed as. Apparently the default permissions are not good enough. See my post on the FAH forums here

Dunc

VeNT · 21 Mar 2007 at 03:49

VMware Server does not support guests with more than two virtual processors. You can, however, power on and run multiple dual-processor virtual machines concurrently if you've enough ram.

fixed

Windows SMP Beta goes Open

Man of Honour

Man of Honour

Man of Honour