Chapter 3 - System Setup - Revision history

SSprencel at 20:15, 20 April 2011

2011-04-20T20:15:44Z

Show changes

SSprencel at 19:24, 19 March 2010

2010-03-19T19:24:24Z

SSprencel at 18:35, 4 March 2010

2010-03-04T18:35:04Z

SSprencel at 21:40, 1 March 2010

2010-03-01T21:40:24Z

Show changes

192.168.0.10: /* Setting Up Custom Features */

2010-02-17T17:37:02Z

‎Setting Up Custom Features

SSprencel at 21:45, 28 January 2010

2010-01-28T21:45:07Z

SSprencel at 23:05, 27 January 2010

2010-01-27T23:05:49Z

SSprencel at 23:04, 27 January 2010

2010-01-27T23:04:23Z

SSprencel at 23:01, 27 January 2010

2010-01-27T23:01:30Z

SSprencel at 22:58, 27 January 2010

2010-01-27T22:58:23Z

@@ Line 98: / Line 98: @@
 ----
 <p style="color:blue;font-style:italic">
-Note: The multi-user version of halFILE must be installed on every workstation where halFILE will be run to ensure the necessary driver files are copied to each station\’s local Windows folder. The halFILE folder for network systems should be a common network folder accessible by all stations and should be selected as the target folder for the installation of halFILE on ALL stations. DO NOT TAKE THE DEFAULT TARGET FOLDER FOR NETWORK INSTALLATIONS.
+Note: The multi-user version of halFILE must be installed on every workstation where halFILE will be run to ensure the necessary driver files are copied to each station's local Windows folder. The halFILE folder for network systems should be a common network folder accessible by all stations and should be selected as the target folder for the installation of halFILE on ALL stations. DO NOT TAKE THE DEFAULT TARGET FOLDER FOR NETWORK INSTALLATIONS.
 </p>
 ----

@@ Line 108: / Line 108: @@
 [[Image:halFile_Install_-_Step_1.jpg]]
-Step 1: Welcome screen – click Next.
+Step 1: Welcome screen – click Next.<br /><br />
 [[Image:halFile_Install_-_Step_2.jpg]]
-Step 2: The default target folder is shown. If this is not correct, click Change and select the folder where halFILE should be installed. NOTE: For network systems, the target folder should be a shared folder on a network drive accessible to all halFILE users.
+Step 2: The default target folder is shown. If this is not correct, click Change and select the folder where halFILE should be installed. NOTE: For network systems, the target folder should be a shared folder on a network drive accessible to all halFILE users.<br /><br />
 [[Image:halFile_Install_-_Step_3.jpg]]
-In almost all cases choose the typical install.
+In almost all cases choose the typical install.<br /><br />
 [[Image:halFile_Install_-_Step_4_(Typical).jpg]]
-Screen shot of the typical install setup screen.
+Screen shot of the typical install setup screen.<br /><br />
 [[Image:halFile_Install_-_Step_4_(Custom).jpg]]
-Screen shot of the custom install setup screen.
+Screen shot of the custom install setup screen.<br /><br />
 [[Image:halFile_Install_-_Installing.jpg]]
-A screen shot of the halFILE installer during the install process.
+A screen shot of the halFILE installer during the install process.<br /><br />
 [[Image:halFile_Install_-_Finished.jpg]]
-Click the Finished button.
+Click the Finished button.<br />
 </small>

@@ Line 1,002: / Line 1,002: @@
 |18
 |Index verify mismatch (used when Verify logging only option enabled)
 |}

@@ Line 819: / Line 819: @@
 '''Use this cartridge for auto rotation''' – check this box if the cartridge is to be included in an auto rotation scheme. See [[Chapter 6 - Archiving Document Images]] for more information on Archiving documents and using the cartridge rotation feature.
-.	Click the '''Initialize''' button to initialize the cartridge. The system will ask into which drive the cartridge is placed and then initialize the appropriate information to identify the cartridge.
+:4. Click the '''Initialize''' button to initialize the cartridge. The system will ask into which drive the cartridge is placed and then initialize the appropriate information to identify the cartridge.
 ----

@@ Line 1,085: / Line 1,085: @@
 <br />[aaaHFWdd] - <font color="800000">''The section name where 'aaa' is the application id and 'dd' is the document type id.''</font>
-IndexExecute=<nowiki><path and file name of the application to execute></nowiki> - ''The path and file name of the application to run when halFILE saves a record in Index can be defined by the Index module's Tools-Options menu.''</font>
+IndexExecute=<path and file name of the application to execute> - <font color="800000">''The path and file name of the application to run when halFILE saves a record in Index can be defined by the Index module's Tools-Options menu.''</font>
 <br />'''HALFILE.INI Entries for Attached Tables'''

@@ Line 1,077: / Line 1,077: @@
 ''The Section header.''
