Category : Miscellaneous Language Source Code
Archive   : EDIINS.ZIP
Filename : INSTALL.WRI

1¾«ýrø2
2
3
4
5
6










EDI Install - v1.2
Complete Windows 3.x installation utility by
Eschalon Development Inc.




© Copyright 1992 Robert Salesas - All Rights Reserved.
COPYRIGHT

© Copyright 1992 Robert Salesas. All Rights Reserved. This document may not, in whole or part, be copied, photocopied, translated, or reduced to any electronic medium or machine readable form, without prior consent, in writing, from Robert Salesas. All software described in this manual is © Copyright 1992 Robert Salesas. All rights reserved. The distribution and sale of these products are intended for the use of the original purchaser only. Lawful users of these programs are hereby licensed only to read the programs, from their media into memory of a computer, solely for the purpose of executing the programs on one machine at a time. Duplicating or copying for other than backup purposes, or selling or otherwise distributing these products is a violation of the law and this agreement.


DISCLAIMER

THIS INFORMATION IS PROVIDED "AS IS" WITHOUT REPRESENTATION OR WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, ANY REPRESENTATIONS OR ENDORSEMENTS REGARDING THE USE OF, THE RESULTS OF, OR PERFORMANCE OF THE INFORMATION, ITS APPROPRIATENESS, ACCURACY, RELIABILITY, OR CURRENTNESS. THE ENTIRE RISK AS TO THE USE OF THIS INFORMATION IS ASSUMED BY THE USER. IN NO EVENT WILL ROBERT SALESAS, ESCHALON DEVELOPMENT INC. OR IT'S EMPLOYEES BE LIABLE FOR ANY DAMAGES, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL, RESULTING FROM ANY DEFECT IN THE INFORMATION, EVEN IF ROBERT SALESAS OR ESCHALON DEVELOPMENT INC. HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THIS DISCLAIMER SHALL SUPERSEDE ANY VERBAL OR WRITTEN STATEMENT TO THE CONTRARY. IF YOU DO NOT ACCEPT THESE TERMS YOU MUST CEASE AND DESIST USING THIS PRODUCT.
LICENSE AGREEMENT

Your use of this package indicates your acceptance of the following terms and conditions:

1. Copyright: These programs and the related documentation are copyright. The sole owner is Robert Salesas. You may not use, copy, modify, or transfer the programs, documentation, or any copy except as expressly provided in this agreement.

2. License: You have the non-exclusive right to use any enclosed program only on a single computer at a time. You may load the program into your computers temporary memory (RAM). You may physically transfer the program from one computer to another, provided that the program is used on only one computer at a time. You may not distribute copies of the complete package or the accompanying documentation to others. You may not decompile, disassemble, reverse engineer, modify, or translate the program or the documentation. You may not attempt to unlock or bypass any copy protection utilized with the program. You may distribute the installation program, along with the unpacking program, as long as its intended use is to install an application other then itself, on a users machine. You may not use EDI Install to distribute with, or install "shareware/PD collections', nor may you use it with any product transmitted via a BBS or information service (example: CompuServe, BIX, or GEnie). If you do distribute the installation program, you must not remove its copyright notice or modify its About box, which can be accessed by pressing ALT-I at the main window. All other rights and uses not specifically granted in this license are reserved by Robert Salesas and/or Eschalon Development Inc.

3. Back-up and Transfer: You may make one (1) copy of the program solely for back-up purposes. You must reproduce and include the copyright notice on the back-up copy. You may transfer the product to another party only if the other party agrees to the terms and conditions of this agreement and completes and returns a registration card to Eschalon Development Inc. If you transfer the program you must at the same time transfer the documentation and back-up copy or transfer the documentation and destroy the back-up copy.

4. Terms: This license is effective until terminated. You may terminate it by destroying the program, the documentation and copies thereof. This license will also terminate if you fail to comply with any terms or conditions of this agreement. You agree upon such termination to destroy all copies of the program and of the documentation.
The shareware concept

