Scanner Installation
Different scanner models sometimes have slightly different setup methods. Use the below to help but read, read, read the scanner documentation or ask for help from DaySpring.
Fujitsu fi-4120C2 Image Scanner
Try to install everything according to manufacturer or DaySpring instructions, but it goes generally as follows:
Physically install hardware according to manual
Plug in power and connection (scsi, usb, etc)
Turn on computer
Install software/drivers
Do NOT install with windows autofind (see manual to make sure)
Install ISIS drivers (ISIS drivers are lower level drivers, that speak a more complicated yet specific language to the scanner; ISIS allows more functionality range for scanners in a business install)
Check device manager for proper install
Test with incorporated scan software or fujitsu software
Fujitsu fi-4091D Large Scanner
Following is a sketch of the physical scanner system setup, of the large scanners. It is not easy to find documentation on the entire scanning systesms parts names, labeled like below.
Installation of Imaging Software
Patched 3.1
Install Scanner software
VRS
Note: Only install VRS on the large, (ussually) SCSI connected scanners, that are capable of the VRS software
Install Kofax Adrenaline software for PCI board in computer from CD or website v3.65B or
website v3.75 (prefered)
Device Manager > Scanners > PCI device > right click > Update Driver... > choose from unzipped place from web, or CD
Control Panel > KSM > Choose the source (4097)
Control Panel > KCM > Choose the accelerator
Fujitsu VRS software CD v1.03 - specifically made for fujitsu scanners we have - can also get it off Fujitsu
website
Try Kofax Board initialization
Test with Kofax demo scan software that was installed above on the Start menu
Troubleshoot: WinXP device manager manual install on un-drivered device if above software does not let you scan
Setup database connection
Verify that a UMBC VPN session with paradocs group access, is working and on
-
setup ODBC datasource in control panel
datasource: paradocs
database: paradocs
server: gsdocs.umbc.edu
<username>
<password>
Para-Docs Install
Refer to PDF Instructions from paradocs makers, located on I:\Information Technology\Software\ParaDocs\PD Imaging 3.1
Install base package of ParaDocs install 3.1
Use ParaDocs Config utility from Start menu
enter server name gsdocs.umbc.ed
“Load all defaults” button
VRS option check marked to be on IF scanner is using Virtual ReScan (Kofax, big scanners), otherwise off
Database type: POSTGRES
1)
Test that Scan and Profile programs work
Patch Para-Docs
Older than 3.1 version
Install software on Para-Docs Imaging CD (follow included directions .pdf)
Patch/Copy over .exe’s if needed; ussually never needed (to upgrade to newer version than CD above)
Install PostgreSQL ODBC driver <link to interior site>
‘Configure image client tools’ icon (FIX ME)
Type server name (gsdocs.umbc.edu) into server-name field (FIX ME)
‘Load all Defaults’ button twice to autofill server into correct fields
Further edit text settings files; ussually never needed
edms_boi.ini - holds initialisation settings for blah (FIX ME)
Connection = Driver = {PostreSQL}; ... (FIX ME) ... database =gsdocs.umbc.edu
other? (FIX ME)
Set Scanner settings inside of ParaDocs Scanner application (this should only need to be done once)
‘Batch Control’ button
Login to Para-Docs table editor as Admin (FIX ME) (login to what? what is table editor?)
‘Scanner Workstation’ button
“Scanner Workstation Administration” window
Workstation: <netbios name of local computer> (run “ipconfig /all” to get this name)
ID: <automatic>
Batch Type: use “NORMAL” for most uses; see <seperation of scanning and profiling> (must be alpha characters)
Batch ID: batch names are preficed with this
Seperate: # of pages in each ‘group’; could be used if the number of pages scanned in a batch is constant
Schema: dropdown - use default (FIX ME) (what is it?)
‘Add’ button; ‘Apply’ button
Scanner Application
| Version | Date Implemented | Notes |
| 2.1.32 | 2002? | Put onto 3 original large scanners (2 in GS, 1 in UG) and 2 small scanners (Kathies) |
| 3.1.83 | 1/2006 | Put onto 1 small scanner in AD211b section C; used it to test server upgrade and then changed it to live server |
| 3.2.0.86 | 2/14/2006 | Put onto the same 1 small scanner as above; it implements the autosave functionality; see below |
| 3.2.0.?? | 6/08/2006 | Patched (just the PDScan.exe) onto small scanner in AD211b section C, Kathy Ruth, and Kathie Nees scanners because old version of this app would write incorrect data to the database and mess stuff up |
| 3.2.0.?? | 11/21/2006 | Patched (just the PDProfile.exe) onto big scanner in 211B Section B, to fix having to close profiler each time |
The Scanning application supplied by DaySpring had its biggest updated to version 3.1.83 in January of 2006. We paid a couple thousand for a license, and made it point to the live systems to be used during our peak period as a third main scanner. We plan to upgrade all systems to this new version of the software eventually.
Autosave to PDF, not TIF
This problem and explanation is DEPRECATED
Deprecated - no longer required or necessary to use. Upon server upgrade, functionality that allows all documents being posted into the system to be automatically changed to PDFs, has been implemented.
Very quickly a problem was introduced once the new scanner mentioned above was put into place. The new application did not default to saving scans to PDFs. The old ones did.
Scanners assumed or forgot that they had to select PDF as the save as... type. They were trained to select this feature, but it is a miniscule detail for scanners to constantly remember.
DaySpring was contacted and they provided a fix in the means of a new, modified version of the software that allows you to set a variable in the config files to allow the automatic choice of the document save as... type.
Following are the directions to implement this ‘custom fix’2):
Make a backup of PDScan.exe and the .CHN and .CHW files from the ..\Para-Docs\bin folder into another folder. ie..\bin\bkup
Copy the files from the zip into ..\Para-Docs\bin.
Open EDMSTree.ini in the ..\Para-Docs\ini folder.
If the tag [LOCAL] is not there add it below [COMMON].
Add a line under [LOCAL]
PdfOnly = true
Please do not edit anything else in this file without a Para-Docs support person’s instruction. Doing so may cause the client station to malfunction.
How to delete a batch scan
Below are instruction on how to delete a scan that was done with Batch scan. This may happen if you accidently scan the wrong thing, or want to get rid of some trash batches sitting out there. This is all done from within the ParaDocs scanning and profiling applications installed on select scanning workstations.
Open the scanning screen
Click on File
Click on Batch Process
Click on Batch Control
Type in the User Name and Password that you use to log into Paradocs
A Batch Control screen will appear
Highlight the batch you want to delete
Click on Delete
How to view queue of documents being posted / scanned to paradocs
In a file explorer window, type the following into the location bar at the top. You are going to be replacing C:/whatevever :
\\gsdocs.umbc.edu
Next, click on the ‘post’ directory in the list of directories.
Again, click on the second ‘post’ directory in the subsequent list of directories.
An .tif image file, and a .env text file will exist for each entry in the queue being posted.