Page 1 of 1

TP7.5.1 Where to place additional .SYN files?

Posted: Fri Oct 02, 2015 11:13 am
by chrisjj
I guess the reason that running TP7.5.1 after installing on a machine having TP6.5 caused errors reporting .syn file load failures, is that the TP7 install has failed to carry over additional .SYN files from TP6.

Really poor.

Where should I store the additional SYN files to avoid this on the next upgrade? I cannot see any support for for a personal .SYN folder http://i.imgur.com/ACeFCp4.png http://i.imgur.com/aaOQX5z.png .

The only supported location seems to be C:\Users\Chris\AppData\Roaming\Helios\TextPad\<version> , and for TP6.5 C:\Program Files (x86)\TextPad\system worked. Neither seems proof from this fail.

Thanks.

Posted: Fri Oct 02, 2015 8:54 pm
by MudGuard
press the ... button beneath the folder list next to the edit field, and you can choose whatever location you want.

(it might be necessary to copy the files from the previous to the new location ...)

Posted: Fri Oct 02, 2015 10:47 pm
by chrisjj
I'm fully aware of that, thanks.

If anyone has an answer to the question, I'd be grateful.

Posted: Mon Oct 05, 2015 6:53 pm
by woho
in preferences/ folder (linux PC here without TP) you can define folders for different files textpad uses - like e.g. *.syn files
so it is a good idea not to use a folder in a \Program FIles subdirectory like you did in 6.5 (and I guess it was the default at least in win XP) which might lost at a new install

anyway it is a good idea to backup the %APPDATA% directory of Win7 (8,10 i do not know) (=C:\Users\Chris\AppData\Roaming\data in your case) for future installations

Posted: Mon Oct 05, 2015 9:21 pm
by chrisjj
woho wrote: it is a good idea not to use a folder in a \Program FIles subdirectory like you did in 6.5 (and I guess it was the default at least in win XP) which might lost at a new install
I used a folder in Program Files because that's what the install instructions say https://archive.is/IVEno#selection-7071.0-7075.130

Devs, please pass on this request for these instructions to be fixed.
woho wrote:anyway it is a good idea to backup the %APPDATA% directory
I did do, thanks, and that allows a manual workaround after the failure. It doesn't answer the question of how to avoid the failure.