Process Lasso INI File Backup...

Started by hanemach_gt, April 27, 2013, 09:45:17 AM

Previous topic - Next topic


While reading that thread, I thought it would be quite easily doable to write a simple script that would be capable of copying both Process Lasso configuration files, so I have written a script allowing to do backups of these files.

The zip file contains four files: pl_ini_backup.cmd, pl_ini_backup.ini, call_config_dirs.cmd and restore_ini_backup.cmd. The second file must exist in the same folder as the first one, since the script gets the destination path for backups from its own INI file.
The content of pl_ini_backup.ini defaults to:

;don't append "\" to the end of the path

You can open that INI file and set your own customized path, that's what that facility was made for.

The script call_config_dirs.cmd does nothing except retrieving INI paths from the Windows Registry and opening both the folders containing Process Lasso configuration: global and user.

Use restore_ini_backup.cmd to easily restore backups made using pl_ini_backup.cmd. Launch restore_ini_backup.cmd. You will be asked if you want to continue. Continuing results in backup directory launched so you can drag one of your files onto the script's window. This script also requires pl_ini_backup.ini.

The script has been tested/working in Windows 7.

To grab the zip file, go to my Google Drive >>,
click the file and then Download.

I hope someone will find this helpful.

UPDATE (6-Jan-2014): Fix call_config_dirs.cmd script falling into an infinite loop as it couldn't get ConfigFile value from the local machine hive. Updated to handle the case. Main backup scripts weren't affected by this bug (both of them already handle lack of registry values).
<img src="[url=""][/url]"/>


I find this MS Power Toy/Tool makes backing up common ini files simple and easy. A little configuration is needed at first, but once that is done all your files can be backed up quickly with the push of a button. :)


In case of this script you also needn't configure much (you don't have to change the path), just unpack and launch the script.  :)  SyncToy is a good point anyway, particularly useful for more than one file.
<img src="[url=""][/url]"/>


Updated the package to contain 2 additional scripts that beta-testers might find useful.
<img src="[url=""][/url]"/>

Jeremy Collake

Software Engineer. Bitsum LLC.