Windows SMP Beta goes Open

BillytheImpaler said:
Is that command window running in administrator mode?

If I run it in admin mode I get another different error

fah-1.jpg
 
Try busting open the .bat file and add ".exe" to the calls. IIRC, Vista seems to think that you're asking for a .com file unless you specify an extension.

@echo off

smpd.exe -install

mpiexec.exe -register

mpiexec.exe -np 2 foo

pause
 
BillytheImpaler said:
Try busting open the .bat file and add ".exe" to the calls. IIRC, Vista seems to think that you're asking for a .com file unless you specify an extension.

How would I do that mate? Bit of a novice with stuff like this

I've opened the bat and presented with the following:

@Echo off
smpd -install
mpiexec -register
mpiexec -np 2 foo
pause

What do I change?

EDIT - nevermind, your edit answers my question hehe

Still doesnt work :( just comes up with the following error just with exe after each call now :(
 
Maybe it's not viewing the right directory. :confused:

Try opening a command window as an administrator they typing
cd "C:\Program Files\Folding@Home Windows SMP Client V1.01"
hit enter

then type
install.bat
hit enter

This assumes you let it install to the default location. If not change as necessary.
 
BillytheImpaler said:
Maybe it's not viewing the right directory. :confused:

Try opening a command window as an administrator they typing
cd "C:\Program Files\Folding@Home Windows SMP Client V1.01"
hit enter

then type
install.bat
hit enter

This assumes you let it install to the default location. If not change as necessary.

That worked! :D:D:D

Thank you soooo much
 
Well that didnt last long, crashed out on me :( Looks like I cant use my main rig for folding anymore, every type of folding client just seems to lock it up
 
BillytheImpaler said:
:( 2610 is by far the worst of the WinSMP WUs. It takes aaaaaaaaages to crunch on my machines.

No no no no... 2610 are my favourite of the WinSMP units... here are my average PPDs taken from FahMon benchmarks.

2604 = 2297.04 ppd
2605 = 2374.71 ppd
2610 = 2758.64 ppd
2651 = 2448.70 ppd
2652 = 1922.23 ppd
 
Is it overclocked, Steedie?
DreederOcUK said:
No no no no... 2610 are my favourite of the WinSMP units... here are my average PPDs taken from FahMon benchmarks.

2604 = 2297.04 ppd
2605 = 2374.71 ppd
2610 = 2758.64 ppd
2651 = 2448.70 ppd
2652 = 1922.23 ppd
Shush you and your quad cores. We plebes stuck with dual cores or dual procs are at the losing end of the 2610 stick, so to speak. ;)
 
BillytheImpaler said:
Is it overclocked, Steedie?Shush you and your quad cores. We plebes stuck with dual cores or dual procs are at the losing end of the 2610 stick, so to speak. ;)

Yeah tis overclocked, but, and I'm not ruling it out, I've never had stability issues before, when I first set my overclock I primed it for 24 hours solid no problems, and I've been running it for about 8 months since stable

But needless to say, it is probably the cause behind it, I'll give it a go at stock, doubt I'd lose much ppd on 200Mhz anyway :p
 
Id recommend you run Memtest86 or similar...

I had problems with one of my old rigs running FaH and it would prime fine for hours and hours, gaming, encoding, everything worked great, but running FaH i would get EUEs all over the place, using Memtest86 i tracked it down to a failing 1gb Crucial Ballistix stick, got it RMAed and all was well again.
 
It must have been an overclock stability issue

Been running fine since then :)

Just wierd how I never noticed problems before after 7-8 months use
 
Back
Top Bottom