Import of .REG info
When importing the reg info from my computer to the portable version of HeidiSQL the session information does not seem to transfer?
Ah, I guess you clicked the "Import settings" menu item? Yes, that one just starts regedit.exe with the file provided as parameter. The portable version works in its own registry folder, and the folder in your .reg file obviously has a different root name than the one you need for your portable instance, e.g. "[HKEY_CURRENT_USER\Software\HeidiSQL]". What I should do is creating a copy of that .reg file before the import actually runs, and modifiy the path to the correct one.
Well the portable uses registry, but only as long as the process runs, and in a different folder than the non-portable does. You can even start multiple portable instances which all use their own registry folder. When you exit the portable, the registry folder is dumped into the portable_settings.txt file, and the registry folder gets deleted.
I'm on the way to change the export file format, from a .reg file into the format used for the portable mode. The advantage is we can import into the used registry path, independently of the portable mode. And, you don't need admin privileges to import such files. I'll probably keep backwards compatibility to .reg files, by detecting the file extension. But solving the above issue will only be done with that new settings file format.
Code modification/commit
6ef3d17
from ansgar.becker,
13 years ago,
revision 7.0.0.4128
Use home brown file format for exporting and importing registry settings, as used for portable_settings.txt. Registry dumps cannot be imported into a separate registry key for a portable instance, which is hereby fixed, see http://www.heidisql.com/forum.php?t=10503 .
maybe another look at this issue is worthwhile.
http://code.google.com/p/heidisql/issues/detail?id=1805
i found that you don't need admin rights to import non-privilaged registry keys if you use "reg.exe" instead or "regedit.exe"...
http://code.google.com/p/heidisql/issues/detail?id=1805
i found that you don't need admin rights to import non-privilaged registry keys if you use "reg.exe" instead or "regedit.exe"...
Please login to leave a reply, or register at first.