Level-2 Service Training Workbook - v2.
Level-2 Service Training Workbook v2.
Table of Contents Introduction Unit 1: DocSTAR SCSI Overview ....................................................................................... 1 Section 1: SCSI Configuration Overview ........................................................................... 2 Section 2: SCSI Configuration Lab .................................................................................... 6 Section 3: Internal Cleaning of Optical Drive Laser Lens ..................................................
Introduction The DocSTAR Level-2 Service Training Workbook and Curriculum are designed for DocSTAR Level-1 certified service engineers who will be supporting the DocSTAR line of Electronic Imaging Systems from BitWise Designs, Inc.
Unit 1: DocSTAR SCSI Overview ? This unit is designed as a thorough review of SCSI configuration and instruction on how to clean the laser lens in an optical drive. Upon completion of this unit you should be able to: ? Identify & configure SCSI host adapters and peripheral devices. Such as: ? Adaptec 2910C/2930/2940 SCSI Host Adapter Cards ? SCSI High-Speed Document Scanners ? SCSI 3½” 640MB MO Disk Drive ? SCSI 5¼” 2.6/5.2GB MO Disk Drive ? SCSI 5¼” 4.
Section 1: SCSI Configuration Overview ? This section will cover the basic theory of SCSI configuration and it’s application in DocSTAR host systems. The Small Computer System Interface (SCSI) has been around for over 25 years. It was developed to provide the capability of attaching many devices and communicating at high speed. For the most part, SCSI devices communicate much faster than their IDE/EIDE (internal) or parallel (external) counterparts.
device and a separate logical unit number for the CD-ROM device. All DocSTAR SCSI Devices are SCSI 2 devices, except for the External RAID5 Tower, which is SCSI 3. Figure 1.2: DocSTAR External SCSI Devices Setting SCSI Ids for DocSTAR devices or SCSI Host Adapters is accomplished by using one of the following methods: Figure 1.3: Methods of Setting SCSI Ids In Figure 1.3, specifying the desired SCSI Id in decimal form sets the rotary switch settings and software settings for SCSI Id.
*Note: Whenever a change is made to the SCSI Bus, all SCSI devices as well as the CPU must be re-booted. All SCSI devices must be turned on before the CPU is powered on. The SCSI cable, which transfers the data from the device to the host adapter or another device, is specified to be a certain length and quality depending on the SCSI classification. When dealing with maximum cable length specifications, the specification is the total cable length from the host adapter to the last physical device.
This is a passive terminator circuit: Figure 1.7: Passive Terminator Circuit This is an active terminator circuit: Figure 1.8: Active Terminator Circuit The final component that must be in place for the SCSI devices to communicate with the PC is the Advanced SCSI Programming Interface (ASPI) Software. The ASPI software, also known as the ASPI Layer, is the software that is responsible for all communications between the PC operating system and the SCSI host adapter.
Section 2: SCSI Configuration Lab ? This section is intended to provide hands-on experience in configuring SCSI devices. Activity: Record the SCSI Ids of your scanner and DVD-RAM/MO drive. Change the SCSI Id of your scanner to Id 4 and your DVD-RAM/MO drive to Id 5, confirm that they have changed properly, and then return them back to their original settings.
Section 3: Internal Cleaning of Optical Drive Laser Lens ? This section will cover the diagnosis and cleaning of an optical drive laser lens. DocSTAR systems have been equipped with an optical drive for the storage of documents since their inception. These optical drives include: ? ? ? ? ? Panasonic 650MB 5¼” PD Disk Drive Fujitsu/Maxoptix 640MB 3½” MO Disk Drive Maxoptix 2.6GB T4/T5/T5-STAR 5¼” MO Disk Drive Maxoptix 5.2GB T6 5¼” MO Disk Drive Panasonic 4.
Section 4: Optical Drive Laser Lens Cleaning Lab ? This section is intended to provide hands-on experience in the cleaning of an optical drive laser lens. Activity: The instructor will lead you through the process of cleaning the laser lens.
Unit 2: DocSTAR v2.3x Database & Index Overview ? This unit is designed to present a detailed description of the DocSTAR filing and retrieving system: the DocSTAR Database and Full-Text Index. Upon completion of this unit you should be able to: ? Identify & explain the function of the files and directories associated with the DocSTAR Database and Full-Text Index. Such as: ? ? ? ? Identify & explain the function of the tables and fields found in the DocSTAR Database.
Section 1: DocSTAR v2.3x Database and Index Design ? This section will cover the design & function of the DocSTAR filing and retrieving system: The DocSTAR Database and Full-Text Index. To understand the DocSTAR system of filing and retrieving, it is important to define filing and retrieving. In a DocSTAR system filing is the process of storing unique information about a document in such a way that it will facilitate quick retrieval of the same document at a later date.
Although we can open Document.MDB with Microsoft Access, each DocSTAR system comes with a utility program called Data Manager which allows us to open the DocSTAR database for viewing or editing. Data Manager is located in the C:\DOCSTAR\TECHDISK directory. The DocSTAR database is comprised of 19 tables, which have relationships with one another. The design of the database can be seen in Figure 2.2. TABLE FIELDS Figure 2.2: DocSTAR v2.
Queue/Temporary Tables (Tables which act as a queue or provide temporary data) Complete Acts as a queue for the deferred archiving of documents * . Dirtytags Acts as a queue for archived documents, which require updates to the title, keywords, security class, and page rotation tags. Inbox Acts as a queue for documents to be processed* which were scanned as ‘file later’ or rejected by automatic filing due to the maximum uncertainty rate. Index Acts as a queue for the deferred filing of documents * .
Hierarchy table PARENTID CHILDID Miscdata table RECORDID RECORDTYPE DATE DATA Origin table ID NAME Page table DOCID PAGENUM PAGEID TEXTSIZE TIFF TEXT ROTATION TOTALLINES ANTSIZE IMAGETYPE FILEID Phone table ID NAME NUMBER The DOCID of a parent folder, DOCID 0 is the root folder. Sub folders off of the root will have a ParentID of 0. The DOCID of this sub folder or document. A unique sequential number that identifies each version history or event log entry.
Rights table ID UID CLASSID RIGHT0 RIGHT1 RIGHT2 RIGHT3 RIGHT4 Stations table STATIONID MACHINENAME LASTLOGON LASTLOGOFF USERID LOGGEDIN HARDWAREID REMOTE FILE SCAN VERSION LASTCHECKED VIEW APPNAME User table ID NAME FULLNAME CLASSES SUSPENDED PASSWORD FOLDER Page 14 A unique sequential number that identifies each DocSTAR rights table entry. The user ID that this entry applies to. The security classification, for this user, that this entry applies to.
LASTLOGON Volume table VOLUMEID VOLUMELABEL CREATED MODIFIED ACCESSED DELETED SOURCE The last time this user logged on. A unique sequential number that identifies each archive disk volume. The volume label of this volume. The date that the DocSTAR began archiving to this volume. The date that this volume was last modified. The date that this volume was last accessed. Indicates whether or not this volume has been deleted.
X1 The horizontal coordinates of the beginning of the uncertainty on the scanned image file. (Used to draw the highlight box on the image). The vertical coordinates of the beginning of the uncertainty on the scanned image file. (Used to draw the highlight box on the image). The horizontal coordinates of the end of the uncertainty on the scanned image file. (Used to draw the highlight box on the image). The vertical coordinates of the end of the uncertainty on the scanned image file.
Normally, it is not necessary to modify this file in any way. However, if a valid word is not being indexed because it is part of the Noise word file, you may use a standard text editor to remove any words from the file so that they may be indexed. Once this is done, any filed documents that contain this word will have to be retrieved, have a character added to the title, have that same character deleted, have the changes saved, and have the document processed again.
Section 2: DocSTAR v2.3x Database and Index Utilities ? This section will cover the design & function of the DocSTAR Database and Full-Text Index utilities. What utilities are available for the Database and Full-Text Index? *As is the case with all DocSTAR repairs, please be cautious in dealing with the Database and Full Text Index. ALWAYS confirm that you have a current backup copy of the Database and Full-Text Index.
Figure 2.5: Using Datamgr.exe to Open the DocSTAR database When the database has been opened there will be a list of tables, as seen in the database design section, which can be opened and edited. See Figure 2.6. Figure 2.6: Using Datamgr.exe to Open tables in the DocSTAR database Once a table has been opened you will see fields, which can be edited manually. It may be necessary to expand the window to allow viewing of all the fields.
Figure 2.7: Using Datamgr.exe to Open the Document table DBCHECK.EXE Dbcheck.exe performs database consistency checks and reports the results to a log file. It checks for invalid conditions, which may occur due to corruption or incomplete processes (e.g. hard disk failures, scanner jams, power problems, etc.). The results are reported to the log file specified in the ‘Report Options’ section of the testing window. See Appendix C for a sample log file. Figure 2.8: DBcheck.
DBMATCH.EXE Dbmatch.exe is rarely used, since problems in the database are more likely to have occurred in the data rather than the structure. Usage of Dbmatch.exe requires that you have a known good (sample) database in the C:\WINDOWS\TEMP directory to compare against your suspect (target) database. Once the sample is in place, the test can be run and any required repairs will be made automatically. Figure 2.9: DBmatch.exe Testing Window DOCUTIL.EXE Docutil.
Initialize Main Index Index Pending Docs Index Documents DIR.TXT file first. This file is a directory and file listing of every disk volume that contains DocSTAR documents. Resets only the Full-Text Index to its default state: blank. This option is used only if the Full-Text Index is missing or corrupted. Indexes any documents, which have not yet been indexed. Indexes any documents that meet the SQL statement parameters. With this command you may index part or all of the documents in a DocSTAR system.
How is an SQL statement structured? As seen in the prior example, a well-structured SQL statement can be a very powerful timesaving tool. On the other hand, a poorly structured SQL statement can be a very destructive tool. It is recommended that you test your SQL syntax by first creating a SELECT SQL to see if it will run as expected, it is also useful in determining how many records will be affected by your proposed SQL statement.
Wildcard characters * ? # Special Values TRUE/FALSE NULL Represents any number of characters Represents any single character Represents any single digit Represents that the condition is true/false (yes/no, checked/unchecked) Represents no data present (at times, an invalid condition) -1/0, There are certain field names that may require brackets ([ ]) around them when using them in an SQL statement.
AND Created > #09/10/1999# AND Created < #01/01/2000# And the created date of the document is greater than 9/10/1999 And the created date of the document is less than 1/1/2000 As seen from the example, the common construction of an SQL statement is as follows: [SELECT or UPDATE] FROM [TABLE] [ACTION] based on [CONDITION 1] AND/OR [CONDITION 2] AND/OR [CONDITION 3] . . . Etc. For a list of some commonly used SQL statements, see Appendix D.
Section 3: DocSTAR v2.3x Database & Index Utilities Lab ? This section is intended to provide hands-on experience in using the Database and Index utilities. Activity: Run Concheck.exe to a remote drive letter. Run DBCheck.exe and review the Dbcheck.log file for potential errors. Using Datamgr.exe open the Document Table in Design view and delete the Index for DOCID. Run DocSTAR and see the resulting error. Now, using DBMatch.exe, correct this problem. Run Docutil.
Unit 3: DocSTAR Networking Overview ? This unit is designed to present a detailed description of the basic configuration and performance considerations involved with networking a Host DocSTAR system and DocSTAR View/File stations. Upon completion of this unit you should be able to: ? Identify & explain different network topologies and configurations. Such as: ? ? ? ? ? Identify & explain the function of network hardware and cabling.
Section 1: Network Topologies ? This section will cover different configurations and topologies of network design. A Network is a group of two or more PC’s and peripherals sharing each other’s resources over a transmission/reception media such as: network cabling, phone lines, and wireless communications. There are two distinct configurations that describe a network in geographical terms. The first is a LAN or Local Area Network.
If termination is not in place, much like SCSI, there will be signal bounce and loss of network communication integrity. A break in the line at any point will bring the network down. One of the most common methods of transmitting data in a bus network is Ethernet. Ethernet is called a contention method of communication because it employs CSMA/CD technology. CSMA/CD stands for Carrier-Sense Multiple Access with Collision Detection.
In the STAR topology, computers are connected to a central point, called a hub. A hub is a device that connects multiple computers and communicates messages from one computer to the all of the computers on the network. In the star topology, if there is a break in one of the lines, only that computer is unable to send and receive data on the network. The star topology is the most common configuration for small networks. One of the most common methods of transmitting data in a star network is ethernet.
Section 2: Network Hubs, Cabling, & NICs ? This section will cover networking hardware. Once you have decided on a network topology you must now choose the network hardware to implement it. Some of the choices to be made are what type of hub to use or should a switch be used instead, what type of cabling to use, and what network interface cards to use. Hubs and Switches A network hub is used only in star topology based networks or hybrid star networks such as a star bus or star ring.
Currently, ethernet hubs can communicate in two speeds 10Mbps and 100Mbps (Fast Ethernet). You can purchase a 10Mbps hub, a 100Mbps hub, or a hub that can communicate at either speed automatically. What is a Switch and when should I use one instead of a Hub? A Switch is a device much like a hub, which connects multiple computers to a central point and regenerates the signal.
most commonly used type of twisted-pair cable. In fact, it is the most popular type of LAN cabling in use today. The difference between STP and UTP is in the transmission distances. Since STP is shielded it can carry a signal for longer distances. UTP cable can carry a signal for 100 meters (328 feet). There are different categories of UTP cable: Category 1 or Cat 1 – Traditional phone cable that can carry voice but not data. Category 2 or Cat 2 – Certifies UTP cable for data transmission rates up to 4Mbps.
Fiber-optic Cable Fiber-optic cable uses light pulses rather than electrical signals to communicate data. Fiber-optic cable is made up of a very thin cylinder of glass, called the core, surrounded by a concentric layer of glass, called the cladding. The fibers are sometimes made of plastic, but plastic cannot carry signals as far as glass. Fiber-optic cable is uni-directional so a pair of cables is necessary, one to send and one to receive.
Network Cable Naming Conventions Based on the information presented earlier in this section, the following naming convention for network cabling should be readily apparent. UTP network cabling is sometimes referred to as 10BaseT or 100BaseT. This naming convention describes the maximum transmission speed (in Mbps), the method of transmission, and the physical cable design.
Section 3: Network Clients, Protocols, Sharing, & Drive Mapping ? This section will cover networking software. Now that the networking hardware has been decided upon and installed, you have to decide on what Client Software and Protocol you will be using. The Client Software is most often a decision between having Novell Networking Clients and/or Microsoft Networking Clients with the capability of communicating with each other.
Figure 3.8 Network Control Panel in Windows 9x The Network Control Panel displays current settings for Client Software, Network Interface Cards, Network Protocols, and Network Services. In addition, you may Add, Remove or change the Properties of any of the network components listed above. After you have added all the network components necessary, you will have to define some of the parameters for Identification, Access Control, Client Software, Network Protocols, and File and Printer Sharing Service.
The computer name must be unique on the network, such as ‘DocSTAR’. The workgroup should be set to what their current workgroup setting is. The Access Control Tab should be set to Share Level Access. See Figure 3.10. The workgroup name should not be the same as any computer name on the network. This may cause conflicts. Figure 3.
The default settings for the Network Interface Card Properties are usually adequate unless problems are encountered. See Figure 3.12. Figure 3.12 Intel(R) PRO/100+ Management Adapter Properties The default settings for the NetBEUI Network Protocol Properties are also adequate unless problems are encountered. See Figure 3.13. Figure 3.
Figure 3.14 IPX/SPX-compatible Protocol Properties If you will be using the TCP/IP Network Protocol you will need to obtain some additional information from the Network Administrator. The most basic component of using TCP/IP is the IP Address. An IP Address identifies the exact location, on the network, at which messages to this computer can be sent and received successfully. This is the reason why millions of PCs on the internet can communicate with each other.
on the client workstations. Do not make adjustments to client workstations without the permission of the Network Administrator. Some terms to know in dealing with these features are: ? Gateway: A gateway is a connection or interchange point for two networks that would otherwise be incompatible. For example, a local area network (LAN) may need a gateway to connect it to a wide area network (WAN) or to the Internet.
Figure 3.16 File and Printer Sharing for Microsoft Networks Properties To ensure that you are indeed able to share files and printers out on the network, click the ‘File and Printer Sharing...’ button on the Network Control Panel, Configuration Tab. See Figure 3.17. The Primary Network Logon should be ‘Client for Microsoft Networks’. Figure 3.
Figure 3.18 File and Printer Sharing Options Creating Shares and Drive Mapping Once your network setup is complete, you will have to actually create a Share and create Drive Mappings. You can share an entire drive letter, sub folder, and/or a printer. We will be dealing with sharing an entire drive letter, since this is what is required when setting up a DocSTAR on the network.
Figure 3.20 My Computer, Hard Drive Shared Now that there is a share on the network, go to the DocSTAR client PC and double-click Network Neighborhood. You should be able to see the DocSTAR on the network as in Figure 3.21. You can test this on the DocSTAR Host System First. Figure 3.21 Network Neighborhood Double-click on DocSTAR, and you should see the share name that you assigned to the DocSTAR Host System’s hard drive as in Figure 3.22. Figure 3.
From the DocSTAR client PC, you can right-click on the share name of the hard drive and select ‘Map Network Drive.’ You will see a window displaying the first available drive letter for mapping, select the ‘Reconnect at Logon’ check box. See Figure 3.23. Figure 3.
Section 4: Networking DocSTAR Host Systems & Client Stations ? This section will cover networking DocSTAR Host Systems & Client stations. To be able to have client stations access the DocSTAR Host System, you must first follow the procedures outlined in sections 1-3 of this workbook. The next step is programming the DocSTAR Host Hardware Licensing Key with the type and number of licenses purchased beforehand.
Now that the network hardware, software, sharing, drive mapping, and DocSTAR Licensing have been addressed, install the DocSTAR software on the client station as a View or View/File, whichever is appropriate. See Figure 3.26. Figure 3.27 DocSTAR Setup Window Once the DocSTAR software installation is complete, double-check to see what drive letter is mapped to the DocSTAR Host System hard drive and record it. Next, run DocAdmin and click the ‘Network Mappings’ button.
Figure 3.
Section 5: Network Performance Considerations ? This section will cover special considerations affecting network performance. Whenever a DocSTAR system is considered for being added into a pre-existing network, some basic steps should be followed to ensure a successful installation. These steps are: 1. Evaluate the customer’s DocSTAR networking needs. 2.
The Network This area requires planning and cooperation. When estimating the impact of DocSTAR traffic on a network you must first know what the current network utilization is. You can find this out by asking the Network Administrator. If there is no network administrator you may check this on your own using network ‘sniffing’ software and/or monitoring the utilization LEDs on the network hub or switch. You may also recommend a network consultant.
Installing a dedicated PC workstation as a Fax Server possibly running WinFax Pro could off-load a high processing load from the DocSTAR. Remember, DocSTAR is an Imaging Server that is capable of sending and receiving low volumes of faxes. The exact amount depends on how heavily the DocSTAR System is used for its primary function: Imaging.
Section 6: Networking Lab ? This section is intended to provide hands-on experience in networking and attaching DocSTAR to a network. Activity: Identify the network hardware present in the classroom. Setup a DocSTAR Host and client stations on the network using the supplied Network hardware.
Unit 4: DocSTAR Software Overview ? This unit is designed as a review of DocSTAR Software. Upon completion of this unit you should thoroughly understand the operation of software such as: ? DocSTAR Software ? DocSTAR v2.3x Host Software ? DocSTAR v2.3x View/File Software ? DocSTAR v2.
Section 1: DocSTAR Software ? This section will cover basic information about DocSTAR v2.3x Software DocSTAR v2.3x Host Software DocSTAR Host Software is responsible for most of what happens in a DocSTAR environment. It is the central collection and distribution point of the Database, Full-Text Index, Image files, and their associated Text and Annotation files (where applicable). It handles inbound scanning, faxing, and importing as well as outbound retrieving, printing, faxing, and exporting.
However, some of the settings that can or need to be modified are not all accessible in the DocAdmin Window. To see some of the other information and settings that can be changed and what they mean please refer to Appendix F (Sample SHARED.INI File) and Appendix G (Sample DOCSTAR.INI File). Additional points to remember about DocSTAR Host Software: 1. Scanning ? Only the Host system is able to scan documents (except for DocSTAR SE Scan Stations). 2.
Additional points to remember about DocSTAR View/File Software: 1. Scanning ? A DocSTAR View/File station cannot scan, the scan function is not accessible. 2. Filing (View/File Client Only, View Client cannot file documents) ? When documents have been filed from the client, the Host system processes the documents (DocSTAR must be running on the Host). 3.
Section 2: DocSTAR Fax Software ? This section will cover basic information about DocSTAR Fax Software DocSTAR Fax Server Software is not actually a real Fax Server package. It is provided with DocSTAR to serve as a light-duty convenience fax. For high-volume faxing requirements, customers must be offered a different solution, such as a dedicated highvolume fax machine/fax server. The following is a working overview of the Fax Server software operation.
Fax Server Software Operation Sending Faxes When sending faxes from DocSTAR, DocSTAR software creates a text file (.txt) and associated image files (.pcx) with a random alphabetic filename beginning with the letter ‘F’ (stands for fax). The text file will contain the filename(s) of the image files to be faxed out. All of the created files are placed in the C:\DOCSTAR\DATABASE\FAX directory. As shown below: DocSTAR software also creates an entry in the ‘Send’ table of the Fax database (Fax.mdb).
Once these steps have been completed Fax Server software reads the database entry and converts the image file(s) into one single or multi-page fax file. The name of the resulting fax file is a random alphabetic filename beginning with the letter ‘S’ (stands for send) and a .fax extension. As shown below: The fax database also reflects the change in filename to Sxxxxxxx.fax. As the fax send procedure progresses, the status is updated in the fax database.
Fax Server software, FAXSERVE.EXE, also creates an entry in the ‘Receive’ table of the Fax database (Fax.mdb). As Shown below: Once these steps have been completed, DocSTAR software converts the Rxxxxxxx.dcx file into a standard DocSTAR document consisting of .tif image files and placed into the DocSTAR Inbox with a title such as ‘Fax from…’. As the fax receive procedure progresses, the status is updated in the fax database.
Section 3: DocSTAR Import Software ? This section will cover basic information about DocSTAR Import Software Each DocSTAR importing software is an add-on option. The following section will describe the general importing process, then each import software package and its special uses will be described. The DocSTAR Import Process The first time that any import software is loaded on the DocSTAR Host or client workstation an entry is made in the Shared.ini file.
If the document was imported through Print Import software, there may also be an associated text file containing the actual text found in the document. DocSTAR Software will use this text to index the document as well. DocSTAR software is responsible for converting the file format (.tif, .jpg, .dcx, .pcx, .bmp) of the image file(s) in the Import directory to one of DocSTAR’s native file formats, .tif (for b&w) or .jpg (for grayscale and color).
DocSTAR Image Import Software DocSTAR Image Import Software, DSIMPORT.EXE, is used to manually select either a single image file or a group of image files for importing directly into the DocSTAR Inbox. As shown below: The image files must be in one of the following formats: TIFF (.TIF, non LZW), JPEG (.JPG), DCX, PCX, or BMP.
Auto Import will poll the C:\Scan directory for new image files to import every 30 seconds. When a new image file is found Auto Import will change the name of the image file(s) to a random name beginning with ‘I’ (stands for Import) and transfer the image file(s) to the DocSTAR Import directory. Auto Import will retain the original image file format and file extension (it will be converted by DocSTAR Software once imported into the Inbox). A new entry is also made into the Import database.
Step 2: Set the type of delimiters you have used in the conversion file. You will then get a preview of how the data will appear. As shown below: Step 3: You may change/set the field types. You need to set the Path/File Name, Title, Keywords, and unused fields. If you select multiple columns for the same field, they will be used in order from left to right.
Page 66 DocSTAR Level 2 Service Training Workbook
Step 4: You may now convert the images or write a preliminary report on expected changes. You can append to an existing report file, display errors, or stop processing after a specified number of errors. Step 5: In this step, you will be asked if you wish to save this template or any changes you have made. You may want to preview the data one last time before clicking Finish.
Step 6: This is the final step, after pressing the ‘Finish’ button you will see a progress bar along with a brief summary of files for conversion. Total possible files will include all files listed in the master conversion file. ‘Successes’ states how many of these files were/will be converted and sent to DocSTAR, ‘Failures’ states how many were unable to be converted. ‘Skipped’ states the number of records you selected in Step 2. For a more detailed report, check the dsconimp.txt file.
Section 4: Xerox Textbridge Pro Millennium Software ? This section will cover basic information about Xerox Textbridge Pro Millennium Software Xerox Textbridge Pro Millennium Software is an OCR package that DocSTAR software has been designed and tested to work with. Xerox Textbridge Pro Millennium software is an optional software package that must be purchased in addition to DocSTAR.
Section 5: Optional Software Lab ? This section is designed to provide hands-on experience in setting up and using optional software packages such as DocSTAR Import Software and Xerox Textbridge Pro Millennium. Activity: Install all the different DocSTAR importing software packages and follow the transfer of files through the importing process.
Unit 5: DocSTAR Mass Storage Devices ? This unit is designed to present DocSTAR Mass Storage Devices in detail.
Section 1: RAID Hardware (Internal and External) ? This section will cover basic information about DocSTAR internal and external RAID hardware Both the Internal and External RAID devices use IDE (ATA-II) hard drives set as Master. Internal RAID Hardware The Internal RAID device is setup as a RAID Level 1 device. This means that it uses ‘Disk Mirroring.’ The Internal RAID device uses a Promise Fasttrak66 PCI IDE RAID Controller card to write the data to IDE channel 1 and IDE channel 2 simultaneously.
Below is a view of the drive bay from the rear. Below is a view of the drive bay from the front. The hard drives are installed inside of the drive carrier, below is a picture of the drive carrier. In addition to the hardware shown, the RAID Controller BIOS must be entered to define an array (if one has not already been defined) or delete an array (if one is to be deleted and recreated). Note: It is not generally required to enter the BIOS and change these settings since they are shipped pre-defined.
FastTrak66 (tm) BIOS Version 1.xx (Build xx) (c) 1995-2000 Promise Technology, Inc. All rights reserved. ID MODE SIZE TRACK-MAPPING STATUS _________________________________________________________________ 1 * 1x2 Mirror 29188M 3720/255/63 Functional Press to enter FastBuild (tm) Utility... The * next to the ID # denotes that the internal RAID is the boot device. After pressing you will see the FastBuild Utility Main Menu as shown below: FastBuild (tm) Utility 1.
FastBuild (tm) Utility 1.xx (c) 1996-2000 Promise Technology, Inc. [ Auto Setup Options Menu ] Optimize Array for: Typical Application to use: Security Not Available [ Array Setup Configuration] Mode..........................................Mirror Spare Drive........................................0 Drive(s) Used in Array.............................2 Array Disk Capacity (size in MB)...............
If you select ‘Define Array [3],’ you will be able to see the current array and its status as shown below, the asterisk (*) denotes that the array is the boot drive: FastBuild (tm) Utility 1.xx (c) 1996-2000 Promise Technology, Inc.
Note: If you delete an array and later want to restore it, you must use the same settings in Auto Setup as were used to originally define the array, otherwise you will lose the data that exists on the drive. If you select ‘Rebuild Array [5],’ you will be able to select an array to be rebuilt as shown below: FastBuild (tm) Utility 1.xx (c) 1996-2000 Promise Technology, Inc.
FastBuild (tm) Utility 1.xx (c) 1996-2000 Promise Technology, Inc. [ Adapter Configuration - Options ] Halt On Error : Enable [ System Resources Configuration ] Channel Channel 1 2 Interrupt Interrupt : A : A I/O Port I/O Port : 6800 : 7000 [ Keys Available ] [? ,? ,Space] Change Option [ESC] Exit Making the Internal RAID Device the Boot drive Using the Internal RAID as the boot drive offers the advantage of fault tolerance. However, it is not necessary for Two-Tier Storage.
You can open the utility by either double-clicking on the System Tray Icon or by selecting it from the Start Menu\Programs\Promise\Fasttrak\FastCheck Monitoring Utility. There are three tabs you may select from the utility. Two of the tabs, ‘Array’ and ‘Controller,’ are just monitoring tabs. The third tab, ‘Options,’ allows you to set some parameters for the Utility functions.
The ‘Options’ tab displays the current FastCheck Utility settings and allows you to modify them. In general, the options should be set as shown below: Special Note: The ASPI Layer version must be 4.60 or later and the DocSTAR software version must be 2.33 or later. External RAID Hardware The External RAID device is setup as a RAID Level 5 device w/a hot-swappable spare. This means that it uses ‘Striping w/Parity’ and there is an idle drive in place, just in case one of the other 5 drives fail.
The following diagram shows the External RAID from the front view: 1. LCD Status Panel DocSTAR RAID OOOOOS R5 ID:2 First 6 letters on the second line correspond to each of the HDD bays (Left to Right (1 - 6)): O R I S X On-line and Functional Error Occurred Identifying Disk Drive Spare Disk Drive Disk Drive Not Installed Second item listed is the Raid Level (R5=Level 5). Third item listed is SCSI ID # (ID:2=SCSI ID 2). 2. HDD Trays 1 – 6 (Hot-swappable Drive carriers) 3.
Replacing a cooling fan: 1. While the External RAID is running, unscrew the 2 Fan Door Screws and swing fan door open. 2. Disconnect power connector for failed fan. Note: The other fans are still turning. Please use caution when replacing fan. 3. Unscrew the 4 fan screws and replace fan. 4. Connect new fan power connector. 5. Close fan door and screw Fan Door Screws back into place. Replacing a Hard Drive: 1. While the External RAID is running, identify which drive has failed by the RED LED indicator. 2.
Replacing a Power Supply: 1. While the External RAID is running, identify which power supply has failed by the Power Supply LED indicator on the front. Whichever LED is not lit, indicates the failed power supply. 2. Switch off and unscrew the failed power supply and slide the power supply out as shown at right. 3. Replace the power supply with a new power supply, screw it in, and switch it on. 4. Then press the RESET switch to link the 2 power supplies again and stop the buzzer sound.
Section 2: Adding RAID/Two-Tier Storage to a DocSTAR System ? This section will cover basic information about adding RAID/Two-Tier Storage to a DocSTAR system After the RAID hardware (and utility software for Internal RAID) is installed DocSTAR software must be setup to use the Two-Tier storage system incorporating the RAID device. The following requirements must be met for Two-Tier storage to work: The system must be running DocSTAR software version 2.
The drive letter, in the Host Path shown above, must correspond to the drive letter of the data partition of the RAID device (C:\ usually represents the system partition and D:\usually represents the data partition). You will see a device label appear on the right as you type a Host Path. This is displayed automatically for you to verify that you have selected the proper partition. You may specify up to 4 RAID devices in this window.
Two-Tier Storage Utilities Once the Two-Tier storage setup has been completed you may begin using any of the provided Two-Tier storage utilities. Selecting the ‘Two Tier’ button from the administration program accesses the utilities. You will see the following screen: The four Two-Tier Utilities are outlined below: Update Archive Disk: Allows you to copy the updated or new files from RAID to the corresponding Archive Disk. (Usually image files that have updated tags or new annotation files).
Section 3: RAID Lab ? This section will provide hands-on experience in installing and troubleshooting RAID hardware and Two-Tier Storage software Activity: Install the RAID hardware. For internal RAID create the Mirror and make the RAID bootable. For the external RAID install the additional SCSI card and attach the RAID Tower to it verifying that the Tower is terminated properly. Set the Tower as the bootable drive.
Appendix A: SCSI Interfaces Names SCSI-1 Max Speed (MB/s) SCSI-1 Fast SCSI 5 10 No. of Devices (A,B) 8 8 SCSI-2 Max Total Length of Cable 6m External Connector Types Comments 50-pin low-density (SCSI-1, Centronix, A-Cable) Many peripherals are available. D Up to 4 devices 3m: 5 or more devices 1.5m Fast Wide SCSI 20 16 Ultra SCSI 20 8 1.
Appendix B: Sample MAINIDX.
Appendix B: Sample MAINIDX.
Appendix B: Sample MAINIDX.
Appendix C: Sample DBCHECK.LOG File ============================================================= Beginning Database Check-Up Reporting 1:56:23 PM 1/21/2000 ============================================================= ============================================================= Report: Duplicate document table entries 1/21/2000 1:56:23 PM ============================================================= ...
Appendix C: Sample DBCHECK.LOG File(cont’d) <<= ---------------------------------------------------- =>> ...None found <<= ---------------------------------------------------- =>> <<= Documents with TOO MANY pages =>> <<= ---------------------------------------------------- =>> ...
Appendix C: Sample DBCHECK.LOG File(cont’d) ============================================================= Report: Documents that still have Inbox path but no Inbox or Review Box Record 1/21/2000 1:56:24 PM ============================================================= ...
Appendix D: Commonly Used SQL Statements SELECT SQL Statements To find the number of pages currently stored in a DocSTAR: SELECT * FROM PAGE To find the number of documents that have been archived to the inbox directory (When the inbox and review box are empty and there are no documents pending processing; AN INVALID CONDITION): SELECT * FROM DOCUMENT WHERE PATH_ LIKE ‘C:\DOCSTAR\INBOX\*’ AND INDEXED_=TRUE EXECUTE SQL Statements To redirect the database to the proper Volume: The following SQL redirects the
Appendix E: Network Cable & Protocol Comparison Charts Network Cable Comparison Chart Cable Features Thinnet coaxial (10Base2) Thicknet coaxial (10Base5) Twisted-pair (10BaseT) (100BaseT) Fiber-optic Cable cost More than twisted-pair 185 meters/ ~607 feet More than thinnet 500 meters/ ~1640 feet Least Expensive 100 meters/ ~328 feet Most Expensive 10 Mbps 10Mbps >1Gbps Fairly flexible Good resistance to interference Less flexible Good resistance to interference 10Mbps (100Mbps for 100BaseT) M
Appendix F: Sample SHARED.
Appendix F: Sample SHARED.
Appendix F: Sample SHARED.INI File(cont’d) (Number of rings to answer,0-9) st (Print 1 Page of Fax, Yes= -1, No=0) (Print Whole Fax, Yes= -1, No=0) Rings=1 Print First Page=0 Print All=0 [System] HostVersion=2.33 (Build 073) Status=17C92F8 ? This is Host System Information. (DocSTAR Software Version) (Current (encrypted) ‘Admin Password’, if it exists. Place a semicolon(;) in front of the word ‘Status’ and save it to bypass the Admin Password temporarily.
Appendix G: Sample DOCSTAR.INI File Wherever there is a yes or no option it is signified by a –1(Yes) or 0(No). ? These are the ‘System Settings’ for this station.
Appendix G: Sample DOCSTAR.INI File(cont’d) installation Program, Do Not Change This Value) [PrintImport] TextCapture=0 ? These are the ‘Print Import’ settings for this station. (Index Document Using Text Found in Document(Only for Documents Containing Text), Yes= -1, No=0) [Jukebox] PrecacheVisible=0 ? This is the ‘Jukebox Precache Panel Visible’ setting.
Appendix H: Sample DSERRLOG.TXT File 2/29/2000 10:21:20 PM :-1 LOG: Main Form Loaded 2.32 (Build 190) Host Volume Database: C:\DOCSTAR\DATABASE Remote: 0 2/29/2000 10:21:25 PM DocSTAR: 10 LOG: Main Form Unloading 2/29/2000 10:22:36 PM :-1 LOG: Main Form Loaded 2.32 (Build 190) Host Volume Database: C:\DOCSTAR\DATABASE Remote: 0 2/29/2000 10:23:51 PM DocSTAR: 10 LOG: Main Form Unloading 2/29/2000 10:24:09 PM :-1 LOG: Main Form Loaded 2.
Appendix I: Cluster/Allocation Unit Chart Partition Size FAT or FAT16 FAT32 NTFS 0-127 MB - 512 bytes - 512 bytes - 512 bytes 2048-8191 MB 2048 bytes (2 KB) 4096 bytes (4 KB) 8192 bytes (8 KB) 16384 bytes (16 KB) 32768 bytes (32 KB) - 8192-16383 MB - 16384-32,767 MB - > 32768 MB (up to 2 TB) - 4096 bytes (4 KB) 4096 bytes (4 KB) 4096 bytes (4 KB) 8192 bytes (8 KB) 16384 bytes (16 KB) 32768 bytes (32 KB) 1024 bytes (1 KB) 2048 bytes (2 KB) 4096 bytes (4 KB) 4096 bytes (4 KB) 4096 bytes (4
