Copying Textpad preferences to new machine

[Eric Vitiello]

I would like to be able to copy all of my textpad preferences to another machine. What do I need to make sure I get (obviously everything in the textpad directory). I'm assuming there is data in the registry... what branches of the registry are needed?

--Eric

[Andreas]

HKEY_CURRENT_USER/Software/Helios/Textpad
with everything underneath.
Make sure textpad is closed when you import textpad entries into registry, otherwise they might get overwritten with the old versions.
It is not necessary to copy everything from Textpad directory, normally subdirectories Samples and User should be enough.
Of course Textpad should first be installed properly on your second machine.

Andreas

[Jeff Epstein]

In the help documentation, look under

How To... --> Customize Settings --> Transfering between PCs

[robbage]

With the number of times I've seen this question come up (including myself , I'm surprised there isn't something built into TP to export all settings (including the ones that don't happen using the registry method).

[Jeff Epstein]

It *would* be pretty sweet to have all configuration (macros, key combinations, clipbooks, registry branch, tools, ...?) saved to a tiny file. Perhaps exe? Perhaps zip?

Then, move that file to the new machine, and some command would install everthing into the TextPad on it. It would have to do things like rectify the install branch (you could have TextPad installed in a different directory than on the original machine) and maybe some other stuff. Like "don't overwrite macros" or whatever. Not sure.

Perhaps this is something that could be, largely, done outside of TextPad? Maybe in Windows batch or Perl...?

Anyway, good idea.

[Bob Grove]

I think you've described pretty well the "settings export file" idea,
but I feel that this should all be managed from within the program
at a logical level, not from WinDoze or OS level. Then, simply
take your TXP version-compatible file and import to another
machine/user/etc.

The only OS responsibilities I want are trying to keep the kernel
happy and healthy.

I'm just as surprised as *robbage* that (considering the great engineering
that makes this product the best tool in the known galaxy) this has not
been addressed within the extant product. Perhaps there are bigger
fish we don't know about!