Registry Tool -- FAQ
Registry Tool Database file FAQs
Question: Is a Registry Tool Database file completely Cross Platform Compatible?
Absolutely! You can even take a Registry Tool Database file created in Windows Vista and send the keys and values into Windows 95. The only real limitations are that you can not create a new root key of HKLM in Windows NT/2000/XP/2003/Vista and Windows 95/98/ME does not contain Registry Security information, so you can not send Security information into Windows 9x/ME.
Question: I opened a Windows 95 Registry Tool Database file while running Windows XP and when I went to the Restore command, I was warned about different versions of Windows, why?
Registry Tool is a very careful program. Registry Tool warned you to be sure you realized the file originally came from a Windows 95 import, and you did not open the wrong file.
Question: Will Registry Tool import a Reg file or Dat/Hive Binary file -- even if the file was made from a different version of Windows?
Yes, because a Registry Tool Database file is Cross Platform Compatible, the Reg file or Dat/Hive binary file source is not important. The only stipulation is that Windows will not open a binary file older than the version you are using. For example, you can open and import a Windows 2000 hive in Windows XP, but you can not open a Windows XP file in Windows 2000.
Question: If I create a Registry Tool Database file from a Dat/Hive binary file or Reg file, can the Registry Tool Database still be used to send data into a different version of Windows?
Yes, because a Registry Tool Database file is Cross Platform Compatible, the keys and values it contains can be sent into any version of Windows.
Question: I have Dat/Hive binary files from an old or broken Windows installation on another hard drive or partition, can Registry Tool import the binary files, and enable me to edit the files? Can I also send the data in the old binary files into the active Windows registry I have Registry Tool loaded in?
Yes to both questions. If you edit a loaded Dat/Hive Binary file, the edits are saved in the file when Registry Tool closes it. This means you can import a Dat/Hive Binary file, creating a Registry Tool Database file, find the "bad" data, edit the binary file, and put it back in a "broken" Windows installation. Once you import the Dat/Hive Binary file and create a Registry Tool Database file, you can use the Registry Tool Database to edit ANY active Windows registry.
Loading Dat/Hive Binary files FAQs
Question: What is a Dat/Hive Binary file and where are they located?
Dat/Hive Binary files are the files Windows uses to store the Registry on your hard drive. In Windows NT 4, 2000, XP, and Vista, the files are located in <windows installation path>\system32\config folder. They are named, without file extension, according to the HKLM key they contain. For example the HKLM\Software key is store in the "Software." file. User settings will be in Documents and Settings\<user name>\NTuser.dat file.
Question: I notice that in the Professional Edition, I have the option to load a Dat/Hive Binary file during the Reg file import process and when I open an existing Registry Tool Database, why would I want to do that?
Loading a Dat/Hive Binary file enables you to use Registry Tool's editing commands to modify it. For example you can send keys and values from the Registry Tool Database file into the binary file or use the Restore command as a mass editing command and send keys and values into the binary file. You can also use the Restore command and actually build a replacement Dat/Hive Binary file for a corrupt one. Search and Replace and Search and Delete can also be used, as well as the entire array of Registry Tool analysis and diagnostic features.
Question: If I load a Dat/Hive Binary file does Registry Tool automatically edit the file if I perform some type of edit or can I control what editing targets are used?
Registry Tool will always ask before performing edits during any editing command process, even if you select the Binary file as an edit target during the binary load process.
Question: Will Registry Tool compare any two Registry Tool Database files -- even if the files were made using data from different versions of Windows?
Yes, because a Registry Tool Database file is Cross Platform Compatible and the comparison is performed between the Registry Tool Database files independent of Windows.
Restore, Mass editing, and Send To command FAQs
Question: I have a Registry Tool Database file that was created from data contained the Registry of another version of Windows. Will Registry Tool send this data into a different version of Windows?
Yes, because a Registry Tool Database file is Cross Platform Compatible and the Restore and Send To Registry commands simply read the keys and values from the Registry Tool Database file and send them to the edit target, active Registry or Dat/Hive Binary file.
Question: Can I use the Restore command as a mass editing command but *only* send the keys and values in the Registry Tool Database file into the active Registry or loaded Dat/Hive Binary file -- and leave all the existing active Registry or loaded Dat/Hive Binary file keys and values untouched?
Yes. Registry Tool does not replace the Registry like other registry software. It uses the Registry Tool Database file as a template and edits the edit target, active Windows Registry, or a loaded Dat/Hive Binary file. The Restore command even contains target scope settings that check the edit target for the presence of a key, and if the key already exists, Registry Tool skips the key.
Question: Can I use a Registry Tool Database file as a backup of my Registry, in case I need to recover from a disaster?
Yes. Registry Tool Database files can be used to completely restore the Windows Registry.
© Copyright 1996 - 2009 Registry Tool -- All rights reserved. Registry Tool ® and Registry Functions PageFrame ® are registered trademarks -- All rights reserved. All other trademarks are the property of their respective owners.