Shareware is copyrighted software which is distributed by authors through bulletin boards, on-line services, disk vendors, and copies passed among friends. It is commercial software which you are allowed to try before you pay for it. This makes shareware the ultimate in money back guarantees.

Most money back guarantees work like this: you pay for the product and then have some period of time to try it out and see whether or not you like it. If you don't like it or find that it doesn't do that you need, you return it and you get your money back. Some software companies won't even let you try their product because in order to qualify for a refund, the diskette envelope must have an unbroken seal.

With Shareware you get to try it for a reasonable limited time (like 30 days), without spending a penny. You are able to use the software on your own system(s), in your own special work environment, with no sales people looking over your shoulder. If you decide not to continue using it, you throw it away and forget all about it. No paperwork, phone calls, or correspondence to waste your valuable time. If you do continue using it, then - and only then - do you pay for it.

Shareware is a distribution method, not a type of software. Shareware is produced by accomplished programmers, just like retail software. There is good and bad shareware, just as there is good and bad retail software. The primary difference between shareware and retail software is that with shareware you know if it's good or bad before you pay for it.

As a software user, you benefit because you get to use the software to determine whether it meets your needs before you pay for it, and authors benefit because they are able to get their products into your hands without the hundreds of thousands of dollars in expenses it takes to launch a traditional retail software product. There are many programs on the market today
which would never have become available without the shareware marketing method.

The shareware system and the continued availability of quality shareware products depend on your willingness to register and pay for the shareware you use. It's the registration fees you pay
which allow us to support and continue to develop our products. Please show your support for shareware by registering those programs you actually use and by passing them on to others. Shareware is kept alive by your support!
What do I get when I register?

Peace of mind. Seriously, if you like EDI Install and you choose to use it, you must register it. You are not allowed to keep, use, and/or distribute EDI Install with/for your applications unless you register. Once you have registered you will receive the latest version of the program. It will not have the opening delay screen that you get with the unregistered version and it will support compression. As well, you will receive a set of Pack and UnPack utilities to compress your files and distribute with your product.

To register EDI Install, have your VISA card ready and give us a call at (604) 520-1543. You may also send a check or money order for $45 US ($55 Cdn, $58 BC) to:

Eschalon Development Inc.
110-2 Renaissance Square
New Westminster, BC
V3M 6K3 Canada

If you have a previous version of EDI Install (1.00 - 1.12) and you would like to receive a "nag-free" version of 1.2, you may call with your VISA card, or send a check or money order for $8.00 US ($10.00 Cdn).
What is EDI Install and what does it do?

When you have completed your application, you will require a method for your clients to set it up on their hard disk. EDI Install is a program designed especially for that purpose and is easy to use by both you and your customers. EDI Install copies your files from the distribution diskettes to the hard disk in a simple and pleasant manner. It introduces the application, obtains the needed information, copies the files and optionally creates a Program Manager group.


How does EDI Install work?

EDI Install allows you to specify a default directory which the user can modify if necessary. It also displays the minimum amount of free space required and advises the user if the selected drive has insufficient room. Throughout the installation EDI Install displays when a directory is created, a file is copied or a Program Manager group is created. This allows the user to feel comfortable with the installation process and not worry about what the program is doing to the system. The only time intervention is required is when a new disk needs to be inserted.

The installation process can be aborted at any time. EDI Install will report that the installation was not completed and that the program should not be used in this condition. The files that have been created will have to be manually deleted. This is done as a precaution since most users would not like a program to start deleting files off the hard disk.

Once the installation has been properly completed and the setup file specifies a Program Manager group, the user is asked whether or not it should be created. If the Program Manager is not loaded, EDI Install attempts to run it and notifies the user of any errors.


Can I compress my files with EDI Install?*

EDI Install supports optional file compression. Packed files require less space on the disk and generally take less time to copy since the CPU usually decompresses faster than the disk drive can transfer the original file. This allows you to use less disks, especially if you have a lot of large data files, and decreases the installation time. Your customers will also appreciate not having to switch disks as often.

