After you have read this document close it down using File|Exit to continue the installation.
After installation if you wish to refer to this document it will be located in the Virtual Access directory and called install.txt
Installing Over Current or Old Versions
=======================================
You can install Virtual Access 4.5 over a 2.x or 3.x version of WigWam/PowWow or any previous version of Virtual Access.
Please note the following points:
o Any waiting actions in Review or scheduled actions will cause Virtual Access to fail to connect correctly, install WILL delete these actions.
o This should retain most current settings - but some, in particular the toolbar and window ones will be lost as may signatures.
o See below for issues concerning usernames and icons
o Installing Virtual Access over a previous version of Virtual Access will require a reindex (build) as the thread file structures have been changed. Do not attempt to avoid this automatic reindex.
o This install will actively hunt out unneeded or redundant files in the directory tree you choose to install it to from old versions of Virtual Access, PowWow and WigWam. It will move them to the chosen backup directory ~\VAPath\old_file\, where you can later delete them to recover disk space, there is no way to avoid this. It will not search for files installed elsewhere other than in the directory tree that you install Virtual Access to though.
Moving the MessageBase
======================
If you want to move your current installation of WigWam/PowWow/Virtual Access then you should do the following before this install:
1) Move the entire directory structure from <old location> to the <new location>. (using File Manager or Explorer to ensure that the system keeps track of things or an xcopy with the /e/s switches to move over all the directories even the empty ones)
2) Edit all the path statements in <new location>\ashmount.ini to reflect the new location.
-- Or --
delete <new location>\ashmount.ini and let the install recreate it. You will have to put in your comms details again (this is the recommended method)
3) edit the <username>.ini files to reflect the current location
-- Or --
delete <new location>\<username>.ini and let the install recreate it. This is the recommended method)
Existing Local Users & Stuff
============================
The install routine will create 3 users, but will only create icons for one user.
User 1 : UserName = admin : Password = admin
This user has full rights to do anything (can connect create users, make topics closed etc.).
The Virtual Access icon created by install (in the program manager group and on the desktop and start menu and folder) are set to this username. See below for how to customise the username and password to suit your existing user files.
User 2 : UserName = default : Password = admin
This user has no administrator rights in a multiuser version of Virtual Access. In the single user version of Virtual Access this user has full rights. This user is installed as a backup user and as a template for creating new users from.
User 3 : UserName = sched : Password = sched
This user is required for scheduled connections. Unless you have this user installed you cannot do scheduled connects. You cannot use this user to do anything other than scheduled connects.
These usernames created may not match your existing usernames.
If you start Virtual Access as one of these new users, you may find all your messages marked as unread and all your screen preferences lost.
New Facilities & Recent Changes
===============================
Please consult the upgrade.rtf and readme.rtf files for this information - these are located in the Virtual Access directory and icons should be created for them in the Virtual Access group.
There is also some information located in the initial messages included in Virtual Access
3.xx PlusPack Users
===================
You will need to download a new version of the Pluspack as the executables in there have been changed in order to tie up with changes in Virtual Access 4.xx.
Other Upgrade Issues
====================
If your VA UserName is not admin or default then you will have loads of old entries in your <username>.ini file (this can slow VA start-up/shutdown a lot). It's best to delete the <username>.ini file, VA will recreate it - you will lose the screen preferences mostly. But to get rid of the major bits that have changed delete all the [window XXXXXX] entries as they are unneeded and have been replaced with a [windows] section
We hope that these notes help. If you have any questions about upgrade issues that are not addressed here then we suggest that you post to our newsgroup/conference/forum where we will be happy to help you resolve these matters.
Files that are replaced or backed up in the installation process will be placed in the ~\VAPath\old_file\ directory - you can delete the contents of this after the install to recover some disk space
Regards,
The Virtual Access Team
Select File, Print to print this out for later reference
Select File, Exit to close this down and continue the installation.
