Jump to content

chudgins

Members
  • Content count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About chudgins

  • Rank
    Occasional Forum Poster
  1. chudgins

    Retrospect 7 for Windows Released

    Yep, that did it. I was done in by my own paranoid "just in case" action of renaming the old file and keeping it in the original directory. I thank you, and my data thanks you! --Chris
  2. chudgins

    Retrospect 7 for Windows Released

    I just installed "Retrospect Update for Retrospect 7.0 (Win) version 7.0.8.103" for my copy of Retrospect Professional 7.0. Before dragging the new rdu.rpx file into the directory where the Retrospect executable resides, I named the old version rdu_old.rpx (just in case). I then copied the new rdu.rpx into the Retrospect directory as instructed. Next, when I tried to start Retrospect, I received an error popup stating - "Retrospect has encountered a serious error: A log of this error has been written to the file "assert_log.utx". Please tell Dantz about this problem." First, it looks like Retrospect is unable to determine the nature of the "serious error". Second, I could find no "assert_log.utx" file. The closest thing I can find to an error log is a file named "rthlpsvc.log". Third, I renamed the new rdu.rpx file to rdu_crashes.rpx, and renamed rdu_old.rpx to rdu.rpx. Unfortunately, this did not help the situation. I received the same error message. Now I am stuck without being able to perform backups at all. The only solution I see is to do a clean install of Retrospect, but I don't know if this will cause problems with my existing catalog. Here is my computer setup: 650 megahertz Intel Pentium III 640 MB RAM Windows XP Professional Service Pack 2 (build 2600) Any assistance will be greatly appreciated!
×