Product Support
   OOMR Assistant
   Orion Survey
Service Support

OOMR Support

Have a question about OOMR? We encourage you to read through the FAQs below. If you don't find what you're looking for, or you would simply like confirmation of your understanding, please contact us via email or phone.
Email: This is the best route for asking questions and receiving documented answers.
Phone: 973-228-7843. If you don't get through immediately, leave a message in the tech support voice mailbox and we will get back to you promptly.

FAQ: General/Setup
Q: What is the latest version of OOMR?
A: The latest version is OOMR Version 1.3.
You can download the latest version by clicking here.

Q: What is the difference between OOMR and OOMR Assistant?
A: OOMR is a set of programming components that developers can use enable OMR (Optical Mark Recognition) capability in their applications. OOMR accomplishes it's work by reading a definition file, provided by the programmer, which describes where marks are to be found on a form. Creating this definition file by hand, while possible, is tedious and error prone. OOMR Assistant provides a user interface that allows developers to graphically define where marks are to be found by highlighting and naming input areas on the form.

Q: Is it possible to save money by purchasing only OOMR, without OOMR Assistant?
A: For now, OOMR Assistant is bundled with the OOMR components free of charge. Anyone who purchases OOMR now receives OOMR Assistant at no additional cost. It is possible that these products will be unbundled in a future version, but for now, one price buys both. Also, anyone who purchases OOMR with OOMR Assistant now will receive the next versions of OOMR and OOMR Assistant as free upgrades, regardless of any future purchase price of OOMR Assistant, when it is unbundled.

Q: Can I re-distribute OOMR components with my application?
A: Yes. There are various purchasing options for OOMR, which include an unlimited distribution/royalty free option:
Click here for up to date pricing information.
Click here to download a free copy of OOMR.
While liberal distribution options are available, all distributed versions of OOMR are licensed. When you purchase OOMR, the product comes with a certain number of 'activations'. When you distribute OOMR components, you ship your product with the necessary license code to automatically activate the product the first time it runs. Activation is done automatically, over the internet. If your user does not have an internet connection, they will receive a popup dialog box that will allow them to register manually.

Q: What components do I need to ship with my application?
A: There are four DLLs that need to be shipped:
OBITMAPATL.DLL - Register when you install your application (i.e., using regsvr32.exe)
OTWAINATL.DLL - Register when you install your application (i.e., using regsvr32.exe)
KEYLIB32.DLL - No registration. Install to the system directory.
SKCA32.DLL - No registration. Install to the system directory.

Q: How much disk space will OOMR use when installed?
A: OOMR and OOMR Assistant fully installed, including documentation and samples, require less than four megabytes of disk space.
The four distributable DLLs require approximately 500K.

Q: Can I use OOMR with my .NET WinForms Application?
A: Yes. In fact, OOMR Assistant uses OOMR and is itself 100% managed .NET C# code.

Q: What scanners does OOMR work with?
A: OOMR V1.3 is designed to work with scanners supporting the TWAIN Specification 1.9 from the TWAIN Working Group Committee. OOMR V1.3 supports scanners with Automatic Document Feeders (ADF) or simple flat bed scanners.
OOMR V1.3 has been tested and is known to work with the following scanners:
HP Scanjet 5550c
Brother MFC 5100-C
Brother MFC 3100-C
Lexmark X-61
Microtek Scanners

Q: OOMR documentation says it corrects for ‘skewing’. What is ‘skewing’?
A: Skewing is what happens when a document is fed on a slight angle by the document feeder, or when a document is layed on the flat-bed such that it is not perfectly square (at a 90-degree angle) with the scanning area. OOMR will adjust for documents that are skewed up to a degree or two, depending on the way the form is designed (size of input marks most affecting ability to adjust). Generally speaking, skewing is usually very slight when a automatic document is used.

Q: If documents are completely mis-fed, will OOMR automatically adjust?
A: No, not at this time. Automatic adjustment for documents fed backwards (180 degrees) or sideways (90 or 270 degrees) are planned for the near future.

Q: Why do I get empty responses reporting 40%, 50% or more filled?
A: It is not uncommon for blank input areas on a form to be reported as 5% or 10% filled. If your form uses very small input areas, it is also common for those non-filled areas to register as 50% or more filled after a scan. The reason for this is that documents that are slightly off a pixel or two in alignment when going through a scanner - this can cause OOMR to see a portion of the rectangular area on the form as being "filled".

Q: What is a good percentage filled to use when interpreting responses?
A: For the reasons stated above, we encourage you to set your "high water mark" at a fairly high percentage of fill - as much as 95% - in order to gaurantee you are reading the users mark, and not the form marker boundary. Generally speaking, the smaller your input areas the higher your percentage of fill should be. If your input areas are fairly large, you can lower the percentage of fill to catch "lazy" fills by your users.

Q: Why do I get a NULL or 'Nothing' handle back on my PictureReady event?
A: This can happen when you use the "file" protocol to scan from a disk image and the image cannot be read as a valid image file. If this happens when reading from your scanner, please let us know by sending an email to our support team. Please include the manufacturer name and model of your scanner.

Q: What are timing marks? Why do I need them?
A: Timing marks are the four marks that appear in the corners of a scan form. They are used to "calibrate" the form so that OOMR can know where to look for input areas and how to adjust for crooked or 'skewed' scans.
Generally, timing marks are designed as fairly large square blocks to ensure that they are recognized unconditionally by OOMR. You can vary the size of timing marks on a form by setting the timing mark size via the OOMR component API (see your programmer docs), but all timing marks must be of equal size. OOMR will scan in from the corners of your form, looking for timing marks.

Copyright (C) 2005,2006,2007,2008,2009,2010, by Orion Development Corporation.  All Rights Reserved. 973-866-5096