Announcement

Collapse
No announcement yet.

Seti @ Home & MURC, on the side

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    Seti @ Home & MURC, on the side

    OK, I just don't get it. I used to not care, but since I've been knocked out of the top 200 I have a new goal to strive for

    How the hell do you all of you get such good hours on your units? I get 32 hours on average w/ K6-2 500 and 192MB Ram. What am I missing? I have it set to run 24x7 no matter what I'm doing on the computer and I still get these crappy hours/pdu(per data unit). I know the K6-2 has a shittier FPU but jesus! is it that bad?

    Dave
    Ladies and gentlemen, take my advice, pull down your pants and slide on the ice.
    Tags: None
  • #2
    Are you using the Windows "screen saver" version. You might want to try the NT Command Line version. It runs in a DOS window. It doesn't, however, shut down when you start using your computer.

    Paul
    paulcs@flashcom.net

    Comment

    • #3
      There are 2 options in running Seti.

      1. Data analysis runs only when the screen saver is active or application window is maximized, or...

      2. Data analysis alwyas runs (recommended only for fast computers with atleast 64MB RAM)

      I have option 2 selected. Does the NT version run in Win98(dos mode) as well? You confuse me when you say 'DOS' in NT since there is not DOS in NT. Do you mean a command prompt?

      Dave

      ------------------
      I can never think of a good signature...~

      Ladies and gentlemen, take my advice, pull down your pants and slide on the ice.

      Comment

      • #4
        The "cmd" line version is one of the correct names for it, another is the "chui" or character interface version.

        It just runs faster than the windows version.

        In the windows version, make sure that the "blank-screen after" is set to 0 seconds.

        Hope this helps....

        Guvyer
        Gaming Rig.

        - Gigabyte GA-7N400-Pro
        - AMD Athlon 3200+ XP
        - 1.5GB Dual Channel DDR 433Mhz SDRAM
        - 6.1 Digital Audio
        - Gigabit Lan (Linksys 1032)
        - 4 x 120GB SATA Drives, RAID 0+1 (Striped/Mirrored)
        - Sony DRU-500A DVD/+/-/R/RW
        - Creative 8x DVD-ROM
        - LS120 IDE Floppy
        - Zip 100 IDE
        - PNY Ultra 5900 (256MB)
        - NEC FE950
        - DTT2500 Cambridge Soundworks

        Comment

        • #5
          Sorry guys, but my GUI version runs an average of 7 hours per WU, on my P3-450, minimized all the time.

          I just use version 1.06
          (Check my average time in the list, I'm around place 70)

          Jord.
          Jordâ„¢

          Comment

          • #6
            Hi Dave,

            go for the Intel cmd line version or if that one doesn't work, grab the Non-Intel cmd line version ...

            I made a directory structure with 20 subdirectories, each containing a different WU. I run those WUs from a batch with '-stop_after_process' and lateron another batch with '-stop_after_xfer' so that I can render 20 WUs in a row without having to connect to SETI ...
            Despite my nickname causing confusion, I am not female ...

            ASRock Fatal1ty X79 Professional
            Intel Core i7-3930K@4.3GHz
            be quiet! Dark Rock Pro 2
            4x 8GB G.Skill TridentX PC3-19200U@CR1
            2x MSI N670GTX PE OC (SLI)
            OCZ Vertex 4 256GB
            4x2TB Seagate Barracuda Green 5900.3 (2x4TB RAID0)
            Super Flower Golden Green Modular 800W
            Nanoxia Deep Silence 1
            LG BH10LS38
            LG DM2752D 27" 3D

            Comment

            • #7
              Well holy-be-joleez! I guerss I'll have to try the 'cmd' line version then

              Thanks everyone,

              Dave
              Ladies and gentlemen, take my advice, pull down your pants and slide on the ice.

              Comment

              • #8
                My K6-2 400 at home knocks out a command line w/u in 16.5 hrs.
                Everything I say is true apart from that which is not

                Comment

                • #9
                  I run a minimun of two command line versions by placing the executable in different directories, then I shorten the name of the .exe to setiathome-1.exe setiathome-2.exe, etc. On my dual systems (Celery550, PII350, PPro200) I run 6, 6, and 3 instances, respectively. My single processor systems (PII400, PPro200) I run 4 instances and 2 instances, respectively. So basically, I am working against 21 WU's at any time. This has helped me reach 12th place.

                  I use SetiSpy to baby sit the units in case their are upload issues. When I find the time, I will even figure out how to cache some down because the Seti server has been down before I ran out of WU's.

                  Have fun and go MURC!

                  ------------------
                  ABIT BP6, 192MB PC100 RAM, dual 366->>550MHz, 3DFXCool GlobalWin FEP32 'Lil Mofo' h/s fans. G400 DH, 3COM 905B NIC, Buslogic FlashPoint LW Ultra-Wide SCSI, SBLive PCI 1024. Segate Medalist PRO 9.1 GB UW SCSI 7200RPM, Maxtor 20.4GB ATA66 7200RPM 2MB Cache, 8GB tape b/u, IDE 32x CDROM, SCSI 4xwrite/8xread Panasonic CD writer, 4 more various 2GB SCSI drives.


                  Tyan Thunder K7, 768MB Registered DDR ECC, 2xMP2200+, Radeon 9700 Pro, Adaptec 2940U2B Ultra2 SCSI, TB Santa Cruz, Pyro 1394DV. RAID 0 stripe set on hacked Promise UltraTX2 with dual WD 120MB SE drives. HP DVD200i DVD+RW drive.

                  Comment

                  • #10
                    I use the GUI version running in the background all the time, and my times are not that bad last time I looked. Hell, I am still in the top 25, and I am running on one system only.

                    Comment

                    • #11
                      Do we not refer to it as the NT command line version because it's confusing, or because I'm way off base about what the "winnt" stands for in the executable's name?

                      Helevitia, in my experience, in Windows 98 the command line version runs in a DOS Window. In Windows 2000, the command line version runs in the "command line console," which looks an awful lot like DOS.

                      It is confusing. The letters "NT" are in the name of the executable, as is i386, but it runs fine in Windows 98 (in a DOS window). It, of course, is not limited to 386's either.

                      This all made selecting the file to download a bit of a challenge (for me at least).

                      Paul
                      paulcs@flashcom.net

                      Comment

                      Previous template Next
                      Working...
                      X