Announcement

Collapse
No announcement yet.

Berkeley stop sending units to pre CLI3.03 clients?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Berkeley stop sending units to pre CLI3.03 clients?

    Just uploaded a few units using Setiqueue. Got some kind of error message which I was not able to read because Setiqueue does not display the seti@home error messages. The uploaded units were counted however. Not sure if this is related to the shutting down of pre-CLI 3.03 clients.

  • #2
    I have got the message to it states as follow:

    Platform: i386-winnt-cmdline
    Version: 3.0
    .
    .
    .
    A new version of SETI@home for i386-winnt-cmdline is available at http://setiath
    ome.ssl.berkeley.edu. You must download it to continue running SETI@home.
    The server has no data now; will try again.


    /Daniel

    Comment


    • #3
      Aggghhhh, ssooner than I thought,

      Found data file: no. Found result header file: no.
      Getting data - connecting to server.
      A new version of SETI@home for 386-winnt-cmdline is available at http://setiathome.ssl.berkeley.edu. You must download it to continue running SETI@home.
      The server has no data now; will try again.


      Must update my computers at work, good job each machine has a 10 unit cache.
      Everything I say is true apart from that which is not

      Comment


      • #4
        Aggghhhh, ssooner than I thought,

        Found data file: no. Found result header file: no.
        Getting data - connecting to server.
        A new version of SETI@home for 386-winnt-cmdline is available at http://setiathome.ssl.berkeley.edu. You must download it to continue running SETI@home.
        The server has no data now; will try again.


        Must update my computers at work, good job each machine has a 10 unit cache.
        Everything I say is true apart from that which is not

        Comment


        • #5
          Just downloaded new units. So I guess its back in operation..

          Comment


          • #6
            Arrgh, here we go again! 2:30pm EST

            Comment

            Working...
            X