Announcement

Collapse
No announcement yet.

Somebody fill me in here...

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

  • Somebody fill me in here...

    Went out of the country for xmas vacation.
    Left all my machines running seti.

    One had a power bump. Didnt crunch for long.
    My friend reset my other two machines.
    His computer got screwed due to setidriver.
    Last machine got reset.

    I lost 4 weeks of seti crunching...
    I have to catch up.


    My Question...finally... ... ...

    When will it be madatory to have seti version 3.03 ?
    When will they stop accepting version 3.0 ?

    Im using 3.0 right now for obvious reasons.

    LaterZ



    ------------------
    I wasn't born, I was created.
    What the hell are we doing in the middle of the desert?

  • #2
    Well, it looks like the old i386-NT-clients is already killed. For all clients, the only date given is 31.01.2001.

    Comment


    • #3
      All my machines are still pumping version 3.0

      I guess I have till the 31st,
      What the hell is with this other dude saying its now mandatory

      ------------------
      I wasn't born, I was created.
      What the hell are we doing in the middle of the desert?

      Comment


      • #4
        <font face="Verdana, Arial, Helvetica" size="2">Originally posted by Zyn:

        What the hell is with this other dude saying its now mandatory

        </font>
        Is you referring to my badly worded "dead"-part or the contents by Matt Lebofsky? If the latter, he's one of the seti@home programmers...

        Comment


        • #5
          Nah, I wasnt talking about him.
          What the hell are we doing in the middle of the desert?

          Comment


          • #6
            More to add to this, One of my four computers running SETI actually came up with a warning message, saying to upgrade to version 3.03

            All of my other machines are still happy running 3.0

            ------------------
            I wasn't born, I was created.
            What the hell are we doing in the middle of the desert?

            Comment


            • #7
              I had that message a couple of weeks back on all 5 of my machines...

              Comment


              • #8
                Switched one of the Win2k servers to 3.03 yesterday because of that message (and I happened to be there) yesterday. Must go to office this evening and switch the rest of the iPAQs, and upload from my iPAQ if the a$$holes haven't shut it down.
                [size=1]D3/\/7YCR4CK3R
                Ryzen: Asrock B450M Pro4, Ryzen 5 2600, 16GB G-Skill Ripjaws V Series DDR4 PC4-25600 RAM, 1TB Seagate SATA HD, 256GB myDigital PCIEx4 M.2 SSD, Samsung LI24T350FHNXZA 24" HDMI LED monitor, Klipsch Promedia 4.2 400, Win11
                Home: M1 Mac Mini 8GB 256GB
                Surgery: HP Stream 200-010 Mini Desktop,Intel Celeron 2957U Processor, 6 GB RAM, ADATA 128 GB SSD, Win 10 home ver 22H2
                Frontdesk: Beelink T4 8GB

                Comment


                • #9
                  Well, went to work, and my machine popped up the message.

                  Came home and my other machine got the message as well.

                  That leaves me with one computer, still running seti version 3.0

                  ------------------
                  I wasn't born, I was created.
                  What the hell are we doing in the middle of the desert?

                  Comment


                  • #10
                    Zyn, the reason you haven't seen upgrade messages for all your old clients, is because you haven't looked on then they have downloaded a new unit. The upgrade message is there, but it becomes hidden by the "Receiving data: 10K ... 3xxK"-lines.
                    It's only then they are completely blocked for download the message aren't hidden by the download-lines.

                    The reason that old clients still can download wu is this: (from alt.sci.seti):
                    message-id: <3A6F6A27.5F18987F@clamazon.com>

                    Matt Lebofsky:
                    "3.03 sucks so much because we cleaned up a bunch of sucking code in this version. We found several cases existed in 3.0 where the clients could process entire workunits without ever touching the suck functions. This was an undetected conflict between the science and suck code, and has been fixed in 3.03. Now we are efficiently maximizing both science and sucking.

                    You are able to use 3.0 during random phases when I don't have mandatory upgrade messages turned on. I turn these on whenever I feel like it, and turn them off when 3.0 clients in tight loops load down our server.

                    As of time of writing, you cannot download workunits with 3.0, but you may be able to later. Within a week, no matter what, 3.0 will be dead in the water. We can only accept results from suckless clients for so long." (24 Jan 2001 23:52:03 GMT)

                    Comment


                    • #11
                      Thanks Rattledagger, that cleared my conscience(sp?)....

                      BTW I'm still running 3.00 and no stupid messages have popped up lately!

                      /Daniel

                      Comment


                      • #12
                        ?detiderc gnieb t'nera s'uw s'enihcam siht naem seoD .s'uw wen kcab sdnes dna stpecca revres ehT .0.3 noisrev gnihcnurc enihcam 1 evah llits I


                        In case you can't understand me.
                        My question is written totally backwards.




                        ------------------
                        I wasn't born, I was created.
                        What the hell are we doing in the middle of the desert?

                        Comment


                        • #13
                          He says,

                          I still have 1 machine crunching version 3.0. The server accepts and sends back new WU's. Does mean this machine's WU's aren't being credited?

                          Comment


                          • #14
                            dibrof nevaeH.daerht sdrawkcab rehtona toN !on hO
                            [size=1]D3/\/7YCR4CK3R
                            Ryzen: Asrock B450M Pro4, Ryzen 5 2600, 16GB G-Skill Ripjaws V Series DDR4 PC4-25600 RAM, 1TB Seagate SATA HD, 256GB myDigital PCIEx4 M.2 SSD, Samsung LI24T350FHNXZA 24" HDMI LED monitor, Klipsch Promedia 4.2 400, Win11
                            Home: M1 Mac Mini 8GB 256GB
                            Surgery: HP Stream 200-010 Mini Desktop,Intel Celeron 2957U Processor, 6 GB RAM, ADATA 128 GB SSD, Win 10 home ver 22H2
                            Frontdesk: Beelink T4 8GB

                            Comment


                            • #15
                              ): .gnikrow si eman-revres dlo eht sa gnol sa krow lliw stneilc ffo-tuc ydaerla toN .detnuoc llits si stluser lla ,stneilc-niw-non etelosbo rof tpecxE


                              Except for obsolete non-win-clients, all results is still counted. Not already cut-off clients will work as long as the old server-name is working.


                              [This message has been edited by Rattledagger (edited 26 January 2001).]

                              Comment

                              Working...
                              X