However this has one disadvantage: the files may not be manually copied to the hard disk since they are useless if they are not decompressed. With that in mind, we supply you with a distributable unpacking utility. This program presents the user with a source and destination directory and a list of files to decompress. The user selects on one or more files and chooses UnPack. The selected files are then decompressed and copied to the destination directory, ready to use. Since the program is a Windows application, it is simpler and more convenient to use then the typical DOS command line utilities supplied with most installation programs.

When you compress a file, the name is changed by adding a "$"
(dollar sign) to the extension. The real name is stored in
the file. When you install it or use UnPack, the real name
is extracted and used for the creation of the new file.
You must specify the name of the compressed file (with the $)
in the [FILES] section, not the original name.

*Please make sure you are using version 1.20 (or greater) of ALL THREE PROGRAMS: Install, Pack, & UnPack.
Files on the distribution disks should be placed in such a way as to minimize disk swapping. Note that the setup file for low density disks will not be the same as one for high density disks. Since the high density disks can hold more files, you won't need as many of them. Keep this in mind when planning the setup file.


How do I use EDI Install?

EDI Install is a complete installation program that you can use without modification. It reads a INSTALL.INF file that contains the necessary information describing the layout and of your files on the distribution disks as well as a variety of options and labels. To customize your installation process you simply modify the INSTALL.INF file to suit your application.


Sample INSTALL.INF file

