Release Notes: MultiView 2000 OEM Sample Release Version: 6.4.00 Release Date: March 11, 2005 ================================================================================= Please review this document carefully before installing or using any of the files discussed in this document. These notes contain last-minute information that may affect your use of the files. ================================================================================ Contents 1.0 Introduction 2.0 Set Up 3.0 Technical Support ================================================================================ 1.0 Introduction MultiView 2000 is easy to customize for OEM purposes and does not require any third party development tools. To help you understand the customization process, two tools are provided on the MultiView Software Family CD: * An OEM guide in PDF format (\mvw2000\samples\oem\guide\oemgde.pdf). * A sample OEM set-up program written with InstallShield 5 Professional (\mvvw2000\samples\oem\setup). ================================================================================ 2.0 Set Up As part of the OEM facilities of the MultiView 2000 set up program an OEM set up can be called (see OEM guide for details). Contained in the samples\oem\setup directory of MultiView 2000 is a sample InstallShield 5 set up which will copy MultiView 2000 configuration files (.zz? files) and create Windows desktop shortcuts. To use the sample OEM set up, copy the MultiView 2000 directory from CD to your hard disk. In the copied MultiView 2000 directory create a sub-directory called oem. Copy the OEM set-up files from the CD to the directory created, including the Data subdirectory. The sample OEM set-up is controlled by a file called filelst.ini. The .ini file is divided into the following sections: [Configurations] This section contains a high level list of configurations to be copied. All files are copied to a "Terminal Sessions" sub-directory of the MultiView 2000 installation directory. Each line should contain the name of a configuration to copy and the name of the section in the .ini file that defines the configuration. e.g., MyEmail=Email This example directs the OEM set up to copy the files in the section Email of the filelst.ini [User Defined Configuration Section] These sections contain settings to control what files are copied and if a shortcut on the users desktop should be created. Entries in this section are as follows: ShortcutTitle= The text to be displayed by the shortcut on the users desktop; Note: if this value is omitted then no shortcut will be created. On Windows NT4 the shortcuts are created in the "All Users" desktop so that all users of the machine will have the shortcut. ShortcutIcon= The file name of the icon to use for the shortcut. If none is specified then the default icon for the configuration file will be used. ConfigFile= The file name of the configuration file that is to be the target of the shortcut. This must be a .zzt or .zzf file. AuxFiles= A comma separated list of file names of any additional files that need to be copied, e.g. script files (.zzs) or icon files (.ico). Note that the list should contain no spaces between file names. All files are expected to be in a Data sub-directory of the sample OEM set-up. The following filelst.ini is shipped with the sample OEM set-up. [Configurations] ;only on config. to copy contained in the email section ;this will create a shortcut to a .zzt file than will ;connect to a remote Unix host and run an email application Email=Email [Email] ShortcutTitle=Email Application ;create a shortcut ShortcutIcon=email.ico ;use the icon file ;"Program Files\MultiView\MuliView 2000\Icons\email.ico" ;for the shortcut. ConfigFile=email.zzt ;use the config. file ;"Program Files\MultiView\MuliView 2000\Terminal Sessions\email.zzt" ;for the shortcut target AuxFiles=email.zzs,email.ico ;also copy these extra files to the ;"Program Files\MultiView\MuliView 2000\Terminal Sessions" ;directory ================================================================================ 3.0 Technical Support For prompt and effective service, please be sure to include your company name, address, any applicable phone (or fax) numbers, name and version number of the product for which you need support. The following technical support options are available: 3.1 North America, South America, Asia and Pacific Rim * E-mail: support@futuresoft.com * Telephone: Monday through Friday between 08:00 and 17:00 Central Standard Time (CST) 1.281.588.6868 * FAX: 1.281.496.1090 * Ground Mail: Technical Support Services 12012 Wickchester Lane, Suite 600 Houston, Texas 77079-1222 3.2 United Kingdom, Europe, Africa and Middle East * E-mail: support@futuresoftuk.com * Telephone: Monday through Friday between 09:00 and 17:30 Greenwich Mean Time (GMT) +44 (0) 1260 292219 * FAX: +44 (0) 1260 292224 * Ground Mail: Technical Support Services Shepherds Mill, Worrall Street Congleton, Cheshire CW12 1DT UK 3.3 Send files via FTP to ftp.futuresoft.com. ================================================================================ Copyright 2005 FutureSoft, Inc. readme.txt MV2000Smpl_oem March 11, 2005 sac