-ExitApplication=<exit application> - <font color="800000">''The path and file name of the application to run when halFILE exits.''</font>
+ExitApplication=<nowiki><exit application></nowiki> - <font color="800000">''The path and file name of the application to run when halFILE exits.''</font>
 <br />'''Special HALFILE.INI Hooks'''

@@ Line 1,039: / Line 1,039: @@
 The halFILE for Windows section contains the following information:
-<br />[halFILE For Windows] - ''Section header that identifies the section.''
+<br />[halFILE For Windows] - <font color="800000">''Section header that identifies the section.''</font>
-Scan Station=B - ''A unique alphabetic character to identify the scan or import station. This can be set under Configure_Station in the Administrator.''
+Scan Station=B - <font color="800000">''A unique alphabetic character to identify the scan or import station. This can be set under Configure_Station in the Administrator.''</font>
-Name of Application=halFILE for Windows - ''The name of the application shown on the main title bar. This line is automatically entered when the program is run the first time, but it can be changed.''
+Name of Application=halFILE for Windows - <font color="800000">''The name of the application shown on the main title bar. This line is automatically entered when the program is run the first time, but it can be changed.''</font>
-Program Directory=<path to HALFILE.EXE> - ''The directory where halFILE.EXE is loaded. This entry is made for you the first time you run halFILE for Windows.''
+Program Directory=<path to HALFILE.EXE> - <font color="800000">''The directory where halFILE.EXE is loaded. This entry is made for you the first time you run halFILE for Windows.''</font>
-Report Directory=<Crystal Report directory> - ''The location of the Crystal Report program, CRW32.EXE. This can be maintained within halFILE using File-Report. For instance, if the location of the CRW.EXE is C:\CRW, this line should read 'Report Directory=C:\CRW\'. (Include the backslash character at the end of the path name).''
+Report Directory=<Crystal Report directory> - <font color="800000">''The location of the Crystal Report program, CRW32.EXE. This can be maintained within halFILE using File-Report. For instance, if the location of the CRW.EXE is C:\CRW, this line should read 'Report Directory=C:\CRW\'. (Include the backslash character at the end of the path name).''</font>
-MailSendApp=<path and file name of the mail utility> - ''Typically this will be set to halmail.exe in the halFILE program folder.''
+MailSendApp=<path and file name of the mail utility> - <font color="800000">''Typically this will be set to halmail.exe in the halFILE program folder.''</font>
-OCRSendApp=<path and file name of the OCR utility> - ''Typically this will be set to halocr32.exe in the halFILE program folder. Note that this program requires Imaging Professional for Windows.''
+OCRSendApp=<path and file name of the OCR utility> - <font color="800000">''Typically this will be set to halocr32.exe in the halFILE program folder. Note that this program requires Imaging Professional for Windows.''</font>
 <br />'''Current Section'''
@@ Line 1,057: / Line 1,057: @@
 The Current section of halfile.ini contains the following information:
-<br />[Current] - ''Section header for current information.''
+<br />[Current] - <font color="800000">''Section header for current information.''</font>
-Application=<application id> - ''Most recently used Application id. This is the application that was last opened by halFILE on this computer. This is automatically maintained by halFILE.''
+Application=<application id> - <font color="800000">''Most recently used Application id. This is the application that was last opened by halFILE on this computer. This is automatically maintained by halFILE.''</font>
-Document Type=<document id> - ''Most recently used Database id This identifies the image database that was last opened by halFILE on this computer. This is automatically maintained by halFILE.''
+Document Type=<document id> - <font color="800000">''Most recently used Database id This identifies the image database that was last opened by halFILE on this computer. This is automatically maintained by halFILE.''</font>
-Basket=<basket name> - ''Most recently used Basket. This identifies the basket that was last opened on this computer. This is automatically maintained by halFILE.''
+Basket=<basket name> - <font color="800000">''Most recently used Basket. This identifies the basket that was last opened on this computer. This is automatically maintained by halFILE.''</font>
-Duplicates=<true or false> - ''This option is maintained by the Edit-Duplicates option in Index.''
+Duplicates=<true or false> - <font color="800000">''This option is maintained by the Edit-Duplicates option in Index.''</font>
-LastDeliverPacket=<counter> - ''This indicates the last delivery of updated halFILE programs or modules to this station and corresponds to the Delivery Packet indicated in hfdeliver.ini in the halFILE program folder.''
+LastDeliverPacket=<counter> - <font color="800000">''This indicates the last delivery of updated halFILE programs or modules to this station and corresponds to the Delivery Packet indicated in hfdeliver.ini in the halFILE program folder.''</font>
-Todays Date=<true or false> - ''This option is maintained by the Edit-Todays Date option in Index.''
+Todays Date=<true or false> - <font color="800000">''This option is maintained by the Edit-Todays Date option in Index.''</font>
 <br />'''Execute Section'''
@@ Line 1,077: / Line 1,077: @@
 ''The Section header.''
