No part of this document may be reproduced, transmitted, photocopied, or translated into another language without the written consent of EPIX, Inc. Information in this document is subject to change without obligation or notice. EPIX, Inc. makes no warranty of any kind with regard to this document, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. EPIX, Inc. assumes no responsibility for any errors that may appear in this document. EPIX, Inc. reserves the right to make changes to the specifications of hardware and software at any time, without obligation or notice.
4MIP, SVIP, XCIP, XCAP, 4MEG VIDEO, 1MEG VIDEO, SILICON VIDEO MUX, QUICK SET VIDEO, 12-7MUX, IMAGE MEMORY EXPANSION, COC40, and COC402 are trademarks of EPIX, Inc.
EPIX, SILICON VIDEO, and PIXCI are registered trademarks of EPIX, Inc.
Other brand, product, and company names are trademarks or registered trademarks of their respective owners.
Printing: 16-Dec-2008
Thank you for purchasing imaging products from EPIX, Inc. We expect our products to perform to their specifications and provide support via the Internet at epix@epixinc.com, via FAX at 847 464 1919, and via telephone at 847 465 1818 to help with installation or to answer questions about the use of our products.
The SILICON VIDEO® 642M or 642C CMOS digital camera and PIXCI® SI imaging board, for the PCI bus, are packed in antistatic bags. Please keep the bags and box in which they were shipped should the need arise to return them. Prior to opening the bags, place the bags near the PC into which the PIXCI SI board will be installed.
We recommend installing the XCAP software prior to installing the PIXCI imaging board.
Please refer to the Software Installation chapter for the XCAP installation
directions, then follow the board installation instructions below.
The size and the number of images that can be stored in DRAM on the motherboard is a function of the amount of DRAM that is not needed by the operating system. XCAP, by default, reserves 16 MB of memory for image buffers. If more memory is required for image sequences, the ''Driver Assistant'' in the ''PIXCI Open/Close'' menu should be used to set the reserved memory size.
The PIXCI® imaging board can capture and store full resolution images
to DRAM on a burst mode PCI motherboard provided that other devices do not
significantly compete for PCI bus bandwidth.
The data transfer capabilities of the motherboard may limit the size of the
image that the PIXCI imaging board can transfer to memory on the motherboard.
PCI bus transfers from other devices will compete for data
transfer time with images to be transferred from the PIXCI imaging board to
memory on the motherboard.
The updating of clocks and other background tasks may interfere with the
capture of images.
These tasks should be disabled if error messages indicate that video
transfers have been interrupted.
Most motherboards manufactured since January 2001 should be capable of operation with the PIXCI imaging board, but motherboard manufacturers never cease to amaze us. If you have questions about the compatibility of the motherboard intended for use with the PIXCI imaging board, contact EPIX, Inc.
EPIX can provide complete, tested computer systems with PIXCI board, or boards and all
required software installed.
The PIXCI® SI imaging board has an 8 pin RJ45 and 9 pin D-Subminiature connectors which are accessible thru the bracket that mounts the board to the computer chassis. A shielded RJ45 cable is included with the SILICON VIDEO 9M001 or 9T001 Camera Kit for connecting to the camera. The cable carries power, control, and pixel clock to the camera, and carries pixel data from the camera.
Typically a 25 foot or 7.6 meter cable will operate at up to 70 MHz pixel clock rates. A 50 foot or 15 meter cable will operate at up to 32 MHz pixel clock rates.
A wire list for the 8 pin RJ45 cable follows.
| Pin No. | Name |
| 1 | Power |
| 2 | Ground |
| 3 | Negative pixel clock |
| 4 | Positive camera data |
| 5 | Negative camera data |
| 6 | Positive pixel clock |
| 7 | Positive SI data |
| 8 | Negative SI data |
CON2 is wired to most of the signals which are on HDR1 for external connection.
See the description for Header 1 for the signal functions.
| Signal | IN/ | Pin | Pin | IN/ | Signal |
| Name | OUT | Number | Number | OUT | Name |
| Ground | 1 | 6 | +5 VDC (0.75 Amp max) | ||
| NTRIG | I | 2 | 7 | I | PTRIG |
| Trigger | Trigger | ||||
| In - | In + | ||||
| Frame- | I | 3 | 8 | I | Frame+ |
| NFEN1 | PFEN1 | ||||
| Strobe- | O | 4 | 9 | O | Strobe+ |
| NSTR1 | PSTR1 | ||||
| OPTION | - | 5 | - | - | - |
See the Trigger and Camera Integration Register Programming section of
this manual in the Camera Control Register chapter for more information
on these signals.
An optional signal on pin 5 is available for custom use.
CON2 signals on pins 1 thru 4 and pins 6 thru 9 are wired to the same
signals on HDR1.
Header 1 is for signals external or internal to
the computer case.
External signals can be connected with a cable to 9 pin D-Subminiature
connector thru a second slot with a bracket to mount the D-Subminiature
connector.
A differential to TTL conversion module and 2 meter cable are available for
connecting TTL trigger, vertical drive, and strobe signals to the PIXCI SI.
Two 10 pin headers are provided for connecting external and internal signals to the PIXCI SI.
The description for Header 1 follows.
| Signal | IN/ | Pin | Pin | IN/ | Signal |
| Name | OUT | Number | Number | OUT | Name |
| Ground | 1 | 2 | +5 VDC (0.75 Amp max) | ||
| NTRIG | I | 3 | 4 | I | PTRIG |
| Trigger | Trigger | ||||
| In - | In + | ||||
| Frame- | I | 5 | 6 | I | Frame+ |
| NFEN | PFEN | ||||
| Strobe- | O | 7 | 8 | O | Strobe+ |
| PSTR | NSTR | ||||
| NIO | I/O | 9 | 10 | I/O | PIO |
| In/Out- | In/Out+ | ||||
See the Trigger and Camera Integration Register Programming section of
this manual in the Camera Control Register chapter for more information
on these signals.
Header 1 is for signals external or internal to
the computer case.
External signals can be connected with a cable to 9 pin D-Subminiature
connector thru a second slot with a bracket to mount the D-Subminiature
connector.
A differential to TTL conversion module and 2 meter cable are available for
connecting TTL trigger, vertical drive, and strobe signals to the PIXCI SI.
Header 1 is located in the lower left of the PIXCI SI board to the right of DB9 CON2 connector.
Pin 1 is ground.
Pin 2 is +5 volts thru a 0.75 ampere thermal sensing, self resetting fuse.
Pin 3, NTRIG, is a negative differential trigger input.
Pin 4, PTRIG, is a positive differential trigger input.
Pin 5, NFEN, is the negative differential frame enable input.
Pin 6, PFEN, is the positive differential frame enable input.
Pin 7, NSTR, is a negative differential strobe output.
Pin 8, PSTR, is a positive differential strobe output. The PSTR and NSTR signals are driven from the camera control state machine and the strobe signal is delayed by two state machine cycles from the exposure signal. The polarity of the NSTR and PSTR can be controlled via bit 5 in the PRIN camera control register.
Pin 9, NIO, is a negative differential board-to-board signal, which can be configured as an output, input, or both.
Pin 10, PIO, is a differential board to board control signal, which can be configured as an output, input, or both.
The intended use for NIO and PIO is for board to board wiring of the exposure signal when multiple cameras must have
the same exposure signal.
One board is configured as a master (driver), the other boards as slaves (receivers).
| Signal | IN/ | Pin | Pin | IN/ | Signal |
| Name | OUT | Number | Number | OUT | Name |
| Ground | 1 | 2 | +12 VDC (fused at 0.75 A) | ||
| Out 1 | Out | 3 | 4 | Ground | |
| Out 2 | Out | 5 | 6 | Ground | |
| In 1 | In | 7 | 8 | Ground | |
| In 2 | In | 9 | 10 | Ground | |
HDR2 is located in the lower left of the board near the DB9 CON2 connector.
Pin 1 of HDR2 is in the upper left position.
Pin 1 is ground.
Pin 2 is +12 volts thru a 0.75 ampere thermal sensing, self resetting fuse.
Pin 3, OUT1, is a general purpose TTL output. The General Purpose OUT1 is controlled by bit 17 in the IET register at offset 4. It is not buffered and should be used only to drive other devices internal to the enclosure.
Pin 4 is ground.
Pin 5, OUT2, is a general purpose TTL output. The General Purpose OUT2 is controlled by bit 18 in the IET register at offset 4. It is not buffered and should be used only to drive other devices internal to the enclosure.
Pin 6 is ground.
Pin 7, IN1, is a general purpose TTL input. This input is bit 23 of the IES register at offset 0. IN1 is pulled up to +5 volts via a 2K ohm resistor. It is not buffered and should be used only to receive signals from other devices internal to the enclosure.
Pin 8 is ground.
Pin 9, IN2, is a general purpose TTL input. This input is bit 24 of the IES register at offset 0. IN2 is pulled up to +5 volts via a 2K ohm resistor. It is not buffered and should be used only to receive signals from other devices internal to the enclosure.
Pin 10 is ground.
XCAP-Plus, XCAP-Std, XCAP-Ltd, and XCAP-Lite are easy to install by following the instructions below.
While XCAP is easy to install, like most manufacturers of computer software, we recommend the precaution of performing a hard disk backup before installing XCAP.
> A:SETUP
or
> B:SETUP
> Z:SETUP (replace Z with drive letter for your CD)
from the EPIX, Inc. ftp site.ftp.epixinc.com/software/xcap_v30/XCAPWIN32.EXE (for 32 bit Windows)
> XCAPWIN32.EXE (for 32 bit Windows) > XCAPWIN64.EXE (for 64 bit Windows)
PCITIPS.TXT
file provides the
PC Configuration Tips,
with tips for resolving hardware and software conflicts.
Command Line: InstallDir \ XCAPWXX
Name: XCAP
replacing
''InstallDir''
with the name of the installation directory chosen above.
Select
''OK''.
The printer port authorization key is approximately the size and shape of a printer cable's connector (5.5×4.5×1.6 cm), but having 25-pin connectors at both ends and no cable attached. If provided, connect the authorization key to any printer port. If a printer cable was attached to the printer port, reconnect the printer cable to the back of the authorization key. The authorization key will not affect normal printer operation.
Do not connect the printer port authorization key to a 25-pin serial (RS-232) port, or to any other interface that happens to use the same style connector; the authorization key will not function, might be permanently damaged, and the warranty will be void!
The USB port authorization key is approximately the size of a small finger (6.0×1.6×0.8 cm), having a USB standard 4-pin connector at one end. If provided, connect the authorization key to a USB port. Operating system support for USB devices is required; XCAP does not add USB support to the operating system.
The authorization key must remain attached, to the printer port or USB port as appropriate, while XCAP is running. If the authorization key is missing, or disconnected while XCAP is running, then XCAP-Plus, XCAP-Std or XCAP-Ltd, will behave similar to the XCAP-Lite version; selected image processing and analysis tools will not be operational.
> C:\XCAP\HARDLOCK\HLDINST -install
> CHDIR C:\XCAP\HARDLOCK
and execute:
HLDINST -install
to run the authorization key utility program.
Start
Settings
Control Panel
Add New Hardware
...
If the PIXCI® imaging board was not previously installed, the first time Windows starts after installation of the PIXCI® imaging board, Windows will notice the new device and inquire.
The first time Windows 95 starts after installation of the PIXCI® imaging board, a window titled ''New Hardware Found'' appears; select ''Driver from disk provided by hardware manufacturer'', click ''OK''. A window stating ''Insert the manufacturer's installation disk ...'', ''Copy manufacturer's files from ...'' appears; click ''Browse'' enter path Drivers\Win95\EPIXXCW5.INF (or EPIXXC32.INF for version 2.0 and earlier) within the chosen installation directory, typically C:\XCAP or C:\Program Files\EPIX\XCAP\XCAP, and click ''OK'', ''OK''. Do not accept the offer to ''Reboot''; a full shutdown and reboot is required. Some later releases of Windows 95 behave similar to Windows 98; the inquiries and responses may instead follow the steps below.
The first time Windows 98 starts after installation of the PIXCI® imaging board, a pop-up window with the message ''New PCI Multimedia Device'' will flash. A window stating ''The wizard searches for new driver for PCI Multimedia Video Device'' appears; click ''Next'', select ''Search for the best driver for your device'', click ''Next''. A window stating ''Windows will search for new driver ...'' and ''Specify Location'' appears; enter path Drivers\Win98\EPIXXCW5.INF (or EPIXXC32.INF for version 2.0 and earlier) within the chosen installation directory, typically C:\XCAP or C:\Program Files\EPIX\XCAP\XCAP, and click ''Next''. A window reports that a driver was found, namely ...\Drivers\Win98\EPIXXCW5.INF, click ''Next'' and ''Finish''.
The first time Windows ME starts after installation of the PIXCI® imaging board, a pop-up window with the message ''New PCI Multimedia Device'' will flash. A window stating ''Windows has found the following new hardware: PCI Multimedia Video Device'' appears; select ''Specify the location of the driver (Advanced)'', click ''Next'', select ''Search for the best driver for your device'', check box ''Specify a Location'', Enter path Drivers\WinME within the chosen installation directory, typically C:\XCAP or C:\Program Files\EPIX\XCAP\XCAP, and click ''Next''. A window reports that a driver was found, namely ...\Drivers\WinME\EPIXXCW5.INF, click ''Next'' and ''Finish''.
If the PIXCI® imaging board was already installed under Windows 95 or 98, and ''Cancel'' was clicked when Windows started and announced the presence of new ''PCI Multimedia Hardware'', then instruct Windows to load the appropriate driver. Click ''Start'', ''Control Panel'', ''System'', ''Device Manager'', and under ''Other Devices'' double-click ''PCI MultiMedia Video Device'' or ''PIXCI(R) Video Capture Board''. Select ''Driver'', ''Change Driver'', ''Other''. Select ''PCI MultiMedia Video Device'' or ''PIXCI(R) Video Capture Board'', select ''Have Disk'', enter path Drivers\Win95 (Drivers\Win98 may be used interchangeably) within the chosen installation directory, typically C:\XCAP or C:\Program Files\EPIX\XCAP\XCAP, and click ''OK''.
If the PIXCI® imaging board was already installed under Windows ME, and ''Cancel'' was clicked when Windows started and announced the presence of new ''PCI Multimedia Hardware'', then instruct Windows to load the appropriate driver. Click ''Start'', ''Settings'', ''Control Panel'', ''System'' (if ''System'' is not listed, click on ''View all Control Panel options''), ''Device Manager'' and under ''Other Devices'' double-click ''PCI MultiMedia Video Device'' or ''PIXCI(R) Video Capture Board''. Select ''Properties'', ''Driver'', ''Change Driver'' or ''Update Driver''. A window reporting ''This wizard searches for updated drivers for PCI MultiMedia Video Device'' or ''This wizard searches for updated drivers for PIXCI(R) Video Capture Board'' appears; select ''Specify the location of the driver (Advanced)'', ''Next'', ''Search for the best driver for your device'', ''Specify a Location'', enter path Drivers\WinME within the chosen installation directory, typically C:\XCAP or C:\Program Files\EPIX\XCAP\XCAP, and click ''Next'', ''Next'', ''Finish''.
SYSTEM.INI
file.
If additional frame buffer memory is desired, then
at the end of the Windows'
SYSTEM.INI
file,
add a section:
[EPIX_XC]
PIXCI=-IM <memorysize>
replacing the
''<memorysize>''
with the desired memory size in kBytes.
Windows must be rebooted for the new specification to take effect.
Windows 95, 98, and ME limits the maximum amount of allocatable frame buffer memory, dependent upon what other devices are installed, the total computer memory size, and other factors.
Windows may provide less frame buffer memory than was requested. If no memory could be allocated, the PIXCI® imaging board will not be usable; reporting ''Can't allocate frame buffer memory''. Otherwise, within XCAP, the amount of frame buffer memory can be checked under PIXCI®, PIXCI® Open/Close.
Use of EPIXXCW5.INF (or EPIXXC32.VXD for version 2.0 and earlier), above, provides automatic installation of EPIXXCW5.VXD (or EPIXXC32.VXD for version 2.0 and earlier) in most circumstances. The following information allows manual installation, correcting problems, or integration with an OEM's procedures.
C:\WINDOWS\SYSTEM
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Unknown\0000
replacing the \0000, if such an entry already exists,
with the next available sequential number.
This entry must contain:
DevLoader= "epixxc32.vxd" (for version 2.0-)
DevLoader= "epixxcw5.vxd" (for version 2.1+)
DriverDesc= "PIXCI(R) PCI Video Capture Board" (optional)
InfSection= "Unknown"
StaticVxD= "epixxc32.vxd" (for version 2.0-)
StaticVxD= "epixxcw5.vxd" (for version 2.1+)
or the existing entry for PIXCI® SV4:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_8086&DEV_1223\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_8086&DEV_1223&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entries for PIXCI® SV5, SV5A, or SV5B:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_109E&DEV_0350\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_109E&DEV_0350&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entries for PIXCI® SV6:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_109E&DEV_036E\BUS_**&DEV_**&FUNC_** (Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_109E&DEV_0878\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_109E&DEV_036E&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_109E&DEV_0878&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® D, PIXCI® D24, or PIXCI® D32:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_14F1&DEV_8800\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_14F1&DEV_8800&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® A:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_10E8&DEV_80D6\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_10E8&DEV_80D6&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® CL3SD:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_10E8&DEV_82B1\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_10E8&DEV_82B1&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® CL3SD:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_C300\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_C300&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® CL1:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_C301\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_C301&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® CL1:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_C100\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_C100&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® CL2:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_C10A\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_C10A&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® D2X:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_C200\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_C200&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® D2X:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_D200\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_D200&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® D2X:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_D201\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_D201&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® D3X:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_D20A\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_D20A&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® E1:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_D300\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_D300&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® E1:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_E001\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_E001&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® E4:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_E0A1\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_E0A1&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® E1DB:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_E004\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_E004&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® E1DB:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_ED01\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_ED01&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® E4DB:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_EDA1\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_EDA1&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® EB1:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_ED04\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_ED04&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® EC1:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_EB01\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_EB01&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® ECB1:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_EC01\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_EC01&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® EL1:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_ECB1\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_ECB1&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® EL1:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_F001\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_F001&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® EL1:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_F0A1\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_F0A1&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® EL1DB:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_F0F1\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_F0F1&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® EL1DB:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_FD01\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_FD01&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® SI:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_FDF1\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_FDF1&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® SI:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_C000\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_C000&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
or the existing entry for PIXCI® SI4:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_C001\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_C001&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
where the **'s may be any digits (assigned and created by Windows after detection of the PIXCI® imaging board).[2] This entry must contain:(Win 95) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_C004\BUS_**&DEV_**&FUNC_** (Win 98) HKEY_LOCAL_MACHINE\Enum\PCI\VEN_165A&DEV_C004&SUBSYS_00000000&REV_**\BUS_**&DEV_**&FUNC_**
Class= "Unknown"
ConfigFlags= 00 00 00 00
DeviceDesc= "PIXCI(R) PCI Video Capture Board" (optional)
Driver= "Unknown\0000" (substitute 0000)
Mfg= "EPIX, Inc." (optional)
where the
''0000''
is replaced by the sequential number used in the previous step.
As described above, frame buffer memory allocated by EPIXXCW5.VXD (or EPIXXC32.VXD for version 2.0 and earlier) during Windows startup is limited to a small percentage of total computer memory.
A larger frame buffer memory can often be obtained by reserving memory before Windows starts:
DEVICE=C:\XCAP\Drivers\Win95\EPIXXC.SYS -IM <framebuffermemorysize>
or
DEVICE=C:\XCAP\Drivers\Win95\EPIXXC.SYS -OS <reservememorysize>
after
DEVICE=HIMEM.SYS,
replacing
''<framebuffermemorysize>''
with the desired frame buffer memory size, in kBytes.
Alternately, the second form reserves
''<reservememorysize>''
kBytes,
for Windows and allocates (almost) all of the remaining memory
for use as frame buffer memory.
[EPIX_XC]
PIXCI=-IM 0
so that
EPIXXCW5.VXD
(or
EPIXXC32.VXD
for version 2.0 and earlier)
doesn't reserve and then waste additional frame buffer memory.
This technique allows most of the computer's memory to be reserved as frame buffer memory (e.g. typically all but 8 or 16 MBytes, as required by Windows). However, the memory is unavailable to Windows, even when the PIXCI® imaging board's driver is not open.
If the specified amount of frame buffer memory could not be allocated,
EPIXXC.SYS
will attempt to allocate smaller amounts.
If no memory can be allocated
EPIXXC.SYS,
will display an error message during Windows startup,
and the PIXCI® imaging board will not be available, stating
''Can't allocate frame buffer memory''.
This alternate frame buffer allocation method is not available under Windows ME.
As described above, frame buffer memory allocated by EPIXXCW5.VXD during Windows startup is limited to a small percentage of total computer memory.
A larger frame buffer memory can be obtained by limiting the amount of memory recognized by Windows ME, and then instructing EPIXXCW5.VXD to explicitly use a section of memory without allocating it from Windows:
[386Enh]
MaxPhysPage=4000 ;; 64 MByte in 4096 byte pages, in hexadecimal
[EPIX_XC]
PIXCI= -IA <image_memory_adrs_in_kByte>
-IM <size_of_image_memory_in_kByte>
-MB <image_memory_partition_size_in_kByte>
In practice, all three fields are on the same line.
The -MB partition size specifies the size into which image memory is partitioned for the sake of virtual memory management: (a) Each frame buffer must be completely contained within a partition, (b) A value of 0 specifies that the entire image memory is to be handled as one partition, and (c) The maximum number of partitions is 256 under 32 bit operating systems. For most systems, a value of 8192 or 16384 is suggested; though the value need not be a power of two. Systems with very high resolution cameras using large frame buffers should choose the partition size carefully, so as to minimize the unusable memory remaining, smaller than a frame buffer, at the end of each partition.
When using more than 1 or 2 GBytes of image memory, it may be necessary to append:
-MU 0x01
to the
''PIXCI''
field, conserving system memory mapping resources by not mapping the
image memory directly into the application program's space.
It may also be necessary
to append:
-MU 0x03
which additionally conserves system resources by mapping memory only on demand.
Be careful that the -IA address is equal to (or above) the specified /MaxPhysPage limit - including exact base2 to base10 conversions! (i.e. for MaxPhysPage=4000 or 64 MByte, the smallest valid value of -IA is 65536, not 64000!). Likewise, be certain that the -IA plus -IM values do not exceed the amount of memory available!
For example, for a computer with 256 MByte of memory, allocating 192 MByte for Windows and the remainder for frame buffer memory, use:
MaxPhysPage=C000
and
PIXCI = -IA 196608 -IM 65536 -MB 16384
Use of HLDINST.EXE, as described above, provides automatic installation of the printer port authorization key's driver, needed under Windows 95, 98, and ME, for XCAP-Plus, XCAP-Std, and XCAP-Ltd (but not needed for XCAP-Lite). The following information allows manual installation, correcting problems, or integration with an OEM's procedures for the printer port version of authorization keys.
HARDLOCK.VXD
must be copied to
the Windows
SYSTEM
directory, typically:
C:\WINDOWS\SYSTEM
or placed within the XCAP installation directory, typically:
C:\XCAP\PROGRAM
AUTOEXEC.BAT,
specifying:
SET HL_SEARCH=378p
SET HL_SEARCH=278p,378p
forces only the I/O port addresses listed (in hexadecimal)
to be searched.
Note that setting HL_SEARCH from a DOS box has no effect,
as the setting is not
''carried back''
from DOS into the Windows 95, 98, or ME environment.
XCAP requires Windows NT Version 4 with Service Pack 3 or later. You must be logged on as Administrator, or have equivalent privileges, to complete the installation procedure.
> A:SETUP
or
> B:SETUP
> Z:SETUP (replace Z with drive letter for your CD)
from the EPIX, Inc. ftp site.ftp.epixinc.com/software/xcap_v30/XCAPWIN32.EXE (for 32 bit Windows)
> XCAPWIN32.EXE (for 32 bit Windows) > XCAPWIN64.EXE (for 64 bit Windows)
PCITIPS.TXT
file provides the
PC Configuration Tips,
with tips for resolving hardware and software conflicts.
Command Line: InstallDir \ XCAPWXX
Name: XCAP
replacing
''InstallDir''
with the name of the installation directory chosen above.
Select
''OK''.
The printer port authorization key is approximately the size and shape of a printer cable's connector (5.5×4.5×1.6 cm), but having 25-pin connectors at both ends and no cable attached. If provided, connect the authorization key to any printer port. If a printer cable was attached to the printer port, reconnect the printer cable to the back of the authorization key. The authorization key will not affect normal printer operation.
Do not connect the printer port authorization key to a 25-pin serial (RS-232) port, or to any other interface that happens to use the same style connector; the authorization key will not function, might be permanently damaged, and the warranty will be void!
The USB port authorization key is approximately the size of a small finger (6.0×1.6×0.8 cm), having a USB standard 4-pin connector at one end. If provided, connect the authorization key to a USB port. Operating system support for USB devices is required; XCAP does not add USB support to the operating system.
The authorization key must remain attached, to the printer port or USB port as appropriate, while XCAP is running. If the authorization key is missing, or disconnected while XCAP is running, then XCAP-Plus, XCAP-Std or XCAP-Ltd, will behave similar to the XCAP-Lite version; selected image processing and analysis tools will not be operational.
> C:\XCAP\HARDLOCK\HLDINST -install
> CHDIR C:\XCAP\HARDLOCK
and execute:
HLDINST -install
to run the authorization key utility program.
Use of EPIXXCWT.INF (or EPIXXCNT.INF for version 2.0 and earlier), above, provides automatic installation of EPIXXCWT.SYS (or EPIXXCNT.SYS for version 2.0 and earlier) in most circumstances. The following information allows manual installation, correcting problems, or integration with an OEM's procedures.
C:\WINNT\SYSTEM32\DRIVERS
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EPIXXCWT (version 2.1+)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EPIXXCNT (version 2.0-)
This entry must contain:
ErrorControl = 0x00000001
Group = "Extended base"
Start = 0x00000001
Type = 0x00000001
and may, as described below, also contain:
PIXCI = "-IM <memorysize>"
Create an entry such as:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\System\EPIXXCWT (version 2.1+)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\System\EPIXXCNT (version 2.0-)
This entry must contain:
EventMessageFile = "%SystemRoot%\System32\IoLogMsg.dll"
TypesSupported = 0x00000007
Under Windows NT, frame buffer memory must be allocated during Windows' initialization.
The requested frame buffer memory size must be specified in the Registry entry described above, using an entry named ''PIXCI'', such as:
PIXCI = "-IM <memorysize>"
replacing the
''<memorysize>''
with the desired memory size in kBytes.
If no frame buffer memory size is specified,
a default size of 32768 kBytes is used.
Windows must be rebooted for the new specification to take effect.
Optionally,
"-MB <memory_partition_size>"
specifies that the requested
"-IM <memorysize>"
is to be allocated in blocks or partitions of the stated size.
Requesting memory partitioned into blocks may allow receiving
more memory that would be available as a single block.
However,
(a) Each frame buffer must be completely contained within a partition, and
(b) The maximum number of partitions is 256 under 32 bit operating systems.
Systems with very high resolution cameras using large frame buffers
should choose the partition size carefully, so as to minimize
the unusable memory remaining, smaller than a frame buffer, at the end of each partition.
For the PIXCI® CL3SD, which has on-board frame buffer memory, memory reserved by the -IM parameter is needed only for support of time stamping of captured frames, such as optionally used by XCAP's Capture - Video to Frame Buffers. Currently, 64 bytes are needed for each frame buffer's status.
Windows NT limits the maximum amount of allocatable frame buffer memory, dependent upon what other devices are installed, the total computer memory size, and other factors. Using the Control Panel's Device Manager to select Boot or System priority startup for EPIXXCWT.SYS (or EPIXXCNT.SYS for version 2.0 and earlier) allows more frame buffer memory to be allocated than selection of Automatic startup.
Windows may provide less frame buffer memory than was requested. If no memory could be allocated, the PIXCI® imaging board will not be available, stating ''Can't allocate frame buffer memory''. Otherwise, within XCAP, the number of available frame buffers can be checked under PIXCI®, PIXCI® Video Setup, Resolution. As the frame buffer memory is allocated once during Windows initialization; the contents of frame buffers are retained as XCAP is closed and restarted, but lost if Windows is restarted.
As described above, frame buffer memory allocated by EPIXXCWT.SYS (or EPIXXCNT.SYS for version 2.0 and earlier) during Windows startup may be limited to a small percentage of total computer memory.
A larger frame buffer memory can be obtained by limiting the amount of memory recognized by Windows NT, and then instructing EPIXXCWT.SYS (or EPIXXCNT.SYS for version 2.0 and earlier) to explicitly use a section of memory without allocating it from Windows NT:
[operating systems]
multi(0)disk(0)rdisk(0)partition(7)\WINNT="Windows NT V 4.00"
to:
[operating systems]
multi(0)disk(0)rdisk(0)partition(7)\WINNT="Windows NT V 4.00 [NT=64M PIXCI=256M]" /MAXMEM=64
multi(0)disk(0)rdisk(0)partition(7)\WINNT="Windows NT V 4.00"
Do
not
copy this new line as shown above; the first portion of the line must be
copied from an existing configuration line in
your
C:\BOOT.INI
file.
The text between quotes appears as a boot selection prompt,
use of
''[NT=64M PIXCI=256M]''
is a suggested reminder, but not required.
Also in C:\BOOT.INI, change the timeout selection to be greater than 0:
[boot loader]
timeout=30
Otherwise the BOOT.INI configuration options will not be shown when Windows starts.
Keeping the original configuration line, as a boot selection option, is highly recommended as a backup.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EPIXXCWT (version 2.1+)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EPIXXCNT (version 2.0-)
On the
''PIXCI''
field add:
-IA <image_memory_adrs_in_kByte>
-IM <size_of_image_memory_in_kByte>
-MB <image_memory_partition_size_in_kByte>
-BH <size_of_BIOS_hole_below_4GB_in_kByte>
In practice, all four fields are on the same line.
The -MB partition size specifies the size into which image memory is partitioned for the sake of virtual memory management: (a) Each frame buffer must be completely contained within a partition, (b) A value of 0 specifies that the entire image memory is to be handled as one partition, and (c) The maximum number of partitions is 256 under 32 bit operating systems. For most systems, a value of 8192 or 16384 is suggested; though the value need not be a power of two. Systems with very high resolution cameras using large frame buffers should choose the partition size carefully, so as to minimize the unusable memory remaining, smaller than a frame buffer, at the end of each partition.
When using more than 1 or 2 GBytes of image memory, it may be necessary to append:
-MU 0x01
to the
''PIXCI''
field, conserving system memory mapping resources by not mapping the
image memory directly into the application program's space.
It may also be necessary
to append:
-MU 0x03
which additionally conserves system resources by mapping memory only on demand.
Be careful that the -IA address is equal to (or above) the specified /MAXMEM limit - including exact base2 to base10 conversions! (i.e. for /MAXMEM=64, the smallest valid value of -IA is 65536, not 64000!). Likewise, be certain that the -IA plus -IM values do not exceed the amount of memory available!
On a computer populated with 4 or more GBytes of memory, some of the memory directly below the 4 GByte address overlaps other hardware resources such as BIOS, memory mapped I/O, PCI configuration space, etc.[5] and is unavailable to either the operating system or for use as frame buffers. The usable frame buffer memory is therefore reduced by the amount by which the -IA address up to the -IA address plus -IM size overlap the 4 GByte address minus -BH size up to the 4 GByte address. The -BH size may be set to 0 (or not specified) if the computer has significantly less than 4 GBytes of memory.
For example, for a computer with 1 GByte of memory, allocating 256 MByte for Windows and the remainder for frame buffer memory, use:
/MAXMEM=256
in C:\BOOT.INI, and use:
PIXCI = -IA 262144 -IM 786432 -MB 8192
in the registry entry.
Note that 262144 is 256×1024,
and 786432 is (1024-256)×1024.
Note that if this memory allocation method is used, program access to image data may be slower. Thus, the video display rate (and image processing) may be slower, but the video capture rate (such as sequence capture) is not adversely affected. This method of memory allocation is primarily used for video rate acquisition of long sequences, followed by off-line analysis or saving of the sequence.
Use of HLDINST.EXE, as described above, provides automatic installation of the printer port authorization key's driver, needed under Windows NT, for XCAP-Plus, XCAP-Std, and XCAP-Ltd (but not needed for XCAP-Lite). The following information allows manual installation, correcting problems, or integration with an OEM's procedures for the printer port version of authorization keys.
C:\WINNT\SYSTEM32\DRIVERS
C:\WINNT\SYSTEM
or placed within the XCAP installation directory, typically:
C:\XCAP\PROGRAM
or
C:\Program Files\EPIX\XCAP\XCAP\PROGRAM
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HardLock
This key must contain values:
ErrorControl = 0x00000001
Group = "Extended Base"
Start = 0x00000002
Type = 0x00000001
or, if using REGEDT32, the values should appear as:
ErrorControl:REG_DWORD:0x1
Group:REG_SZ:ExtendedBase
Start:REG_DWORD:0x2
Type:REG_DWORD:0x1
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HardLock\Parameters
which contains a value:
IoPortAddress0 = 0x???? (for REGEDIT)
IoPortAddress0:REG_DWORD:0x???? (for REGEDT32)
where the
''????''
is replaced with the parallel port's I/O address in hexadecimal.
As before, Windows must be shut down and restarted.
> A:SETUP
or
> B:SETUP
> Z:SETUP (replace Z with drive letter for your CD)
from the EPIX, Inc. ftp site.ftp.epixinc.com/software/xcap_v30/XCAPWIN32.EXE (for 32 bit Windows)
> XCAPWIN32.EXE (for 32 bit Windows) > XCAPWIN64.EXE (for 64 bit Windows)
PCITIPS.TXT
file provides the
PC Configuration Tips,
with tips for resolving hardware and software conflicts.
Command Line: InstallDir \ XCAPWXX
Name: XCAP
replacing
''InstallDir''
with the name of the installation directory chosen above.
Select
''OK''.
The printer port authorization key is approximately the size and shape of a printer cable's connector (5.5×4.5×1.6 cm), but having 25-pin connectors at both ends and no cable attached. If provided, connect the authorization key to any printer port. If a printer cable was attached to the printer port, reconnect the printer cable to the back of the authorization key. The authorization key will not affect normal printer operation.
Do not connect the printer port authorization key to a 25-pin serial (RS-232) port, or to any other interface that happens to use the same style connector; the authorization key will not function, might be permanently damaged, and the warranty will be void!
The USB port authorization key is approximately the size of a small finger (6.0×1.6×0.8 cm), having a USB standard 4-pin connector at one end. If provided, connect the authorization key to a USB port. Operating system support for USB devices is required; XCAP does not add USB support to the operating system.
The authorization key must remain attached, to the printer port or USB port as appropriate, while XCAP is running. If the authorization key is missing, or disconnected while XCAP is running, then XCAP-Plus, XCAP-Std or XCAP-Ltd, will behave similar to the XCAP-Lite version; selected image processing and analysis tools will not be operational.
> C:\XCAP\HARDLOCK\HLDINST -install
> CHDIR C:\XCAP\HARDLOCK
and execute:
HLDINST -install
to run the authorization key utility program.
If the PIXCI® imaging board was not previously installed, the first time Windows starts after installation of the PIXCI® imaging board, Windows will notice the new device and inquire.
The first time Windows 2000 starts after installation of the PIXCI® imaging board, a pop-up window with the message "Multimedia Video Controller" will flash. A window stating ''Welcome to the Found New Hardware Wizard'' appears; click ''Next'', select ''Search for the best driver for your device'', click ''Next'', check box ''Specify a location'', enter path Drivers\Win2K within the chosen installation directory, typically C:\XCAP or C:\Program Files\EPIX\XCAP\XCAP, and click ''Next''. A window reports that a driver was found, namely ...\Drivers\Win2K\EPIXXCW2.INF; click ''Next''. A window reports that Microsoft's ''Digital Signature was not found''; click ''Yes''. A window states ''Completing the Found New Hardware Wizard'' and ''This device is not configured correctly. (Code 1)'' (this error indicates that the newly installed driver will be functional only after a reboot); click ''Finish'' and restart Windows.
If the PIXCI® imaging board was already installed, and ''Cancel'' was clicked when Windows started and announced the presence of a new ''Multimedia Video Controller'', then instruct Windows to load the appropriate driver. Click ''Start'', ''Settings'', ''Control Panel'', ''System'' (if ''System'' is not listed, click on ''View all Control Panel options''), ''Device Manager'', and under ''Other Devices'' or ''Imaging Devices'' double-click ''PCI MultiMedia Video Device'' or ''PIXCI(R) Video Capture Board''. Click ''Properties'', ''Driver'', ''Change Driver'' or ''Update Driver''. A window stating ''Welcome'' appears; click ''Next''. A window stating ''This wizard searches for updated drivers for: PCI MultiMedia Video Device'' or ''This wizard searches for updated drivers for: PIXCI(R) Video Capture Board'' appears; select ''Search for a suitable driver for my device (recommended)'', click ''Next'', select ''Specify a Location'', enter path Drivers\Win2K within the chosen installation directory, typically C:\XCAP or C:\Program Files\EPIX\XCAP\XCAP, and click ''Next'', ''Next''. A window reports that Microsoft's: ''Digital Signature was not found''; click ''Yes''. A window reports ''This device is not configured correctly. (Code 1)'' (this error indicates that the newly installed driver will be functional only after a reboot); click ''Finish'' and restart Windows.
Use of EPIXXCW2.INF (or EPIXXCNT.INF for version 2.0 and earlier), above, provides automatic installation of EPIXXCW2.SYS (or EPIXXCNT.SYS for version 2.0 and earlier) in most circumstances. The following information allows manual installation, correcting problems, or integration with an OEM's procedures.
C:\WINNT\SYSTEM32\DRIVERS
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EPIXXCW2 (version 2.1+)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EPIXXCNT (version 2.0-)
This entry must contain:
ErrorControl = 0x00000001
Group = "Extended base"
Start = 0x00000001
Type = 0x00000001
and may, as described below, also contain:
PIXCI = "-IM <memorysize>"
Create an entry such as:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\System\EPIXXCW2 (version 2.1+)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\System\EPIXXCNT (version 2.0-)
This entry must contain:
EventMessageFile = "%SystemRoot%\System32\IoLogMsg.dll"
TypesSupported = 0x00000007
Under Windows 2000, the Windows NT driver EPIXXCWT.SYS can be, and was previously, used instead of EPIXXCW2.SYS. In contrast to EPIXXCWT.SYS, the EPIXXCW2.SYS is Plug & Play compatible.
Under Windows 2000 frame buffer memory must be allocated during Windows' initialization.
The requested frame buffer memory size must be specified in the Registry entry described above, using an entry named ''PIXCI'', such as:
PIXCI = "-IM <memorysize>"
replacing the
''<memorysize>''
with the desired memory size in kBytes.
If no frame buffer memory size is specified,
a default size of 32768 kBytes is used.
Windows must be rebooted for the new specification to take effect.
Optionally,
"-MB <memory_partition_size>"
specifies that the requested
"-IM <memorysize>"
is to be allocated in blocks or partitions of the stated size.
Requesting memory partitioned into blocks may allow receiving
more memory that would be available as a single block.
However,
(a) Each frame buffer must be completely contained within a partition, and
(b) The maximum number of partitions is 256 under 32 bit operating systems.
Systems with very high resolution cameras using large frame buffers
should choose the partition size carefully, so as to minimize
the unusable memory remaining, smaller than a frame buffer, at the end of each partition.
For the PIXCI® CL3SD, which has on-board frame buffer memory, memory reserved by the -IM parameter is needed only for support of time stamping of captured frames, such as optionally used by Capture - Video to Frame Buffers. Currently, 64 bytes are needed for each frame buffer's status.
Windows 2000 limits the maximum amount of allocatable frame buffer memory, dependent upon what other devices are installed, the total computer memory size, and other factors. Under Windows 2000, the maximum amount of memory that can be allocated by this method is typically limited to 64 or 92 MByte.
Windows may provide less frame buffer memory than was requested. If no memory could be allocated, the PIXCI® imaging board will not be available, stating ''Can't allocate frame buffer memory''. Otherwise, within XCAP, the number of available frame buffers can be checked under PIXCI®, PIXCI® Video Setup, Resolution. As the frame buffer memory is allocated once during Windows initialization; the contents of frame buffers are retained as XCAP is closed and restarted, but lost if Windows is restarted.
As described above, frame buffer memory allocated by EPIXXCW2.SYS for Windows 2000, during Windows startup may be limited to a small percentage of total computer memory; typically 64 to 96 MByte.
A larger frame buffer memory can be obtained by limiting the amount of memory recognized by Windows and then instructing EPIXXCW2.SYS for Windows 2000 to explicitly use a section of memory without allocating it from Windows 2000:
[operating systems]
multi(0)disk(0)rdisk(0)partition(7)\WINNT="Windows 2000"
to:
[operating systems]
multi(0)disk(0)rdisk(0)partition(7)\WINNT="Windows 2000 [NT=64M PIXCI=256M]" /MAXMEM=64
multi(0)disk(0)rdisk(0)partition(7)\WINNT="Windows 2000"
Do
not
copy this new line as shown above; the first portion of the line must be
copied from an existing configuration line in
your
C:\BOOT.INI
file.
The text between quotes appears as a boot selection prompt,
use of
''[NT=64M PIXCI=256M]''
is a suggested reminder, but not required.
Also in C:\BOOT.INI, change the timeout selection to be greater than 0:
[boot loader]
timeout=30
Otherwise the
BOOT.INI
configuration options will not be shown when Windows starts.
Keeping the original configuration line, as a boot selection option, is highly recommended as a backup.
Under Windows XP, the
BOOTCFG
command, provided with Windows, can be used to
change the
BOOT.INI
file
instead of manual editing.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EPIXXCW2
On the
''PIXCI''
field add:
-IA <image_memory_adrs_in_kByte>
-IM <size_of_image_memory_in_kByte>
-MB <image_memory_partition_size_in_kByte>
-BH <size_of_BIOS_hole_below_4GB_in_kByte>
In practice, all four fields are on the same line.
The -MB partition size specifies the size into which image memory is partitioned for the sake of virtual memory management: (a) Each frame buffer must be completely contained within a partition, (b) A value of 0 specifies that the entire image memory is to be handled as one partition, and (c) The maximum number of partitions is 256 under 32 bit operating systems. For most systems, a value of 8192 or 16384 is suggested; though the value need not be a power of two. Systems with very high resolution cameras using large frame buffers should choose the partition size carefully, so as to minimize the unusable memory remaining, smaller than a frame buffer, at the end of each partition.
When using more than 1 or 2 GBytes of image memory, it may be necessary to append:
-MU 0x01
to the
''PIXCI''
field, conserving system memory mapping resources by not mapping the
image memory directly into the application program's space.
It may also be necessary
to append:
-MU 0x03
which additionally conserves system resources by mapping memory only on demand.
Be careful that the -IA address is equal to (or above) the specified /MAXMEM limit - including exact base2 to base10 conversions! (i.e. for /MAXMEM=64, the smallest valid value of -IA is 65536, not 64000!). Likewise, be certain that the -IA plus -IM values do not exceed the amount of memory available!
On a computer populated with 4 or more GBytes of memory, some of the memory directly below the 4 GByte address overlaps other hardware resources such as BIOS, memory mapped I/O, PCI configuration space, etc.[7] and is unavailable to either the operating system or for use as frame buffers. The usable frame buffer memory is therefore reduced by the amount by which the -IA address up to the -IA address plus -IM size overlap the 4 GByte address minus -BH size up to the 4 GByte address. The -BH size may be set to 0 (or not specified) if the computer has significantly less than 4 GBytes of memory.
For example, for a computer with 1 GByte of memory, allocating 256 MByte for Windows and the remainder for frame buffer memory, use:
/MAXMEM=256
in
C:\BOOT.INI,
and use:
PIXCI = -IA 262144 -IM 786432 -MB 8192
in the registry entry.
Note that 262144 is 256×1024,
and 786432 is (1024-256)×1024.
Note that if this memory allocation method is used, program access to image data may be slower. Thus, the video display rate (and image processing) may be slower, but the video capture rate (such as sequence capture) is not adversely affected. This method of memory allocation is primarily used for video rate acquisition of long sequences, followed by off-line analysis or saving of the sequence.
Use of HLDINST.EXE, as described above, provides automatic installation of the printer port authorization key's driver, needed under Windows 2000 for XCAP-Plus, XCAP-Std, and XCAP-Ltd (but not needed for XCAP-Lite). The following information allows manual installation, correcting problems, or integration with an OEM's procedures for the printer port version of authorization keys.
C:\WINNT\SYSTEM32\DRIVERS
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HardLock
This key must contain values:
ErrorControl = 0x00000001
Group = "Extended Base"
Start = 0x00000002
Type = 0x00000001
or, if using REGEDT32, the values should appear as:
ErrorControl:REG_DWORD:0x1
Group:REG_SZ:ExtendedBase
Start:REG_DWORD:0x2
Type:REG_DWORD:0x1
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HardLock\Parameters
which contains a value:
IoPortAddress0 = 0x???? (for REGEDIT)
IoPortAddress0:REG_DWORD:0x???? (for REGEDT32)
where the
''????''
is replaced with the parallel port's I/O address in hexadecimal.
As before, Windows must be shut down and restarted.
Command Line: InstallDir \ XCAPWXX
Name: XCAP
replacing
''InstallDir''
with the name of the installation directory chosen above.
Select
''OK''.
The printer port authorization key is approximately the size and shape of a printer cable's connector (5.5×4.5×1.6 cm), but having 25-pin connectors at both ends and no cable attached. If provided, connect the authorization key to any printer port. If a printer cable was attached to the printer port, reconnect the printer cable to the back of the authorization key. The authorization key will not affect normal printer operation.
Do not connect the printer port authorization key to a 25-pin serial (RS-232) port, or to any other interface that happens to use the same style connector; the authorization key will not function, might be permanently damaged, and the warranty will be void!
The USB port authorization key is approximately the size of a small finger (6.0×1.6×0.8 cm), having a USB standard 4-pin connector at one end. If provided, connect the authorization key to a USB port. Operating system support for USB devices is required; XCAP does not add USB support to the operating system.
The authorization key must remain attached, to the printer port or USB port as appropriate, while XCAP is running. If the authorization key is missing, or disconnected while XCAP is running, then XCAP-Plus, XCAP-Std or XCAP-Ltd, will behave similar to the XCAP-Lite version; selected image processing and analysis tools will not be operational.
> C:\XCAP\HARDLOCK\HLDINST -install
> CHDIR C:\XCAP\HARDLOCK
and execute:
HLDINST -install
to run the authorization key utility program.
If the PIXCI® imaging board was not previously installed, the first time Windows starts after installation of the PIXCI® imaging board, Windows will notice the new device and inquire.
The first time Windows XP or XP(x64) starts after installation of the PIXCI® imaging board, a pop-up window with the message ''Multimedia Video Controller'' will flash. A window stating ''Welcome to the Found New Hardware Wizard'' appears; select ''Install from a list or a specific location. (Advanced)'', click ''Next'', select ''Search for the best driver in these locations'', uncheck box ''Search removable storage media'', check box ''Include this location in the search'', enter path Drivers\WinXP for Windows XP, or Drivers\WinXP64 for Windows XP(x64), within the chosen installation directory typically C:\XCAP or C:\Program Files\EPIX\XCAP\XCAP, and click ''Next''. A window reports that a driver was found, namely ...\Drivers\WinXP\EPIXXCW2.INF, Or ...\Drivers\WinXP64\EPIXXCW6.INF for Windows XP(x64), click ''Next''. A window states ''The software that you are installing for ... has not passed compatibility testing''; click ''Continue Anyway''. A window states ''Completing the Found New Hardware Wizard'' and ''The hardware you installed will not work until you restart your computer''; click ''Finish'' and restart Windows.
If the PIXCI® imaging board was already installed, and ''Cancel'' was clicked when Windows started and announced the presence of a new ''Multimedia Video Controller'', then instruct Windows to load the appropriate driver. Click ''Start'', ''Control Panel'', ''Performance and Maintenance'', ''System'', ''Hardware'', ''Device Manager'', and under ''Other Devices'' or ''Imaging Devices'' double-click ''PCI MultiMedia Video Device'' or ''PIXCI(R) Video Capture Board'' (the latter appears if a PIXCI® imaging board driver was previously installed). Click ''Properties'', ''Driver'', ''Change Driver'' or ''Update Driver''. A ''Welcome'' window appears; select ''Install from a list or a specific location. (Advanced)'', click ''Next'', select ''Search for the best driver in these locations'', uncheck ''Search removable storage media'', check ''Include this location in the search'', enter path Drivers\WinXP for Windows XP, or Drivers\WinXP64 for Windows XP(x64), within the chosen installation directory typically C:\XCAP or C:\Program Files\EPIX\XCAP\XCAP, and click ''Next'', ''Next''. A window reports ''The software that you are installing for ... has not passed compatibility testing''; click ''Continue Anyway''. A window reports ''The hardware you installed will not work until you restart your computer''; click ''Finish'' and restart Windows.
Use of EPIXXCW2.INF or EPIXXCW6.INF, above, provides automatic installation of EPIXXCW2.SYS or EPIXXCW6.SYS in most circumstances. The following information allows manual installation, correcting problems, or integration with an OEM's procedures.
C:\WINDOWS\SYSTEM32\DRIVERS
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EPIXXCW2
for Windows XP
or
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EPIXXCW6
for Windows XP(x64).
This entry must contain:
ErrorControl = 0x00000001
Group = "Extended base"
Start = 0x00000001
Type = 0x00000001
and may, as described below, also contain:
PIXCI = "-IM <memorysize>"
Create an entry such as:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\System\EPIXXCW2
for Windows XP
or
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\System\EPIXXCW6
for Windows XP(x64).
This entry must contain:
EventMessageFile = "%SystemRoot%\System32\IoLogMsg.dll"
TypesSupported = 0x00000007
Under Windows XP or XP(x64), frame buffer memory must be allocated during Windows' initialization.
The requested frame buffer memory size must be specified in the Registry entry described above, using an entry named ''PIXCI'', such as:
PIXCI = "-IM <memorysize>"
replacing the
''<memorysize>''
with the desired memory size in kBytes.
If no frame buffer memory size is specified,
a default size of 32768 kBytes is used.
Windows must be rebooted for the new specification to take effect.
Optionally,
"-MB <memory_partition_size>"
specifies that the requested
"-IM <memorysize>"
is to be allocated in blocks or partitions of the stated size.
Requesting memory partitioned into blocks may allow receiving
more memory that would be available as a single block.
However,
(a) Each frame buffer must be completely contained within a partition, and
(b) The maximum number of partitions is 256 under 32 bit operating systems,
the maximum number of partitions is 256 under 64 bit operating systems.
Systems with very high resolution cameras using large frame buffers
should choose the partition size carefully, so as to minimize
the unusable memory remaining, smaller than a frame buffer, at the end of each partition.
For the PIXCI® CL3SD, which has on-board frame buffer memory, memory reserved by the -IM parameter is needed only for support of time stamping of captured frames, such as optionally used by Capture - Video to Frame Buffers. Currently, 64 bytes are needed for each frame buffer's status.
Windows XP or XP(x64), limits the maximum amount of allocatable frame buffer memory, dependent upon what other devices are installed, the total computer memory size, and other factors. Under Windows XP the maximum amount of memory that can be allocated by this method is typically limited to 512 MByte, but not more than half of the physical memory. Under Windows XP(x64), the typical amount of allocated memory has not yet been determined.
Windows may provide less frame buffer memory than was requested. If no memory could be allocated, the PIXCI® imaging board will not be available, stating ''Can't allocate frame buffer memory''. Otherwise, within XCAP, the number of available frame