Windows SMP Client, general troubleshooting

[Samuknow]

I appreciate you taking the time to learn so much and work so hard at this.

I will be a few days out before getting SMP running on my rig. I will see what happens then.

[Necorum]

Wolfs problem is he isnt folding smp clients under necorum

[Strongwolf]

Originally Posted by SteveI

Careful with overclocks. The memory & CPU are both very highly stressed while folding, and the SMP core is very sensitive. If the WU has a lot of progress, let it go until it completes... Last thing you need is to have the core dump the WU @ 99% due to an overclock problem.

Whaaaa,Whaaaa, Whaaaaa, that's exactly what happened. Lost the wu (5000) @99%

I know I'm becoming a pain in the neck, but I'm feeling better and want to deal with this once and for all (or not).

First: Can't find the "install.bat file.

Second: What am I suppose to type after ---> "account <domain\user> [WOLF3\Juan]"
This is where troubles start. OK no OC. I give up for the time being.
Now......can anybody help me?,...please!!!

[dabaerman]

no SMP joy yet.

[ThunderRd]

@Strongwolf:
The install.bat file is in the installation directory. Run it by double clicking on it. When you see the "account <domain\user>" prompt, just enter the correct information. If "[WOLF3\Juan]" is correct, don't type anything, just press enter, and then enter your password when prompted. This will install and register MPI and SMPD services. After that you'll see the "if you see this twice" message.

@Dabaerman:
Corestatus = 63 is most likely a permissions problem. I've never seen it personally but it's documented, and I have researched it for you. It could also be an MPI and/or SMPD install problem. Are you logged on as Administrator with full rights? Do you have an actual password? It WILL NOT RUN with a blank password. Rerun the install.bat and enter your password. Also make sure that you have .net 2.0 installed.

If you still have problems check this thread:

Folding-community.org :: View topic - Error 63 (99)

If you are able to solve the problem, please post the solution here, step by step, when you have time.

[Samuknow]

I was thinking password as well. I had that error before.

[dabaerman]

OK, I think I have it. since I haven't used SMP before, I had to get the SMP
file and install it. then there is the SMP update that I didn't use. stsveI says
to replace the .exe and I didn't. so, when I get home, I will make sure to do that.


Ron

[ThunderRd]

When did you download the file? If you have downloaded it in the past week it is current. You need no update. If you downloaded it before that, re-DL now, and re-install. Overwriting the .exe as Steve suggested is only for users that are already running the old version, and don't want to re-install. You are doing a fresh install, so DL the current file.

I believe the installation file you have is current; if it wasn't, the client wouldn't even start and you couldn't generate a log. The command window would open for about 1 second, and close immediately. That's how I realized that I hadn't updated one of my boxen last week. It just wouldn't run.

[dabaerman]

" Credentials for xxx rejected, aborting. unable to connect to xxx.
press any key to continue."

back to square one.

Ron

well, if you haven't figured it out, I did. seems like the admin password was different than
the one I tried to use. changed password, install complete!!!


Ron

[dabaerman]

and folding too.

Ron

[dabaerman]

oops.

[ThunderRd]

Yeah, that looks ok. (I forgot to mention that it is useful to use the correct password)

Get used to those IO_ERROR messages when starting...it's one of the things they are going to try to correct in the next version. You showed patience by waiting before re-starting, that's also good. Windows needs a bit of time to release file handles on mpiexec before it can fully close down the program. If the box gets really grouchy and won't start the client, a reboot will often solve the problem.

If you want to learn more about what the client is doing you can start it up with the -verbosity 9 flag; it will log all kinds of useless and arcane information that may be of interest to you.

After you are familiar with the client, if you want to run it as service and rid your machine of the window, let me know and I'll guide you through it.

[dabaerman]

thanks for all the help guys; ThunderRd, Strongwolf, Sam. yes, as a service later, I will certainly ask for guidance!!!


Ron

[Strongwolf]

One flawless intallation of SMP to Wolf3.
We can count now with an Opty 175x2 @ 2.4 (sorry can't help myself).

[Daniel ~]

Well done Ron! ":O}

[dabaerman]

another problem has reared it's ugly head. after a client shutdown, good
or bad, how am I to restart it. when I use the fah icon in the SMP folder, the
client starts from the very beginning, ie, the setup (dos) screen.
Windows auto updated/restarted the pc and I have lost that first wu. attempting to restart the client.

Ron

[dabaerman]

did I mention that I am an unemployed brain surgeon? no patients! continuing to practice
on self, just in case.

Ron

[ThunderRd]

Are you saying that each time you start the client it asks for your username, team name, etc? That's odd.

But looking at your log it appears that it isn't; it's just being bitchy.

Try this. Reboot the box, and make a shortcut to the executable on the desktop. Then run it with this argument: -configonly

This should take you through all of the setup dialog without starting up the cores. It will shut down when you have finished. Then, remove the argument from the command line, and start it again. Does it ask for the info again? If it does, I've no idea how to help. If it doesn't, and it just doesn't want to start, just be patient and do as you have done before; shut the client down with ctrl-c and kill the mpiexec process and the core processes, if any are running. Use task manager to do this.

It may take one to many attempts to kick it. It can be aggravating. You'll know when it's running by reading my previous post:
http://www.aoaforums.com/forum/samuk...tml#post456400

Running a backup routine has saved many a WU for me. You may want to consider it.

[smiffy]

Hi All

If any help I have found repairing Microsoft.Net Framework 2 cured a few smp problems as well.I think the error 63 was one of them.

Another single core rig on the way soon.Just got to figure out which of my 3 single core works best under the Prometia before the cold bug kicks in.
Smiffy

[Strongwolf]

Hi ya, smiffy!!!