Contains all newer d7x formatted config files.
The first three files you never want to delete, or would save if you wished to delete your config and start over (these files will save you the trouble of re-registering the app.) These are the only files which are encrypted as a whole file.
- d7x.License.dat – This license file contains the d7x product keys and your d7x account credentials.
- d7II.License.dat – This is a backup of your d7II license (product keys, d7x account credentials, plus the technician password) if updated from d7II to d7x, and a direct copy of the d7II license filename “Reg.Settings.dat”
- d7x.Admin.dat – This file contains your technician password, some subscription type details, and (future) user credentials for multi-user licenses.
The next files contain configuration information for specific areas of d7x which you can save/restore or delete individually to maintain those settings.
All of these files can be opened with notepad.exe for viewing/editing as necessary (not recommended unless directed by support.) Some individual settings in *.cfg files (e.g. account credentials) may be encrypted and should never be edited manually. Note that editing an *.cfg file while d7x is running will not change d7x behavior, and your edits will be overwritten with previous values when d7x saves it’s configuration or is closed/restarted; if you must edit manually, always edit/save with d7x closed.
- d7x.cfg – The main d7x settings file, containing most of the app’s various settings that aren’t described below as part of the rest of these configuration files.
- FtpServers.cfg – FTP server configuration only. Account credentials are individually encrypted.
- SmtpServer.cfg – SMTP server configuration only. Account credentials are individually encrypted.
- d7xBrowser.cfg – Configuration for the web browser defaults and search engine defaults; this is shared between d7x and the separate d7xBrowser.exe file.
- PFD_*.cfg (e.g. PFD_RunBox.cfg) – Persistent Form Data for various windows in d7x where data from drop down combo boxes, text boxes, check boxes, and other options are saved to persist for subsequent usage. For example PFD_RunBox.cfg contains a history of files and their command line arguments that you ran through the various “run box” features in d7x, and will populate the drop down selection boxes with that data so you can easily select it again without browsing or retyping anything. These files can be deleted to wipe that data.
Other config file types:
- *.txt – Config files for the drop down d7x menus at the top of the main d7x interface.
- Folders.txt – File system links to open from the Folders menu.
- RegLinks.txt – Registry shortcuts (to open in Regedit.exe) from the Registry menu.
- SiteSearch.txt – Websites for specific site searches from the Search menu.
- oeminfo.ini – This file is created when you fill out the “Support Information Button Text” section under Config > OS Customization > Windows XP ONLY Branding Options. It is copied directly to the \Windows directory when branding a Windows XP system (along with an OEMLOGO.BMP if one is found in the .\d7x Resources\Config\Logos directory) and these are found/displayed from the System Properties screen in Windows XP.
- d7xSupportSuiteConfig.zip – If you have configured dSupportSuite (now included with d7x) from d7x and saved the configuration for re-use on other systems, this zip file contains the dSupportSuite-specific configuration files which will be copied to other systems after installing the dSupportSuite software through d7x.
The next two files are can be deleted to re-trigger app/config/defs updates and product activation behavior.
- d7x.Refresh.cfg – Contains information to track the last check for updates to the app itself and your account activation status, as well as config files and definitions from the cloud portal (or your FTP server if configured.) Deleting this file will force a re-check for all of the above items.
- d7x.UpdateInfo.cfg – Contains all app update related information as downloaded from our server during an update check. Deleting this file may trigger a recheck and fresh download of the information, depending on information also present in the d7x.Refresh.cfg file.
- PostUpdateTasks.cfg – Contains task information for d7x to perform when d7x restarts after an update has occurred. This file is only written prior to restart after update, and so it is temporary and can safely be deleted without causing any issues to the operation of d7x, though it’s existence causes no adverse affects either.
d7II-based configuration files which are currently used by d7x as-is. These are moved from .\Config when starting a new session. Currently this directory contains all configuration related to “Auto Mode” profiles as well as Custom Apps. With the possible exception of specific custom apps, you should never edit most of these files directly.
d7II-based configuration files which are only used by d7x if they exist during an existing session; when starting a new session they will be moved to .\d7x Resources\Config_Legacy and most files will be re-written and saved in .\d7x Resources\Config under the newer d7x config settings format. If a session is already in progress, the contents will remain largely in-tact.
- Reg.Settings.dat – Your d7II specific license file. This is copied to .\d7x Resources\Config\d7II.License.dat (saved as a backup) when the license is converted to d7x format. This file may also be imported for conversion when registering a new copy of d7x, to avoid having to enter in your license details manually.
- d7II.ini – The main d7II configuration file.
- d7II.ini.cfg – A temporary d7x import of the d7II.ini file.
Join us for live tech chat, product questions, support, and technical training right here!
Customer or not, you are welcome to drop in and discuss anything ‘tech’ with us!
d7x Quick Tip – Automating the d7xRDT d7x Quick Tip – Automating the d7xRDT with d7x v19.6.18