-ExitApplication=<exit application> - ''The path and file name of the application to run when halFILE exits.''
+ExitApplication=<exit application> - <font color="800000">''The path and file name of the application to run when halFILE exits.''</font>
 <br />'''Special HALFILE.INI Hooks'''
@@ Line 1,083: / Line 1,083: @@
 To configure halFILE to execute an external application when you save a record in index, use the IndexExecute option in the database section of halfile.ini as follows:
-<br />[aaaHFWdd] - ''The section name where 'aaa' is the application id and 'dd' is the document type id.''
+<br />[aaaHFWdd] - <font color="800000">''The section name where 'aaa' is the application id and 'dd' is the document type id.''</font>
-IndexExecute=<path and file name of the application to execute> - ''The path and file name of the application to run when halFILE saves a record in Index can be defined by the Index module's Tools-Options menu.''
+IndexExecute=<path and file name of the application to execute> - ''The path and file name of the application to run when halFILE saves a record in Index can be defined by the Index module's Tools-Options menu.''</font>
 <br />'''HALFILE.INI Entries for Attached Tables'''
@@ Line 1,091: / Line 1,091: @@
 A section in HALFILE.INI enables a 'pop-up' search feature fields that are linked to an externally attach table. For instance, if you were linking a Policy Number from your image database to a Policy Number in an external Policy Master Database, these HALFILE.INI entries make the question mark icon appear when the Policy Number field is active. Clicking the question mark icon will display the information from the external table and let you search and select information within the table. The following sample entries placed into HALFILE.INI illustrates how this feature is enabled.
-<br />[aaaHFWdd] - ''This section header identifies the halFILE database. 'aaa' is the application id and 'dd' is the document type. 'TSTHFWIM' would be entered if the application was 'TST' and the database document type identifier was 'IM'. You must include a section for each image database that has a link to an externally attached table.''
+<br />[aaaHFWdd] - <font color="800000">''This section header identifies the halFILE database. 'aaa' is the application id and 'dd' is the document type. 'TSTHFWIM' would be entered if the application was 'TST' and the database document type identifier was 'IM'. You must include a section for each image database that has a link to an externally attached table.''</font>
-ExternalDatabaseName=<file name> - ''The external attach database file name. If the Microsoft Access database \’POLICY.MDB\’ was the attached table, you would enter 'ExternalDatabaseName=POLICY.MDB' on this line.''
+ExternalDatabaseName=<file name> - <font color="800000">''The external attach database file name. If the Microsoft Access database \’POLICY.MDB\’ was the attached table, you would enter 'ExternalDatabaseName=POLICY.MDB' on this line.''</font>
-ExternalDatabasePath=<PATH NAME> - ''The directory where the external database resides. For instance, if the POLICY.MDB file is located in C:\POLICY, then this line would read 'ExternalDatabasePath=C:\POLICY\'. Be sure to include the backslash at the end of the path.''
+ExternalDatabasePath=<PATH NAME> - <font color="800000">''The directory where the external database resides. For instance, if the POLICY.MDB file is located in C:\POLICY, then this line would read 'ExternalDatabasePath=C:\POLICY\'. Be sure to include the backslash at the end of the path.''</font>
-LookupTable=<Microsoft Access Table name> - ''Enter the table name within the external database that is attached. For instance, if the POLICY.MDB database included a table named 'Policy Master' that was being attached, this line would read 'LookupTable=Policy Master'.''
+LookupTable=<Microsoft Access Table name> - <font color="800000">''Enter the table name within the external database that is attached. For instance, if the POLICY.MDB database included a table named 'Policy Master' that was being attached, this line would read 'LookupTable=Policy Master'.''</font>
-LookupString=<field number 1>;<field length 1;<field number 2>;<field length 2>... - ''The lookup string identifies what fields will appear on the pop-up form and how many characters should be displayed from each field. For example, if you wanted to display the first 3 fields from the Policy Master table and those fields were 'Policy Number', 'Last name' and 'First name', you would enter 'LookupString=0;10;1;20;2;15'. The pop-up form would then include ten characters of the Policy Number (field 0 in the table), twenty characters of the Last name (field 1) and fifteen characters of the First name (field 2).''
+LookupString=<field number 1>;<field length 1;<field number 2>;<field length 2>... - <font color="800000">''The lookup string identifies what fields will appear on the pop-up form and how many characters should be displayed from each field. For example, if you wanted to display the first 3 fields from the Policy Master table and those fields were 'Policy Number', 'Last name' and 'First name', you would enter 'LookupString=0;10;1;20;2;15'. The pop-up form would then include ten characters of the Policy Number (field 0 in the table), twenty characters of the Last name (field 1) and fifteen characters of the First name (field 2).''</font>
-LookupTitleBar=Policy Holders - ''This line indicates the message that appears in the title bar of the pop-up box.''
+LookupTitleBar=Policy Holders - <font color="800000">''This line indicates the message that appears in the title bar of the pop-up box.''</font>