Below is a sample INSTALL.INF (taken from one of our products', WinCLI Pro, distribution disks) file that we will use to explain the format required by EDI Install.


; WinCLI Pro V1.0 - Installation Script
; Eschalon Development Inc.


[Application]
; Application information
Name=WinCLI Pro
Title=WinCLI Pro - Installation
Directory=C:\WINDOWS\WINCLI
PM Group=WinCLI Pro
Free Space=1024
Debug Mode=0


[Disks]
;List of disks needed. Names are used for user request. They
;do not need to be the disk's label.
1=WinCLI Pro Disk #1
2=WinCLI Pro Disk #2


[Directories]
;lists of directories that must be created from the destination
;directory files to be copied are in the same directory structure
;on the floppy (by default)
1=.
2=Extended
3=Program
4=Program\DemoExt.Pas
5=Program\DemoExt.C
6=Program\STUtls
7=Program\UUCode


[Windows Files]
;description, name, (diskette #), (Compressed)
Custom control library=System\BWCC.DLL 1 Y


[Files]
;List of files and where they can be found.
;(description), (name), (directory #), (disk #), (Compressed?)
ReadMe text file=README.TXT 1 1 N

WinCLI Pro=WINCLI.EX$ 1 1 Y
WCLIUtls library=WCLIUTLS.DL$ 1 1 Y
WCLIExts library=WCLIEXTS.DL$ 1 1 Y

WinCLI Pro help=WINCLI.HLP 1 1 N
WinCLI Control Panel help=WCLICTRL.HLP 1 1 N
WC FileApp help=FILEAPP.HLP 1 1 N

DemoExt - DLL=DEMOEXT.DL$ 2 1 Y
STUtls - DLL=STUTLS.DL$ 2 1 Y
UUCode - DLL=UUCODE.DL$ 2 1 Y

API Interface - Help=PROGHELP.EX$ 3 1 Y
API Interface - C Help=WCLIINTC.HLP 3 1 N
API Interface - Pascal Help=WCLIINTP.HLP 3 1 N
API Interface - C=WCLIINT.H 3 1 N
API Interface - Pascal=WCLIINT.PAS 3 1 N

DemoExt - Pascal=DEMOEXT.PAS 4 2 N
DemoExt - C=DEMOEXT.C 5 2 N
DemoExt - Def=DEMOEXT.DEF 5 2 N
STUtls - C=STUTLS.C 6 2 N
STUtls - Def=STUTLS.DEF 6 2 N
TrimFile - C=TRIMFILE.C 6 2 N
UUCode - C=UUCODE.C 7 2 N
UUCode - Def=UUCODE.DEF 7 2 N
UUDecode - C=UUDECODE.C 7 2 N
UUEncode - C=UUENCODE.C 7 2 N

WinCLI Control Panel=WCLICTRL.EX$ 1 1 Y
WC FileApp=FILEAPP.EX$ 1 1 Y
WC SysInfo=SYSINFO.EX$ 1 1 Y
WC Drives=DRIVES.EX$ 1 1 Y
WC ClkSvr=WCCLKSVR.EX$ 1 1 Y
WC ClkSvr - Hook=WCCSHOOK.DL$ 1 1 Y
WC Password=PASSWORD.EX$ 1 1 Y
WC CalcApp=CALCAPP.EX$ 1 1 Y
UnPack Utility=UNPACK.EXE 1 1 N


[PM Group]
;Description, File Name (with relative path), Icon Name (with
;relative path), Icon Index
WinCLI Pro=WINCLI.EXE
WinCLI Control=WCLICTRL.EXE
WC FileApp=FILEAPP.EXE
WC SysInfo=SYSINFO.EXE
WC Drives=DRIVES.EXE
WC ClkSvr=WCCLKSVR.EXE
WC Password=PASSWORD.EXE
WC CalcApp=CALCAPP.EXE
Readme=README.TXT WINCLI.EXE 2


INSTALL.INF sections

The INSTALL.INF file is separated into various sections that control different aspects of the installation process. By modifying them you configure EDI Install for your own application. All the sections except [PM Group] are required for the installation process to be completed correctly.


[Application] Section

The application section describes the basics about your application.

Field Description

Name The name of the application that is to be installed. The name appears in portions of the text in some dialog boxes.
Title The title that should appear in the caption of every dialog box.
Directory The default directory where you want the installation placed. The user may change this by specifying a different path.
PM Group The name of the Program Manager group to create. This field is optional and is only required if you want EDI Install to create a PM group. If you don't want a group created, don't include this label or leave it blank.
Free Space The amount of free kilobytes required for the installation to succeed.
Debug Mode This is a special option that sets a "debug mode" on. When this value equals "1", EDI Install will not actually copy the files, it will just pretend that it is doing it. This is usefull when you have a long INSTALL.INF to debug. Make sure you either omit this field or set it to "0" before shipping, or no files will be installed!!!


[Disks] Section

The disks section lists the names of the disks required for the installation. These names do not have to be the disks label's, just some names with which the user will recognize which disk to insert. Preferably the name will be printed on the disk in such a way that the user can spot it quickly.

Each line consists of an integer number (1 to 32000), an equal sign, and the name of the distribution disk. The numbers are only used internally and need not be consecutive, although it makes more sense to number them like this: 1, 2, 3, 4, 5, etc... than like this: 1, 45, 33, 56, 78, etc...

When EDI Install cannot find a file in the currently inserted disk, it will prompt the user to insert the appropriate disk which is retrieved from the disks section. The user has the option of changing the source diskette each time EDI Install prompts for a new disk.


[Directories] Section

The directories section lists the names of the directories required for the installation. EDI Install will attempt to create all the directories in the section. If a directory already exists, an error is not reported. It will create all the directories in the order in which you list them, so if you need to create a subdirectory that is more than one level deep, make sure that the subdirectories that are closer to the root are listed first. For example, in the sample INSTALL.INF the directories section looks like this:

[Directories]
1=.
2=Extended
3=Program
4=Program\DemoExt.Pas
5=Program\DemoExt.C
6=Program\STUtls
7=Program\UUCode

notice how before it can create directory number 7, Program\UUCode, it needs to create directory number 4, Program, and therefore directory number 4 is listed first.

Each line consists of an integer number (1 to 32000), an equal sign, and the name of the directory. The numbers are only used internally and need not be consecutive, although it makes more sense to number them like this: 1, 2, 3, 4, 5, etc... than like this: 1, 45, 33, 56, 78, etc...

EDI Install uses this information to determine which directory on the distribution diskette contains the file and to which directory, relative to the destination, the file is to be copied. The path is always relative to the source and/or destination, which the user specified.


[Files] Section

The files section lists all the files that EDI Install must copy to the users hard disk. Each line consists of a description, an equal sign, and 4 fields separated by at least one space. The description is displayed in the progress dialog box indicating which file is being copied. It may contain spaces, commas, quotes, and other special characters.

The following 4 fields provide information on the file to be copied. They are each separated by a space.

Field Description

File name The exact name of the file to be copied, as it appears on your disks. Do not specify the path. If the file is compressed, you should specify the name with the "$" extension. EDI Install will automatically create the destination file with the original name.
Directory The directory number that contains the file to be copied. The source path is constructed by combining the source directory, the this directory, and the file name. The same process is used to construct the destination path.
Disk The disk number that contains the file to be copied. EDI Install first attempts to read the file in the current disk, if the file cannot be located, it prompts the user to insert the this disk.
Compression Notifies EDI Install whether or not the file is stored in a packed format. If the value is Y, EDI Install will decompress the file as it is copied. If the value is N, it will simply copy the file without decompressing it. If you attempt to decompress a file that was not compressed using the included Pack utility, an error will be reported. However, no error is reported if a packed file is copied without being decompressed.


[Windows Files] Section

The Windows files section lists all the files that EDI Install must copy to the users Windows directory. This is typically used to install files such as MS Visual Basic's vbrun100.dll or Borland Resource Workshop's bwcc.dll. Each line consists of a description, an equal sign, and 3 fields separated by at least one space. The description is displayed in the progress dialog box indicating which file is being copied. It may contain spaces, commas, quotes, and other special characters.

The following 3 fields provide information on the file to be copied. They are each separated by a space.

Field Description

File name The exact name of the file to be copied, as it appears on your disks. If you specify a path, it will be relative to the Windows directory as the destination, and the disk's root directory as the source. For example:

[Windows Files]
;description, name, (diskette #), (Compressed)
Custom control library=System\BWCC.DL$ 1 Y

would copy the BWCC.DLL located in the System directory of the first diskette and place it in the Windows\System directory on the users hard disk.
If the file is compressed, you should specify the name with the "$" extension. EDI Install will automatically create the destination file with the original name.

Disk The disk number that contains the file to be copied. EDI Install first attempts to read the file in the current disk, if the file cannot be located, it prompts the user to insert the this disk.
Compression Notifies EDI Install whether or not the file is stored in a packed format. If the value is Y, EDI Install will decompress the file as it is copied. If the value is N, it will simply copy the file without decompressing it. If you attempt to decompress a file that was not compressed using the included Pack utility, an error will be reported. However, no error is reported if a packed file is copied without being decompressed.


[PM Group] Section

The pm group section describes the Program Manager group that you want EDI Install to create. This is the only optional section in the INSTALL.INF file. Each line consists of the name of the group to create, an equal sign, the file's path name and parameters (enclosed in quotation marks), the icon file's name and the icon index. If you want to use the relative destination directory as the file's path, you must specify it using the string "%s" (without the quotes). EDI Install will insert the destination directory in the program and icon file specifications, where ever it finds a percent sign followed by an s. For example:

EDI Install=%s\INSTALL.EXE %s\INSTALL.EXE 0

would tell EDI Install to add the destination directory to the program and icon file names when creating the Program Manager item. Don't forget the backslash (\)!

If you wish to specify any parameters along with the file's path name, you must enclose the command line (program name and parameters) in quotation marks. For example:

Manual="WRITE.EXE %s\INSTALL.WRI" WRITE.EXE 0

By specifying a different icon file Program Manager will use an icon in the specified file instead of the program file. The icon index is used to determine which icon (0..?) will be used from the icon file.

The file names should include the destination relative path. For example, to add PROGHELP.EXE located in the PROGRAM directory of the sample INSTALL.INF, you would use PROGRAM\PROGHELP.EXE as the file name.

Examples:

[PM Group]
EDI Install=%s\INSTALL.EXE %s\INSTALL.EXE 0
Manual="WRITE.EXE %s\INSTALL.WRI" WRITE.EXE 0
Order form="NOTEPAD.EXE %s\ORDRFORM.TXT" NOTEPAD.EXE 0
WinCLI Info="WRITE.EXE %s\WINCLI.WRI" WRITE.EXE 0


General information on INSTALL.INF

The INSTALL.INF file is parsed using the Window function ReadPrivateProfileString and is limited to some of its restrictions. Basically, anything you can do in an .INI file you can do in the INSTALL.INF file.

For example, you may not use tabs as Windows treats them as end of line markers (a bug maybe?). You can use as many spaces as you want after the equal sign and they are simply ignored by EDI Install. If you use extra spaces before the equal sign, Windows will interpret them and it can cause problems later on. Any line that starts with a semi-colon is treated as a remark and is ignored by EDI Install. Use it to document your INSTALL.INF file.

This also means that each label before the equal sign must be unique within a section. For example you cannot have something like this:

DemoExt=DEMOEXT.PAS 4 2 N
DemoExt=DEMOEXT.C 5 2 N
DemoExt=DEMOEXT.DEF 5 2 N
STUtls=STUTLS.C 6 2 N
STUtls=STUTLS.DEF 6 2 N
TrimFile=TRIMFILE.C 6 2 N
UUCode=UUCODE.C 7 2 N
UUCode=UUCODE.DEF 7 2 N
UUDecode=UUDECODE.C 7 2 N
UUEncode=UUENCODE.C 7 2 N

Instead you need to add something that will make each label unique, like this:

DemoExt - Pascal=DEMOEXT.PAS 4 2 N
DemoExt - C=DEMOEXT.C 5 2 N
DemoExt - Def=DEMOEXT.DEF 5 2 N
STUtls - C=STUTLS.C 6 2 N
STUtls - Def=STUTLS.DEF 6 2 N
TrimFile - C=TRIMFILE.C 6 2 N
UUCode - C=UUCODE.C 7 2 N
UUCode - Def=UUCODE.DEF 7 2 N
UUDecode - C=UUDECODE.C 7 2 N
UUEncode - C=UUENCODE.C 7 2 N

These are not major limitations, you just need to keep them in mind when creating your INSTALL.INF file.

Finally, you must remember that the INSTALL.INF file is like a program's source code. It needs to be tested and debugged under various conditions. We have used and tested the installation program thoroughly and so far, to the best of our knowledge, there are no major bugs. Still, this only means that the installation program itself is safe, the INSTALL.INF file that you write can still contain bugs. Check that you have properly labelled the disks; that the labels in each section are uniqe; that all files have the correct directories and disks; and finally that you have checked that all compressed files are properly marked. If the user attempts to run a compressed file he might find himself shocked that it doesn't work.


Distributing EDI Install

When you have completed the INSTALL.INF file and you have created your distribution disks, you will need to copy INSTALL.EXE, INSTALL.INF, UNPACK.EXE to the first disk in your package. This disk should be clearly identified so the user can locate it easily. You might also consider writing a message similiar to this, on the label:

INSERT DISK AND RUN INSTALL FROM WINDOWS.

You may not distribute PACK.EXE with your package, only the UNPACK.EXE utility is redistributable. It is highly recommended that you include the unpacking utility since without it your customers will not be able to use the compressed files unless the go through the whole installation process. That is not always desirable.

We suggest you add a README.TXT file to your disk and include something like the following passage, to let customers know about the compressed files:

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

The executable and library files in this package are
compressed. If you don't use the installation program
or you need to copy one of the original files onto
your hard disk, use the UNPACK.EXE file located in the
WinCLI Pro directory or on the diskette.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Both INSTALL.EXE and UNPACK.EXE may be modified using a resource editor, such as Borland's excellent Resource Workshop or WRT. With them you'll be able to change ANY of the strings, the fonts used in the dialogs, even the dialog layouts themselves! The only thing you ARE NOT ALLOWED to change is the special About dialog box. This is a secret dialog box that only appears if you press ALT-I. The user will never see this, so it isn't a problem. Please remember, you MUST NOT remove or change this dialog box. Anything else you may change to suit your needs or style.

Contacting us at Eschalon Development

We will periodically provide bug fixes and upgrades. You may contact us for the latest version. Minor changes and/or bug fixes are free; major revisions will carry an upgrade fee. You always pay for shipping and handling.

For technical assistance, orders, site licenses or information on our other products, you may contact us at:

Eschalon Development Inc.
110-2 Renaissance Square
New Westminster, BC
V3M 6K3 Canada

Telephone/Fax: (604) 520-1543
CompuServe: 76625,1320
Usenet: [email protected]
que€”w¨tùr2
n;
jhfrbw^ÍZßVâRBN²i*

 



 BOw8 sC o›
k¤
g…
c‹
_T[lWgSpO¿K²i*





 ¿ÖvØránªj­fÔbÚ^MZQV\R}MI²



ÐwÔsªo­k<g@cE_K[kW”R–N˜J²

 ˜s!ww!s‘!n“!j•!fJ&bu&]v&[x&Wz&S˜)Ož)K²




 ž)R+wX+s,oL,jN,fO,b·,^¹,Zþ-V.R.M.I²



 .ƒ.wŽ.s”/o˜/k¯/f±/b³/^[0Z]0VÓ;RÙ;Ní;I²



 í;ï;wñ;sÅ<oÏ<k=g/=c1=_{=[=Vj@Rk@NAJ²

 AjAwpAsAoAkìDg
EcE_G[”GW{JSŠJOŒJK²


 ŒJ`LwrLr…LnŠLj#Mf$MbžM^¤MZ‚NVˆNRyPN}PJ²
 }PýPwQsQoÄQkÐQgðQcøQ_sS[…SV˜SRSNqTJ²

 qTçTwUsUoKUkYUg¾Uc¿U_1V[7VW(XS,XO¨XK² ¨X¾XwÀXs€Zo‚Zk?[gl[cÁ\_ð\[£^Wx_S|_Ož_J²


 ž_ _w¢_sÛ_oó_kF`gJ`cÿ`_a[YaW_aSÆbOÈbK² ÈbNdwPds do¢dk*fgxic{i_“iZ•iV—iRjNjJ²

 jjw js"jo,jkèjgüjck_k[kWwkSølO6mK² 
 6m>nw|ns~noãnkôngŒoc›o_µo[ºoW¿pSäpNæpJ²

  æpèpwýrs~noãnkôngŒoc›o_µo[ºoW¿pSäpNæpJ²

€‚X„X†XˆXŠXŒXŽXX’X”XäpNæpJ²

"=ðp
”¨XÖ5ñ"
ðp"
à
p"
ðpñóXõX÷XùX1
X>
5@
5d5"=ðp"
ðpdfXhXuXwXÍXÎXâXäX@XBX6 X8 XRXTX"=ðpTeXgX¾XÖXØX
XX¡X£X„X†XìXîXcX"=ðpc´X¶X·XxX\X]X}X5£X"Ððp"=ðpX’X7X95\X]X}X5£X"
Ððp"Ððp9TXnXƒX•X—5]X}X5£X"ðp"
ðp—kX–5˜5•X—5]X}X5£X"=ðp"Ððp˜s!Xu!Xw!X“!5•!5]X}X5£X"=ðp"Ððp•!Ï#XÑ#X:%X<%XH&XJ&XL&5x&5£X"=ðp"Ððpx&z&X (5"(5<%XH&XJ&XL&5x&5£X"Ððp"=ðp"(®*X°*Xï*5,+5i+5¢+5á+5,5£X"=ðp"ðp,N,X¹,5º,"Ððp"ðp"h
pº,.X.5.5.5Ððp"=ðp"Ððp.!.X”/X–/X˜/X±/5p"=ðp"Ððp±/³/XY0X[05]05±/5p"=ðp"Ððp]0‡0X¥0X§0X©0X¹0XÔ0Xå0X1X#1X81XI1XW1XZ1X\1X"Ððp\1f1X¦1XÌ1Xâ1Xø1Xû1Xý1Xþ1X2XO2X“2X±2X¶2XÂ2X"ÐðpÂ2Í2Xä2Xù2X3X3X35!35þ1X2X"Ä ðp"Ððp!323Xb3X—3X™35›35¤35Ò35452X"Ððp"<Ä ðp4B4XD4Xt4X¤4XÔ4XÖ4X5X65Xf5Xh5X˜5XÈ5Xø5Xú5X"Ððpú5*6XZ6XŠ6Xº6Xê6Xì6X7XL7X|7X¬7XÜ7X 8X<8Xl8X"Ððpl8œ8XÌ8XÎ8XÏ8Xÿ8X/9Xa9X‘9XÁ9Xñ9X!:XQ:X:X„:X"Ððp„:†:X“:XÒ:Xï:X;X%;X=;XU;Xk;Xƒ;X;Xµ;XÕ;X„:X"Ððp
Õ;×;XÙ;Xï;5ï:X;X%;X=;XU;Xk;X"=ðp"Ððpï;ñ;X=X=X=X1=X3=Xy=5U;Xk;X"Ððp"Ððpy={=X=5‘="p`úðp"Ððp"ÐÐðp‘= >XT>X×>X½?X@XlAXnA5pA5"Ððp"p`úðppAAXƒAX¯B5±B5ØC5ÚC5èD5pA5"Ððp"ÐðpèDêDXìDXEXEXG5G5èD5pA5"Ððp"ÐðpG(GX-GX9GXDGX[GXpGX‚GX”GX"Ððp" ðp”G–GX=HX?HX^IX`IXwJXyJX{J5"Ððp"Ððp{JŒJXŽJXñK5óK5^L5wJXyJX{J5"Ððp"Ððp^L`LXtL5vL"p`úðp"Ððp"ÐÐðpvLwLX†MXtNX=OXùPXûPXýPXQ5"Ððp"p`úðpQQXS5S5qS5ùPXûPXýPXQ5"Ððp"ÐðpqSsSX‡S5‰S"p`úðp"Ððp"ÐÐðp‰SŠSXoTXqTX‚T5²T5çT5p"<Ä ðp"p`úðpçTéTX}U5!V5‚T5²T5çT5p"pðp"p`úðp!V#VXìVX¨XXªX5¬X5ÀX5ÂX5"Ððp"p`úðpÂX=[X?[Xl[5ªX5¬X5ÀX5ÂX5"<Ððp"Ððpl[n[X\X\X¿\XÁ\Xð\5ÂX5"<Ððp"Ððpð\ò\XÃ]XÅ]5¿\XÁ\Xð\5ÂX5"ÐÐðp"ÐðpÅ]–^X˜^5£^5¿\XÁ\Xð\5ÂX5"p`úðp"Ððp£^¥^X±^5Þ^5
_5E_5x_5ÂX5"<Ððp"Ððpx_z_X|_X _5
_5E_5x_5ÂX5"=ðp"Ððp _¢_Xu`Xw`X:bXe5ee5NdX"Ððp"ÐðpeeŒeX³eXÚeX
fX(fX*f5>e5ee5NdX"=ðp"Ððp*f–fX˜fXviXxiXziX{i5•i5ee5NdX"=ðp"Ððp•i—iXæjXèjXk5ziX{i5•i5ee5NdX"
ðp"ÐðpkkX]lX_lXölXølX6m58m5nm5NdX"Ððp"Ððpnm¦mXÚmXnXnX|nX~n5½p5NdX"Ððp"Ððp½p¿pXæp5èp"Ððp"=ðp"ÐðpèpÉqXËqX:rX ~1O8 W>
F÷K
S¼aûhKqp Helv Tms Rmn 0CourierlAXnA5pA5"Ððp"p`úðp