Today's Checksum

Discussion in 'Trojan Defence Suite' started by Rainwalker, Mar 28, 2004.

Thread Status:
Not open for further replies.
  1. Rainwalker

    Rainwalker Registered Member

    Joined:
    May 18, 2003
    Posts:
    2,376
    Location:
    USA
    Hello all.....i just got the latest TDS update file and the DC site showed it to be
    2507E01F49FE1A5BAEC75D326143F495
    and i am showing 1e2664723fa95b36b0c827f33d2b8121
    anyone else with showing similier :doubt:
     
  2. TheQuest

    TheQuest Registered Member

    Joined:
    Jun 9, 2003
    Posts:
    2,304
    Location:
    Kent. UK by the sea
    Hi, Rainwalker

    Just checked mine with CS MD5 checksum, in TDS directory dated 27/03/04.

    And it is 1E2664723FA95B36B0C827F33D2B8121

    Which is the same as yours is showing.

    TheQuest :cool:
     
  3. Rainwalker

    Rainwalker Registered Member

    Joined:
    May 18, 2003
    Posts:
    2,376
    Location:
    USA
    Hi... TheQuest....... thanks for getting back
    hmmmm i am showing the my update as 2-28 but not sure if it's because i got the update today or not. That must be it as it's the weekend. Maybe they forgot to post MD5 hash :doubt: I'll get monday's update and try again. Being the same as yours is close enough for me :)
     
  4. Jooske

    Jooske Registered Member

    Joined:
    Feb 12, 2002
    Posts:
    9,713
    Location:
    Netherlands, EU near the sea
    [33025 references - 12195 primaries/9366 traces/11464 variants/other]
    How about the last references?
    For me was Databases updated 26-03-2004
     
  5. TheQuest

    TheQuest Registered Member

    Joined:
    Jun 9, 2003
    Posts:
    2,304
    Location:
    Kent. UK by the sea
    Hi, Jooske

    Same as mine but one day later [27/03/04]
    1E2664723FA95B36B0C827F33D2B8121

    TheQuest :cool:
     
  6. Gavin - DiamondCS

    Gavin - DiamondCS Former DCS Moderator

    Joined:
    Feb 10, 2002
    Posts:
    2,080
    Location:
    Perth, Western Australia
    Same.. dont know what happened but the database was OK ! Will fix it but I think it was related to PG not allowing the MD5 program that runs during the final stages of a database job ;)
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.