Client Expired, What's next?

[CoW]8(0)]

Well my SMP beta client expired. How should I go about fixing this? Should I use the regular no-nonsense console client (I hear it supports SMP now), or should I continue with the next beta?

The expired beta installed a good amount of stuff onto my machine if I recall correctly. Does the other beta client make use of it? Does the no nonsense client make use of it? I really don't like having things like these dangling on my machine.

 

[Xilikon]

Just download the next beta client and replace fah.exe only. You don't need to change anything else and it will resume where you left.

 

[Crosshairs]

Hmm..when did it expire, and how do I know if I have the new one?...I just installed the SMP client last week...

 

[Pocatello]

The old client expired on October 1st.

Do like Xilikon says...

download the whole thing, extract / run it in a safe folder... [not your working SMP folder] and then copy and paste the fah.exe into your real SMP folder. Just that one file: fah.exe. Start again and you are good to go until this one expires.

 

[Crosshairs]

The old client expired on October 1st.

not to be a noob.....But how do I know if I have the old client or the new one??
I mean, its still working, so do I assume that I'm OK?

Is there a version # anywhere I can look at?

 

[APOLLO]

Should I use the regular no-nonsense console client (I hear it supports SMP now)

Since when does the standard client support SMP?

 

[CoW]8(0)]

Actually it was the "Windows 2000/XP/Vista Graphical client"

What's changed?
All the modifications from the previous version are listed in the change log. On the download page, just click on the version number link that's immediately to the left of your download link. Changes of particular note:

- support in client and backend infrastructure for passkey
- accept message from server (for example PRFC) and print to unitinfo and
queueinfo (only on units assigned from servers supporting this)
- integration of SMP support into the standard client. Run with the -smp
flag on eligible hardware to receive SMP units.
- detailed detection of CPU type and features
- no benchmark on startup
- We regret that a v6 Windows/SMP client is not yet available.

 

[Pocatello]

not to be a noob.....But how do I know if I have the old client or the new one??
I mean, its still working, so do I assume that I'm OK?

If you reboot and restart the SMP client--- it just won't work. It will say that it is expired.

Since when does the standard client support SMP?

Things are a changin' over at stanford.

 

[[BRO]Alaskan]

Remember when you start the new client to add the "-smp" flag after the the start command or you will be starting the console client

 

[Xilikon]

Remember when you start the new client to add the "-smp" flag after the the start command or you will be starting the console client

Yes for v6 clients but I assume we are talking about the Windows SMP here, which doesn't use this flag yet.

 

[[BRO]Alaskan]

Windows is not using the V6.0 client yet and that is the client that supports both the console and SMP so I assumed that is what the poster was refering to. I guess the original poster needs to say which O/S he is using so we do not give out bad info.

 

[aldamon]

Windows is not using the V6.0 client yet and that is the client that supports both the console and SMP so I assumed that is what the poster was refering to. I guess the original poster needs to say which O/S he is using so we do not give out bad info.

I wish Stanford would just release v6 for everything so isn't so much confusion.

 

[CoW]8(0)]

This is getting confusing.

In their V6 FAQ for both the console and graphical client they say:
- integration of SMP support into the standard client. Run with the -smp
flag on eligible hardware to receive SMP units.
....
- We regret that a v6 Windows/SMP client is not yet available.


That's one confusing changelog

 

[Xilikon]

This is getting confusing.

In their V6 FAQ for both the console and graphical client they say:
- integration of SMP support into the standard client. Run with the -smp
flag on eligible hardware to receive SMP units.
....
- We regret that a v6 Windows/SMP client is not yet available.


That's one confusing changelog

The log is about the OSX and Linux clients which include both cpu and smp clients. The Windows SMP isn't released, hence this note.

 

[[BRO]Alaskan]

This is getting confusing.

In their V6 FAQ for both the console and graphical client they say:
- integration of SMP support into the standard client. Run with the -smp
flag on eligible hardware to receive SMP units.
....
- We regret that a v6 Windows/SMP client is not yet available.


That's one confusing changelog

If it was to easy a caveman could do it.