Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About jmatz

  • Rank
    Occasional forum poster
  1. Well, I already figured out the problem but yes I was doing an upgrade from 7.0 to 7.5, but it would seem that on 7.0 the config files are at: C:\Program Files\Dantz\Retrospect 7.0 and on 7.5 the config files are stored at: C:\Documents and Settings\All Users\Application Data\Retrospect Retrospect won't build the config files to be usable by 7.5 unless the config files are at this path when retrospect 7.5 starts up for the first time. All I had to do was place config70.dat in this path before 7.5 started the first time. You can't place them there after 7.5 has started up because at startup it will create config75.dat with nothing in it (since it didn't see config70.dat when it started up) which it will use by default every time it starts up and ignore any config70.dat you place in the directory. I suppose you could also just delete config75.dat and config75.bak and then place your copy of config70.dat into this directory and start up retrospect. Either way problem solved.
  2. Yeah, realized that retrospect won't rebuild the config70.dat file if there is a config75.dat file already at C:\Documents and Settings\All Users\Application Data\Retrospect which of course is created as soon as retrospect starts up which it does right after an install. I suppose you could just throw the config70.dat file into C:\Documents and Settings\All Users\Application Data\Retrospect and delete the config75.dat and config75.bak file and then start up retrospect and it will rebuild the config file.
  3. Nevermind, I figured this out. Just have to have the config70.dat file in the C:\Documents and Settings\All Users\Application Data\Retrospect folder when you install the upgrade. Can't put it in after the fact.
  4. When I upgrade from retrospect 7.0 to 7.5 how can I get the config files to transfer over? I don't really feel like adding all the clients and scripts again.
  5. From what I've heard is that the 64 bit version of the retroclient crashes and is basically unusable, and that you should use the 32 bit version. Is this still the case, or has this been addressed at all?