FILESTAR.INI
FS/2 creates a default initialization file, FILESTAR.INI, whenever it is started without an existing file. If an existing file is found, the program uses it to restore previously used settings and other parameters. All stored data are saved in this file and no program settings are written to the OS/2 initialization files.
On startup, the program searches the CONFIG.SYS file environment variables for a SET FILESTAR=X:\PATH statement. If one is found, that directory will be used as the *.INI and *.log files directory. If the environment directory is specified but doesn't exist, it will be created. If there is no environment directory specified, the directory of the executable program file is used to store the *.INI and *.log files unless starting FS/2 from a CDROM. If FS/2 is started from a CDROM with no environment directory specified, the *.INI and log files directory is set to the system TMP or TEMP directory.
If FS/2 is started form a directory with write privileges (not a CDROM), it makes a backup copy named FILESTAR.BAK of the FILESTAR.INI file each time the program is closed in the FS/2 directory. Additionally, it copies the FILESTAR.BAK file to \Backup\FILESTAR.BKI on first startup of the day.
If the FILESTAR.INI file becomes corrupted, it will generally be necessary to delete it and let the program generate a new default file or restore a backup copy. To restore a backup copy, copy it to the directory that contains the INI file and then Close FS/2 without saving its configuration using the Close w/o Save menu option from the pulldown System menu. This is necessary to prevent the program from writing corrupted or current data to the restored INI file. Restart FS/2 and the restored INI data will be used to initialize the program.
It is possible to import an older FILESTAR.INI or FILESTAR.BKI file to update the current file with parameters from the imported file. See Importing a FILESTAR.INI file.
FLEXEDIT.INI
FlexEdit also creates and maintains a FLEXEDIT.INI file which contains its startup settings and user preferences. There is no backup of this file after each use. However, as noted below, there is a backup copy of this file, FLEXEDIT.BKI, updated every other day in the \Backup directory.
PATHMARK.INI
A PATHMARK.INI file, which contains stored DirMarks and FTP URLs, is also maintained by FS/2. There is no backup of this file after each use. However, as noted below, there is a backup copy of this file, PATHMARK.BKI, updated every other day in the \Backup directory.
Backup Directory
FS/2 maintains several backup files in the FS/2 Backup subdirectory. It updates all three FS/2 initialization files, FILESTAR.BKI, FLEXEDIT.BKI and PATHMARK.INI, and the current toolbar.bar on first use two days (or later) after last update.
A FS/2 \Backup\Drive_X subdirectory ( where 'X' is the boot drive letter) is created for each bootable partition, if more than one exists, to backup those files unique to each partition. It stores copies of both config.sys and config.bak, the OS2.INI and OS2SYS.INI files and, if a Desktop backup has been made, the SysBak_X.zip desktop backup file and its restore file, DESKREST.CMD file in the Drive_X subdirectory.
Program Data Dumps
The keys Ctrl+Alt+I cause the program to dump program data Information, including program paths used by the program, to fs_info.log. This log will be found in the FS/2 directory.
A more extensive dump of program data, generally useful for debugging program faults, may be activated at any time by Ctrl+Alt+Shift+0. After this dump, the fs_dump.log will be found in the FS/2 directory. This log is generally only useful for analysis of program faults by the vendor. It is automatically generated on program exception faults.