• Tag Archives digital archaeology
  • Digital Archaeology: Dell Inspiron 531s

    The Dell Inspiron 531S is a slimline desktop. Dell made several models of a similar design in both Intel and AMD varieties. This particular one has a Athlon 64 X2 5000+. The Intel models (Core 2 duo based) used the 530s model designation. Hardware specs of this one include:

    • CPU: Athlon 64 X2 5000+ @ 2.6 GHz
    • Memory: 3 GB DDR2 @ 800 MHz
    • Video: GeForce 6150LE

    For more complete specs, check out the HardInfo report.


    When this desktop was contemporary, this CPU was reasonably fast. the GeForce 6150LE is part of the chipset and for an integrated solution, it was pretty good for the time but if you wanted to do gaming, you would still need a discrete GPU.

    The 3GB of RAM was pretty typical for the time. The reason being that, despite the fact that most CPUs were 64-bit by this time, Windows and most apps and drivers were still primarily 32-bit. This machine shipped with Windows Vista. There was a 64-bit version of Vista but most OEM PCs shipped with the 32-bit version. By the time 64-bit drivers for more devices were widely available, I think things were already moving on to Windows 7. Vista was not very popular.


    The fastest officially supported CPU on this machine is the Athlon 64 X2 6000+ which runs at 3.1 GHz (Socket AM2). This would be a modest upgrade with, very roughly, a 20% increase in performance. More significant upgrades would be the addition of a discrete GPU and an SSD. Moving up to 4GB would be helpful too.

    Given the small size and limited power supply, the GPU selection will be limited. Something like a GT 1030 or some other card that doesn’t require an external power connection would be the best card that would work for this machine. It would have to be a low profile card with associated low profile bracket. This would still be a massive improvement over the integrated video.


    This machine has an issue that I haven’t been able to work out yet. When ever I move the window for the BOINC application, the screen scrambles and the computer freezes. I’m not sure if this is a software or hardware problem. I don’t seem to have issues with any other application nor do I have problems using the BOINC app (provided I don’t move the window around) or any of the projects I run. There’s no temperature problem and otherwise it seems perfectly stable. However, I’ve run this version of Linux and BOINC on other machines with this chipset (though perhaps later revisions?) without any problem. I was going to try adding a discrete GPU. I have one that is small enough but I don’t have a low profile bracket handy. At this point, it’s been running with 100% CPU activity for a few days now with no problems so I’m not convinced this is a hardware problem.

    Speaking of BOINC, this PC is still capable of running most of the projects I normally participate in. These projects include Einstein@home, Asteroids@home, Milkyway@home, Universe@home, World Community Grid, and Rosetta@home though 3 GB is a marginal amount for trying to run Rosetta tasks. You can see how it is doing overall at FreeDC.


  • Digital Archaeology: Floppy Disk #14 – SIGMET.DOC

    A summary for those that haven’t been keeping up with this series:

    I found a number of 5.25″ disks at a thrift store a number of years ago (sometime in the late 1990s to the best of my recollection). I finally got around to acquiring a 5.25″ disk drive and extracting the contents a several years back. Since then, I have been occasionally posting the content here.

    Based on the contents, most or all of these disks were apparently once owned by someone named Connie who used to run the “Close Encounters” Special Interest Group (SIG) on Delphi in the mid 1980s.

    The following description of this SIG was found in a document on one of the disks: “This SIG, known as ‘Close Encounters’, is a forum for the discussion of relationships that develop via computer services like the Source, CompuServe, and Delphi. Our primary emphasis is on the sexual aspects of those relationships.”

    This service was text based and was accessed via a modem and whatever terminal program you had available for your computer to dial in with. Many of these disks have forum messages, e-mails and chat session logs. All of this is pre-internet stuff and I am not aware of any archives in existence today that contain what was on Delphi in the 1980s.

    This post includes the contents of PROT.DOC. This is a set of rules to be followed to participate in a conference or group chat that occurred every Saturday on Delphi in the Friendship Circle Special Interest Group (SIG). I guess there would be a specific topic each week and, based on the description here, it seems like it would be pretty heavily moderated. This message includes all the commands you can use during the conference.


    =-=
    SIGMET.DOC
    =-=


    I am sure I speak for all the SigOps in expressing my
    appreciation to Wes and JohnWG for a very informative
    conference.  I'm sure we are all looking forward to the
    changes in the SIG program.
    
    We all seem to realize that regular conferences with fellow
    SigOps and Delphi personnel are a must for a successful
    partnership.  However, if I may, I would like to make some
    suggestions about these conferences.
    
    First, my SIG, The Friendship Circle, has held conferences on
    CIS for several years and has been holding them on Delphi
    since last August.  We have a conference protocol that allows
    each person to have his say uninterrupted. Although this
    protocol tends to slow things down a bit, you do have the
    feeling of having accomplished something when a conference
    is over and the frustration of trying to have your say is
    greatly diminished.
    
    Second, all TFC conference topics are announced in advance,
    using Dmail.  I would suggest that possible topics for
    discussion be sent to Chris and that he schedule conferences
    to discuss these particular topics.  This, in addition to
    the conference protocol, will allow for a more organized
    meeting and we will not all feel as tho we are jumping from
    one thing to the other without resolving anything.
    
    Granted, since SigOp conferences are new, there is a lot to
    discuss, but we need to do it in an orderly manner.  Also I'd
    like to suggest that we try to stick to a two-hour time limit
    for conferences and have the conferences on the same night
    or same date as this will help enable many of us to work the
    conferences into our busy schedules.  (But please, please
    don't have the conferences on Saturday nights!) 
    
    Another suggestion to make things flow smoothly would be to
    use the /send function to say your individual "hellos" and
    "goodbyes" when someone says he/she is leaving.  This will
    allow the normal conference to continue uninterrupted.
    
    Let's all work together as a team to have the most successful
    SIGs around!
    
                               -Connie, SigOp, The Friendship Circle
    
    P.S.  If you would like to review the conference protocols I
    mentioned above, TFC Info article #10 is the place to look.
    Or you can send me a note via Dmail and I'll send you a copy.
    Thanks.
                                                                                     
    

  • Digital Archaeology: Floppy Disk #14 – PROT.DOC

    A summary for those that haven’t been keeping up with this series:

    I found a number of 5.25″ disks at a thrift store a number of years ago (sometime in the late 1990s to the best of my recollection). I finally got around to acquiring a 5.25″ disk drive and extracting the contents a several years back. Since then, I have been occasionally posting the content here.

    Based on the contents, most or all of these disks were apparently once owned by someone named Connie who used to run the “Close Encounters” Special Interest Group (SIG) on Delphi in the mid 1980s.

    The following description of this SIG was found in a document on one of the disks: “This SIG, known as ‘Close Encounters’, is a forum for the discussion of relationships that develop via computer services like the Source, CompuServe, and Delphi. Our primary emphasis is on the sexual aspects of those relationships.”

    This service was text based and was accessed via a modem and whatever terminal program you had available for your computer to dial in with. Many of these disks have forum messages, e-mails and chat session logs. All of this is pre-internet stuff and I am not aware of any archives in existence today that contain what was on Delphi in the 1980s.

    This post includes the contents of PROT.DOC. This is a set of rules to be followed to participate in a conference or group chat that occurred every Saturday on Delphi in the Friendship Circle Special Interest Group (SIG). I guess there would be a specific topic each week and, based on the description here, it seems like it would be pretty heavily moderated. This message includes all the commands you can use during the conference.


    =-=
    PROT.DOC
    =-=


    .lt
     10  24-NOV  CONFERENCE PROTOCOLS
    
    
    The FRIENDSHIP Circle holds weekly conferences each Saturday
    night starting at 9:15 PM EST on a variety of subjects.
    Conference schedules are posted well in advance as are the
    protocols to be observed during the conference.
    
    Existing protocols for the Saturday Conferences:
    
    ?          to signal the moderator that you have a comment or
    question you would like a chance to voice.
    
    ga         means you are done with your talk.
    
    :::msg:::  you are either unavailable temporarily, or just
    returning.  There is no need to announce your arrival or
    departure into the conference area as the Delphi conference
    program does that for you. You could use this, however, if you
    want others to know that you will return shortly or something
    of that nature.
    
          The conference moderator has acknowledged your ? or
    !. (Please be patient.)  Also, you will be called in turn to
    the best of the moderator's ability to keep track.
    
    !          Use this when you have a pressing but brief comment
    or question for the current speaker.  The speaker has the
    first option to allow the interrupt.  If this is abused, it
    will be treated like a '?'. It's  purpose is to get immediate
    and relevant comments which can otherwise get lost in a long
    line.
    
    ATN     should be self explanatory.
    
    Often you will find that these protocols are not strictly
    followed because of the "mood" of the evening.  Do not be
    alarmed or upset if you suddenly see a lot of comments and
    then have the conference moderator (JohnMyself) call for ATN!
    We do try to follow the protocols as outlined in fairness to
    all, but being human, we do get carried away at times!
    
    As a matter of common courtesy, please keep side comments and
    /send messages to a minimum.  Thank you.
    .el