outpost's cfg file - bad format?

Hello. I ran system restore now OP's cfg files are all corrupt. Is there a solution short of creating rules all over again?

http://img441.imageshack.us/img441/9423/op1qt.jpg

 

The only option I could suggest would be to use a hex editor to compare the "corrupted" file with a new one since the problem could be just in the first few bytes.

However creating a new configuration from scratch would likely take less time. You may also find using disk imaging software (like Drive Snapshot or Acronis TrueImage) to take a full backup a more reliable alternative than System Restore.

 

I also grabbed a cfg file from secure zone - same problem. I didn't use TI because image was a little old.

 

That suggests that the configuration may have been altered by another program since even an old configuration from a previous Outpost version should be read in (what do you mean by secure zone?). However this doesn't change my suggestion given above.

 

this sucks. I don't really want to configure it all over. I guess I have to

You don't know what Acronis secure zone is?