Oculus-TCi Device Driver Version: 1.14
Pharlap 386/Dos-Extender Version
--------------------------------------
Table of Content
1. Installation Procedure
2. Supported Hardware
3. Disk Content
4. WCONFIG.EXE
5. ODX.INI
6. EMBBUF.EXE
7. ODXDEMO.EXE
8. Creating Applications
9. JPEG codec
10. History
11. Licence Agreement
--------------------------------------------------------------------------
1. INSTALLATION PROCEDURE
a) Insert the Oculus-TCi Device Driver Disk in a floppy drive
b) From the DOS prompt, type <drive>:install
where <drive> is replaced with the floppy drive letter
(ie. a:install)
2. SUPPORTED HARDWARE
2.1 TCI-SE (if and only if the Host Frame Buffer is available: see EMBBUF.EXE)
Features:
a) Multiple board access capability.
b) Monochrome acquisition support.
c) 16-bit and 32-bit RGB acquisition support.
d) Host Frame Buffer support in 8, 16 and 32 bits/pixel.
Limitations:
a) Does not use interrupts.
b) Does not support video transfer to the system VGA.
2.2 TCI-VGA in dual moditor mode only (where another VGA is the primary display system).
Features:
a) Multiple board access capability.
b) Monochrome acquisition support.
c) 16-bit and 32-bit RGB acquisition support.
d) Host Frame Buffer support in 8, 16 and 32 bits/pixel.
Limitations:
a) Does not use interrupts.
b) Supports only the TCi-VGA in dual-monitor mode (another VGA must be
in the system).
c) Does not support video transfer in the system VGA.
d) Only one acquisition frame buffer is available on the TCi-VGA.
2.3 Host Frame Buffer (see also EMBBUF.EXE)
Features
a) Support for 8, 16 and 32 bits/pixel.
b) Can be created with both the TCI-SE and the TCI-VGA.
Limitations
a) There is only 1 Host Frame Buffer Memory location. Thus if
more than one board requests a Host Frame Buffer, the same memory
will be allocated to the boards.
2.4 JPEG encoding and decoding
Features
a) JPEG codec (if the Compression/Decompression Module (CDM) is present).
Limitations
a) Maximum compressed image size of 640x480 in PAL/CCIR.
b) When decoding, the JPEG file should have been encoded with
quality factor not greater than 80. Otherwise a decompression
error will result.
c) Codec firmware is unoptimized.
Known Bugs
a) Decompression of 8-bit monochrome image is not supported.
b) A green band at the top of the image might be saved with the
compressed image.
c) Occasionally the error 'VCPXI rsp timeout' can occur while
compressing images.
3. DISK CONTENT
By default all files are copied to c:\odtcipl3 unless indicated below.
Please see the TCi User's Guide for information on the distribution files.
EMBBUF.EXE Extended Memory Buffer creation program.
_ENV.H Environment definition file.
ENV.H Environment selection file.
GETARG.H 'Search for a given switch on a command line' header file.
ODTCI.LIB Oculus-TCi Watcom/Pharlap/386 32-bit Device Driver Library.
ODX.H ODX prototype definition header file.
ODXDEF.H ODX Structure Definitions
ODXDEMO.C Demonstration program.
ODXDEMO.EXE Demonstration program executable to be run with Pharlap
386/Dos-Extender (run386.exe).
ODXDEMO.LK1 Demonstration program Watcom linker file.
ODXDEMO.MK Demonstration program Watcom makefile.
ODXDEMO.MK1 Demonstration program Watcom makefile.
ODXDEMO.TGT Demonstration program Watcom 'traget' file.
ODXDEMO.WPJ Demonstration program Watcom 'project' file.
OPR.H ODX register definition header file.
PVIEW.EXE DOS PCI bus mapping view/utility.
READ.TXT This file.
STD.H Type definition header file.
SYSDIAG.DLL Required DLL for WCONFIG.EXE
WCONFIG.EXE Oculus-TCi configuration program.
JPEG Codec Related Files
COD.SUN JPEG codec firmware.
INIT.SUN JPEG codec firmware.
MONITOR. VCPI interface firmware.
VCP.INI JPEG codec configuration file.
4. WCONFIG
WCONFIG is a Windows 3.1 configuration program for the Oculus-Tci.
Use it to configure the boards before running an ODX application
compiled for Pharlap 386/Dos-Extender. WCONFIG creates a configuration
file (ODX.INI) which can also be edited and created with a text editor.
Several sections of the WCONFIG utility don't apply to the Pharlap
386/Dos-Extender version of the driver:
- Display Section/Primary VGA
5. ODX.INI
(See also the Oculus-TCi user's manual.)
New ODX.INI Entries:
"Secondary Buffer Display Format" :
value Description
4 VGA 640x480 60Hz
5 VGA 640x480 72Hz
6 VGA 640x480 75Hz
7 VGA 640x480 85Hz
9 SVGA 800x600 56Hz
10 SVGA 800x600 60Hz
12 SVGA 800x600 72Hz
13 SVGA 800x600 75Hz
14 SVGA 800x600 85Hz
16 SVGA 1024x768 60Hz
17 SVGA 1024x768 70Hz
18 SVGA 1024x768 72Hz
19 SVGA 1024x768 75Hz
20 SVGA 1024x768 85Hz
21 SVGA 1280x1024 60Hz
23 SVGA 1280x1024 72Hz
24 SVGA 1280x1024 75Hz
25 SVGA 1280x1024 85Hz
"Secondary Buffer Type" :
value Description
0 RGB 16 (5551)
1 RGB 32 (8888)
2 Monochrome 8
6. EMBBUF.EXE
This program is a TSR which creates an Extended Memory Buffer. The main
characteristic of this Buffer is that its entire memory is physically
contiguous, a necessity in order to acquire with the Oculus-TCI. This
Buffer is then used by the ODTCI Device Driver to create a Host Frame
Buffer Minor Device.
Usage: EMBBUF [options] [parameters]
-c check if TSR is installed
-a allocate a buffer in EMB (size in KB)
-r release buffer in EMB
-p get physical address of buffer
-h get handle of buffer
-s get size of buffer
-i get information on EMB
-? get help
-w write a word to buffer (offset, data, len) in hex
-g get a word from buffer (offset, len) in hex
Example: If you want 2 Host Frame Buffer of 320x240, 32 bits/pixel:
2 * 320 * 240 * 4 bytes/pixel = 614400 bytes or 600 KB.
Thus before running your application, run the EMBBUF program
as follow: EMBBUF -a 600
Note: When defining an 8-bit Host Frame Buffer, you must allocate an
additional amount of memory equal to 1/8th of the Host Buffer
Size. This extra memory is needed by the TCI in order to hold
the 'UV' component of the YUV data generated when acquiring
images. Even if you define more than 1 Host Frame Buffer, only
one extra region of memory needs to be allocated.
Example 2:
If you want 3 Host Frame Buffer of 320x240, 8 bits/pixel:
(3 * 320 * 240 * 1 byte/pixel) + ((320 * 240)/8) = 240000 bytes or ~235 KB.
7. ODXDEMO.EXE
ODXDEMO.EXE is a Pharlap 386/Dos-Extender Demonstration Program. Its usage
is defined below and can be displayed by specifying the switch '-?' or
'-h'.
Usage: ODXDEMO [options]
Switch Default Description
-t? 0 Test to Perform
0: TCI Information
1: HFB to SFB Copy
2: HFB Acquisition followed by a HFB to SFB Copy
3: Acquisition in SFB
Glossary: HFB = Host Frame Buffer
SFB = Secondary VGA Frame Buffer
For example, to execute the test #3, one would type at the DOS command
prompt the following: run386 odxdemo -t3
8. CREATING APPLICATIONS
Watcom C compiler v:10.5
------------------------
1) Install Pharlap TNT 386/Dos-Extender development kit.
2) Create a project with your application's files.
3) Add the library ODTCI.LIB to your project.
- The memory model must be FLAT (-mf).
- Calling convention: 80486, Stack Based Calling (-4s)
To run your application, type on the command line:
run386 odxdemo.exe.
To debug your application, type on the command line:
wd /tr=pls odxdemo
Use the demonstration program as an example.
You can compile the demonstration program with the IDE or on the command line
by typing:
wmake -f odxdemo.mk -h -e
Please modify odxdemo.wpj for your development environment.
9. JPEG CODEC
MONITOR is a firmware file necessary to implement communication with
the CDM. The JPEG codec is implemented in firmware executing on the CDM
module. The files that need to be uploaded to the CDM are: INIT.SUN and
COD.SUN. They must be present in the working directory of the
executing application. The configuration file (VCP.INI) is also expected
to be located in this directory.
The frame to be encoded is acquired at the beginning of the compression
process. Note that it is not the image previously grabbed and currently
displayed on the output device that will be encoded.
The ODXDEMO application demonstrates encoding of a single frame in full
color format. Sequential compression and two other color formats are also
available.
10. HISTORY
January 24th, 1996
Release of Version 1.12
March 1fst, 1996
Release of Version 1.12c
Fixes:
a) Fixed minor device selection during initialization;
b) Fixed timing functions.
April 8th, 1996
Release of Version 1.13
New Features:
a) Added support for graphic functions in 32 bits/pixel (ie. drwbox)
b) Added support for Host Frame Buffers
c) Host frame buffer pixel size is now independant of the system VGA pixel
size.
d) Support of PAL acquisition with the RGB module.
e) Support of TCI-VGAs with 1MB of frame buffer memory.
Fixes:
a) Fixed Triton PCI chipset deadlock for TCI-Acquisition only. Fix only available
in full frame acquistion when there is no scaling.
May 8th, 1996
Release of Version 1.14
New Features:
a) JPEG codec (if the CDM module present).
Fixes :
a) When acquiring a single frame, the function 'fbgrab' will only
return upon the completion of the frame grab. This is true only
for the DOS Extender Libraries.
11. LICENCE AGREEMENT
The installation program used to install the Oculus-TCi Device Driver, INSTALL,
is licensed software provided by Knowledge Dynamic Corp, P.O. Box
780068, San Antonio, Texas 78278 (USA). INSTALL is Copyright (c)
1987-1993 by Knowledge Dynamics Corp which reserves all copyright
protection worldwide. INSTALL is provided to you for the exclusive
purpose of installing the Oculus-TCi Device Driver. Coreco Inc. is exclusively
responsible for the support of the Oculus-TCi Device Driver, including support
during the installation phase. In no event will Knowledge Dynamic Corp
provide any technical support for the Oculus-TCi Device Driver.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.