DownloadAndInstall

Download and Install

Before downloading can occur, you must have registered and be logged in. Downloads are available almost immediate for the following editions:

• Book
• Educational
• Evaluation

Purchases require more time since our sales need to confirm the purchase order and grant permission to download:

• Personal Edition
• Professional Edition
• Enterprise Edition

After the installers are downloaded, a license will be generated and emailed to your account.

Windows Installation

After downloading an installation file, you may simple run the program. The name is typically something like:

CaseTalk.Edition.Version.exe

This installation will create several folders with files on your computer. By default the folders created are:

C:\Program Files (x86)\BCP\CaseTalk
C:\Users\<username>\AppData\CaseTalk12 
C:\Users\<username>\My Document\CaseTalk 

Java JRE

Some features may require you to install Java or the Java JRE. In the Free Downloads of CaseTalk.com you will find a zipped Java JRE. After having installed CaseTalk, create a subfolder called Java where you can unzip your JRE.

You may check to see if CaseTalk has detected the JRE by navigating to the Help\About\System Info where it'll be listed. If not, please restart CaseTalk.

Windows Azure

CaseTalk can be deployed to Windows Virtual Machines in Azure without any problem. For organizations lacking Windows clients, or due to high security levels don't allow custom software, this is a great opportunity.

All it requires is for you to open an Azure account, open a virtual machine, install Windows and CaseTalk.

Mac OS (32 bit) Installation

Since CaseTalk software requires Windows to run, there's no real support for running it on other operating systems. However if you're willing to try, you may find the following talk useful. It describes the required steps to run Windows Software on OSX.

The original and full documentation on installing and running software using Wine on OSX can be found here: Windows on OSX

It requires the following steps to be executed in a terminal window:

# Install BREW

ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
brew doctor
sudo xcodebuild -license

# Install WINE

brew cask install xquartz
brew install wine

# Install CaseTalk

wine your_downloaded_casetalk_setup_file.exe

# Run CaseTalk

cd ~/.wine/drive_c/Program\ Files/BCP\ Software/CaseTalk/
wine casetalk.exe

Mac OS (64 bit) Installation

Although an experimental 64 bit version of Wine is available through:

brew install --cask wine-stable

The CaseTalk application is still 32 bit. There's currently no way to run it using Wine on 64 bit OSX versions.

Linux Installation

Like above CaseTalk requires Windows to run, but may be run on WINE. The steps required are installing WINE, download the CaseTalk installation file, and have WINE run that.

Portable App

When a full blown installation is not required or unwanted, a more simple installation is available. This may be the case where you want you software to run from a USB Stick to be flexible on different workspaces. Or another more common use, is the deployment from a file server with a network share.

For this to work, you can download the software without installer (if available) which is a regular zip of 7zip file. You can extract the archive to any folder you like, and immediately start the software from the folder. This will be one of the following:

 <Extraction Path>\{app}\CaseTalk.exe
 <Extraction Path>\app\CaseTalk.exe 

If a no-installer is not available for download, you can manually extract the installer yourself. CaseTalk software installs are using InnoSetup. The required files and folders can be extracted using InnoExtract using the following commandline:

 innoextract.exe -e -d <target folder> CaseTalk.Edition.Version.exe 

Removable Media

Removable media is commonly writeable which means CaseTalk will attempt to load and save all configuration files locally. Project files however are a different story and can be saved anywhere. Configuration files are stored in the unarchived folder:

 <Extraction Path>\{userappdata}\ 

Fileshare

Fileshares are typically used to easily deploy new files without the need to install the full package on every workstation. Since CaseTalk 8.15 the Portable App behaviour has been enhanced to support such installations.

Simply extract the non-installer zip file and copy the entire folder structure as is to the fileshare. Make sure all required configuration files are prepared appropriately in "{userappdata}". As soon as CaseTalk Modeler, -Viewer or -Manager is started, they'll pick up any defaults from that folder and store it in the user roaming profile folder for further storage and updates.

If you want even a more specific way of deployment, you can force CaseTalk to run as a portable app by starting it with an additional commandline parameter:

CaseTalk.exe /portable

The main window title will start with: "CaseTalk - Portable"

Or force (aka simulate) it to act as a portable app running from a readonly share:

CaseTalk.exe /portable:shared

The main window title will start with: "CaseTalk - Shared Portable"

Once installed on a fileshare, installing updates while users are actively using the existing installation can be a pain. Folder and File locks might be in place, preventing network administrators to update the software.

The following is a guideline on how to set it up in a way that allows updating without a hassle. In this example the first version is "9.0.0" and later on it'll be updated to "9.1.0":

First installation

1. Create a fileshare "casetalk"
2. Create a subfolder with the version number, for example, "9.0.0"
3. Unzip the available casetalk archive into the "casetalk\9.0.0" folder
4. Create the relevant shortcuts in "casetalk" pointing the executables in "casetalk\9.0.0\..."

Updating the installation

1. Copy the "casetalk\9.0.0" folder to a new folder "casetalk\9.1.0"
2. Unzip the "9.1.0" into the newly created folder
3. Edit the "casetalk\9.0.0\...\lock.example.txt" so users get notified to use "9.1.0" instead
4. Rename this text file to "lock.txt". Users who start the old version will receive a notification instead.
5. Change the previously made shortcuts to point to the new executables in "casetalk\9.1.0\..."