Meeting Schedule Assistant

Vista Compatibility

Beginning with version 3.03, attempts have been made to make Meeting Schedule Assistant more compatible with the new �Vista� Operating System by Microsoft. Outlined below are the changes made to the program and these may or may not affect you if you are an existing Meeting Schedule Assistant user.


Meeting Schedule Assistant 3.04 (November 2007)

Administrator privileges no longer required

This has been achieved by writing our own mechanism to export and import the registry data.  This means that we no longer require the use of REGEDIT.  The side effect of this is that legacy ZIP files will not restore fully.  You will be warned if this is the case and if so, you must manually import the registry file by right-clicking it.  All new backups made with version 3.04 will work correctly.


Meeting Schedule Assistant 3.03 (October 2007)

Location of data files

The location of the internal data files created and maintained (ie: *.BIN) have been moved from {programfiles} folder to the {userappdata} folder.  This is more inline with the way that Vista expects program data files to be stored.  If you upgrade from 3.01 or below, the installer will try to copy your existing data files to the new location.  However, under certain circumstances this might fail, so you are encouraged to backup your settings first from within Meeting Schedule Assistant so that you can restore them if required after the upgrade has been installed.

Vista awareness

The Meeting Schedule Assistant executable is now Vista aware.  For now, Meeting Schedule Assistant tells Vista that it wants to be elevated to have Administrator rights.  The primary reason for this requirement is because of the way the backup / restore feature works.  I will look at changing how this functions in a future release so that we can reduce the need for running Meeting Schedule Assistant with these rights.  What this means is that when you run Meeting Schedule Assistant in Vista, and the UAC (User Access Control) is switched on (see control panel) you will be prompted to sign in with the administrator credentials.