USER'S MANUAL

PIXCI® D3X for
Dalsa CA-D6 & CT-P1

Revision 1

24 January 2007

For use with:
PIXCI® D3X Rev. 2 or 3



Copyright © 2007 EPIX, Inc.
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: 14-Jul-2008

Table of Contents


 

 

 

1. Installation

Thank you for purchasing imaging products from EPIX, Inc. We are available via the Internet, FAX, and telephone to help with installation or to answer questions about the use of our products for your application.

The PIXCI® D3X imaging board, for the PCI bus, is packed in a static dissipative bag. Please keep the bag and box in which the board was shipped should the need arise to return the board. Prior to opening the bag, place the bag near the PC into which the board will be installed.

We recommend installing XCAP 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.

  1. Turn off the power and remove the cover from the PC into which the PIXCI imaging board is to be installed.

  2. Select a vacant PCI bus slot and remove the metal bracket and screw covering the back panel slot with which it is aligned. Consult the reference manual for the PC if there is any doubt about which slot is a PCI bus slot.

  3. Use of a static free area and a wrist strap connected to the PC or to the static free area is suggested during installation. Walking can generate static electricity. Keep your feet stationary while removing the PIXCI imaging board from the anti-static bag. Hold the bag and the PC at the same time, or place the bag on the PC chassis and hold the chassis to dissipate the static charge that may have been created while transporting the board to the PC.

  4. Remove the PIXCI imaging board from the anti-static bag and insert it into the PCI bus connector. This can require up to 15 pounds of force. Do not use too much force as the board may not be inserted into the connector correctly, and the result can be damage to the connector and the board. Consult the reference manual for the PC if there is any doubt about which slot is a PCI bus slot. Note that some computers have 3.3 volt PCI bus slots or may have 64 bit, 66 MHz PCI slots. The PIXCI D3X board may be installed in 3.3 volt and 66 MHz PCI slots. When the PIXCI D3X board is installed in a 66 MHz slot, other cards installed in 66 MHz slots will not be operate faster than 33 MHz.

  5. Replace the screw to secure the PIXCI imaging board in the slot.

  6. Remove the power from all equipment to be connected.

  7. Connect the cable(s) between the PIXCI, camera, and power supply. The PIXCI end of the cable has a 68 or 100 pin SCSI style subminiature D connector. Do not plug it into a SCSI card. Connect the other end of the cable into the labelled camera connectors.

  8. Power up the camera, PC, and monitor(s).

  9. Operate XCAP by following the instructions in the Software Installation and Getting Started chapters in this manual.

  10. Check for display of video on the VGA monitor by clicking on the Capture and then the Snap menu in the View window or by using the shortcut menu.

  11. Note that for line scan cameras, either an external vertical drive signal or the ''Internal'' vertical drive selection must be used.

  12. If there is no video displayed, check for the presence of vertical drive by clicking on ''PIXCI,'' ''PIXCI Status,'' and ''PIXCI-Unit x Status'' (where x is the number of the board being used). The number reported in the ''Vertical Sync Count'' box should be increasing if vertical drive is being received from the camera. If it is not increasing, check the connections and power to the camera. If that fails, refer to the ''In Case of Trouble'' chapter in this manual.

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. ISA bus transfers will also 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.

 

1.1. Motherboards

Most motherboards manufactured since January 2001 should be capable of operation with the PIXCI imaging board. If you have questions about the compatibilty of the motherboard intended for use with the PIXCI imaging board, contact EPIX, Inc. EPIX, Inc. can provide tested systems including the camera and PC.

For fast display updates, motherboards with an Advanced Graphics Port (AGP) and an AGP VGA are recommended. EPIX can provide complete, tested computer systems with a PIXCI and all required software installed as well as tested AGP VGA boards and motherboards.


 

 

 

2. Connectors

The PIXCI D3X imaging board has three connectors for input/output. Two 10 pin headers are provided for connecting external and internal signals to the PIXCI D2X. A 100 pin connector is accessible thru the bracket that mounts the board to the computer chassis. The 100 connector is a Honda PCS-XE100LFD-HS. The suggested mating connector is a HONDA PCS-XE100MA.

 

2.1. PIXCI D3X 10 Pin Header 1 Signal List

Signal IN/ Pin Pin IN/ Signal
Name OUT Number Number OUT Name

Ground 1 2 +5 VDC (0.75 Amp max)

NTRIG1 I 3 4 I PTRIG1



NFEN1 I 5 6 I PFEN1


NSTR1 O 7 8 O PSTR1


NIO I/O 9 10 PIO

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 D3X. None of the signals on Header 1 are provided on the 100 pin connector.

Header 1 is located in the top center of the PIXCI D3X.

Pin 1 is ground.

Pin 2 is +5 volts thru a 0.75 ampere thermal sensing, self resetting fuse.

Pin 3, NTRIG1, is a negative differential trigger input.

Pin 4, PTRIG1, is a positive differential trigger input.

Pin 5, NFEN1, is the negative differential frame enable input.

Pin 6, PFEN1, is the positive differential frame enable input.

Pin 7, NSTR1, is a negative differential strobe output.

Pin 8, PSTR1, is a positive differential strobe output. NSTR1 and PSTR1 provide a strobe output which is driven from a separate driver from the PSTR and NSTR strobe signal on the 100 pin connector. The PSTR1 and NSTR1 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 NSTR1 and PSTR1 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. NIO and PIO are 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).

For a line scan camera, the vertical drive signal and trigger input are selected via hardware to come from Header 1 instead of the 100 pin connector. It is possible to have these signals come from the 100 pin connector as an option.

 

2.2. PIXCI D3X 10 Pin Header 2 Signal List

Signal IN/ Pin Pin IN/ Signal
Name OUT Number Number OUT Name

Ground 1 2 +12 VDC (fused at 0.75 A)

OUT1 Out 3 4 Ground

OUT2 Out 5 6 Ground

IN1 In 7 8 Ground

IN2 In 9 10 Ground

Header 2 is located in the lower left of the board near the 100 pin connector. None of the signals on Header 2 are available on the 100 pin connector.

Pin 1 of Header 2 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.

 

 

 

 

2.3. PIXCI D3X 100 Pin Connector Signal List

The 100 pin connector, J1, pinout is listed below with the reference location and pin number for the respective driver or receiver TTL input or output, and an in/out direction indicator for each signal.

Drvr/Rcvr Signal IN/ Pin Pin IN/ Signal Drvr/Rcvr
Pin Number Name OUT Number Number OUT Name Pin Number

+12 VDC Controlled O 50 100 O +12 VDC Controlled

Ground 49 99 Ground

A1-7 User + O 48 98 O +5 VDC Controlled

User - O 47 97 Ground

C1-27 Trigger + O 46 96 I Pixel Clock + C1-31

Trigger - O 45 95 I Pixel Clock -

C1-26 Field + I 44 94 O Strobe + A1-8

Field - I 43 93 O Strobe -

A1-13 Master Clock + O 42 92 O Bin + A1-12

Master Clock - O 41 91 O Bin -

A1-14 Expose + O 40 90 O Prin + A1-15

Expose - O 39 89 O Prin -

C1-23 Line Enable + I 38 88 I Frame Enable + C1-24

Line Enable - I 37 87 I Frame Enable -

Ground 36 86 Ground

D1-57 MSB + I 35 85 I MSB -1 + D1-58

MSB - I 34 84 I MSB -1 -

D2-57 MSB-2 + I 33 83 I MSB -3 + D2-56

MSB-2 - I 32 82 I MSB -3 -

D2-54 MSB-4 + I 31 81 I MSB -5 + D2-53

MSB-4 - I 30 80 I MSB -5 -

D1-52 MSB-6 + I 29 79 I MSB -7 + D1-51

MSB-6 - I 28 78 I MSB -7 -

D1-46 MSB-8 + I 27 77 I MSB -9 + D1-45

MSB-8 - I 26 76 I MSB -9 -

GND 25 75 GND

D1-44 MSB-10 + I 24 74 I MSB -11 + D1-43

MSB-10 - I 23 73 I MSB -11 -

D1-41 MSB-12 + I 22 72 I MSB -13 + D1-40

MSB-12 - I 21 71 I MSB -13 -

D1-39 MSB-14 + I 20 70 I MSB -15 + D1-38

MSB-14 - I 19 69 I MSB -15 -

H1-59 MSB-16 + I 18 100 I MSB -17 + H1-58

MSB-16 - I 17 67 I MSB -17 -

H1-57 MSB-18 + I 16 66 I MSB -19 + H2-56

MSB-18 - I 15 65 I MSB -19 -

GND 14 64 GND

H1-54 MSB-20 + I 13 63 I MSB -21 + H1-53

MSB-20 - I 12 62 I MSB -21 -

H1-52 MSB-22 + I 11 61 I MSB -23 + H1-51

MSB-22 - I 10 60 I MSB -23 -

H1-46 MSB-24 + I 9 59 I MSB -25 + H1-45

MSB-24 - I 8 58 I MSB -25 -

H1-44 MSB-26 + I 7 57 I MSB -27 + H1-43

MSB-26 - I 6 56 I MSB -27 -

H1-41 MSB-28 + I 5 55 I MSB -29 + H1-40

MSB-28 - I 4 54 I MSB -29 -

H1-39 MSB-30 + I 3 53 I MSB -31 + H1-38

MSB-30 - I 2 52 I MSB -31 -

GND 1 51 GND

Pixel clock is driven by the camera.

Master clock is an optional output for cameras that require a pixel clock.

Line Enable is an active high signal when pixels from the camera have valid data.

Frame Enable is an active high signal when lines from the camera have valid data. FEN1 on Header 1 is used when the board is configured for a line scan camera.

Bin is used to enable binning on the camera.

Prin is used to cause the camera to dump charge.

User is an optional camera tristate enable signal.

Field is an optional field indicator from the camera.

Trigger is an optional input to start image acquisition. TRIG1 on Header 1 is the default trigger input.

Strobe is an optional output that can be program generated or generated by the camera control state machine. STR1 on Header 1 is the default strobe output.

Expose is used to control the camera exposure time and send an image to the PIXCI D3X.

MSB is the most significant bit from the camera (bit 31).

MSB-31 is the lease significant bit from the camera (bit 0).

The IN/OUT column indicates if the signal is an input to or an output from the PIXCI D3X.

The Drvr/Rcvr column indicates the TTL input or output that receives or drives the respective differential signal. For example, C1-31 indicates that the differential receiver at location C1 uses pin 31 for the TTL output of the differential pixel clock input from the camera.

 

 

 

 

2.4. PIXCI D3X 100 Pin Connector to Dalsa CA-D6 Signal List

Camera cables are available for connecting to the Dalsa CA-D6 or CT-P1 or to cameras from other camera manufacturers. Standard lengths for camera cables are 2 meters. Other lengths are available.

Wire lists for the Dalsa CA-D6 and CT-P1 cables follow.

Interface Signal Camera OS3 Interface
100 Pin Name 50 Pin Signal
MALE PLUG Type

69 OS3D0B (M-15-) 29 RS-644 Input

70 OS3D0 (M-15+) 45 RS-644 Input

19 OS3D1B (M-14-) 12 RS-644 Input

20 OS3D1 (M-14+) 28 RS-644 Input

71 OS3D2B (M-13-) 44 RS-644 Input

72 OS3D2 (M-13+) 11 RS-644 Input

21 OS3D3B (M-12-) 27 RS-644 Input

22 OS3D3 (M-12+) 43 RS-644 Input

73 OS3D4B (M-11-) 10 RS-644 Input

74 OS3D4 (M-11+) 26 RS-644 Input

23 OS3D5B (M-10-) 42 RS-644 Input

24 OS3D5 (M-10+) 9 RS-644 Input

76 OS3D6B (M-9-) 25 RS-644 Input

77 OS3D6 (M-9+) 41 RS-644 Input

26 OS3D7B (M-8-) 8 RS-644 Input

27 OS3D7 (M-8+) 24 RS-644 Input

78 OS4D0B (M-7-) 6 RS-644 Input

79 OS4D0 (M-7+) 22 RS-644 Input

28 OS4D1B (M-6-) 38 RS-644 Input

29 OS4D1 (M-6+) 5 RS-644 Input

80 OS4D2B (M-5-) 21 RS-644 Input

81 OS4D2 (M-5+) 37 RS-644 Input

30 OS4D3B (M-4-) 4 RS-644 Input

31 OS4D3 (M-4+) 20 RS-644 Input

82 OS4D4B (M-3-) 36 RS-644 Input

83 OS4D4 (M-3+) 3 RS-644 Input

32 OS4D5B (M-2-) 19 RS-644 Input

33 OS4D5 (M-2+) 35 RS-644 Input

84 OS4D6B (M-1-) 2 RS-644 Input

85 OS4D6 (M-1+) 18 RS-644 Input

34 OS4D7B (M-0-) 34 RS-644 Input

35 OS4D7 (M-0+) 1 RS-644 Input


PIXCI D3X 100 Pin Interface Connections and Signals—Part 1/3


Interface Signal Camera OS1 Interface
100 Pin Name 50 Pin Signal
MALE PLUG Type

52 OS1D0B (M-31-) 29 RS-644 Input

53 OS1D0 (M-31+) 45 RS-644 Input

2 OS1D1B (M-30-) 12 RS-644 Input

3 OS1D1 (M-30+) 28 RS-644 Input

54 OS1D2B (M-29-) 44 RS-644 Input

55 OS1D2 (M-29+) 11 RS-644 Input

4 OS1D3B (M-28-) 27 RS-644 Input

5 OS1D3 (M-28+) 43 RS-644 Input

56 OS1D4B (M-27-) 10 RS-644 Input

57 OS1D4 (M-27+) 26 RS-644 Input

6 OS1D5B (M-26-) 42 RS-644 Input

7 OS1D5 (M-26+) 9 RS-644 Input

58 OS1D6B (M-25-) 25 RS-644 Input

59 OS1D6 (M-25+) 41 RS-644 Input

8 OS1D7B (M-24-) 8 RS-644 Input

9 OS1D7 (M-24+) 24 RS-644 Input

60 OS2D0B (M-23-) 6 RS-644 Input

61 OS2D0 (M-23+) 22 RS-644 Input

10 OS2D1B (M-22-) 38 RS-644 Input

11 OS2D1 (M-22+) 5 RS-644 Input

62 OS2D2B (M-21-) 21 RS-644 Input

63 OS2D2 (M-21+) 37 RS-644 Input

12 OS2D3B (M-20-) 4 RS-644 Input

13 OS2D3 (M-20+) 20 RS-644 Input

65 OS2D4B (M-19-) 36 RS-644 Input

66 OS2D4 (M-19+) 3 RS-644 Input

15 OS2D5B (M-18-) 19 RS-644 Input

16 OS2D5 (M-18+) 35 RS-644 Input

67 OS2D6B (M-17-) 2 RS-644 Input

68 OS2D6 (M-17+) 18 RS-644 Input

17 OS2D7B (M-16-) 34 RS-644 Input

18 OS2D7 (M-16+) 1 RS-644 Input

37 LVALB (LEN-) 14 RS-644 Input

38 LVAL (LEN+) 30 RS-644 Input

87 FVALB (FEN-) 23 RS-644 Input

88 FVAL (FEN+) 39 RS-644 Input

95 STROBEB (PCK-) 46 RS-644 Input

96 STROBE (PCK+) 13 RS-644 Input

47 USR_ENB (USR-) 40 RS-644 Output

48 USR_EN (USR+) 7 RS-644 Output


PIXCI D3X 100 Pin Interface Connections and Signals—Part 2/3


Interface Signal Camera Interface
100 Pin Name 15 Pin Signal
MALE PLUG Type

39 EXSYNCB (EXP-) 4 RS-644 Output

40 EXSYNC (EXP-) 12 RS-644 Output

89 PRINB (PRIN-) 13 RS-644 Output

90 PRIN (PRIN+) 5 RS-644 Output

91 PRETRIGB 14 RS-644 Output

92 PRETRIG 6 RS-644 Output


PIXCI D3X 100 Pin Interface Connections and Signals—Part 3/3

 

 

 

 

2.5. PIXCI D3X 100 Pin Connector to DALSA CT-P1 Signal List

Interface Signal Camera OS1 Interface
100 Pin Name 37 Pin Signal
MALE PLUG Type

52 OS1D0B (D31-) 35 RS-644 Input

53 OS1D0 (D31+) 16 RS-644 Input

2 OS1D1B (D30-) 34 RS-644 Input

3 OS1D1 (D30+) 15 RS-644 Input

54 OS1D2B (D29-) 33 RS-644 Input

55 OS1D2 (D29+) 14 RS-644 Input

4 OS1D3B (D28-) 32 RS-644 Input

5 OS1D3 (D28+) 13 RS-644 Input

56 OS1D4B (D27-) 31 RS-644 Input

57 OS1D4 (D27+) 12 RS-644 Input

6 OS1D5B (D26-) 30 RS-644 Input

7 OS1D5 (D26+) 11 RS-644 Input

58 OS1D6B (D25-) 29 RS-644 Input

59 OS1D6 (D25+) 10 RS-644 Input

8 OS1D7B (D24-) 28 RS-644 Input

9 OS1D7 (D24+) 9 RS-644 Input

60 OS2D0B (D23-) 27 RS-644 Input

61 OS2D0 (D23+) 8 RS-644 Input

10 OS2D1B (D22-) 26 RS-644 Input

11 OS2D1 (D22+) 7 RS-644 Input

62 OS2D2B (D21-) 25 RS-644 Input

63 OS2D2 (D21+) 6 RS-644 Input

12 OS2D3B (D20-) 24 RS-644 Input

13 OS2D3 (D20+) 5 RS-644 Input

65 OS2D4B (D19-) 23 RS-644 Input

66 OS2D4 (D19+) 4 RS-644 Input

15 OS2D5B (D18-) 22 RS-644 Input

16 OS2D5 (D18+) 3 RS-644 Input

67 OS2D6B (D17-) 21 RS-644 Input

68 OS2D6 (D17+) 2 RS-644 Input

17 OS2D7B (D16-) 20 RS-644 Input

18 OS2D7 (D16+) 1 RS-644 Input

37 LVALB (LEN-) 37 RS-644 Input

38 LVAL (LEN+) 18 RS-644 Input

95 STROBEB (PCK-) 36 RS-644 Input

96 STROBE (PCK+) 17 RS-644 Input


PIXCI D3X 100 Pin Interface Connections and Signals—Part 1/3


Interface Signal Camera OS3 Interface
100 Pin Name 37 Pin Signal
MALE PLUG Type

69 OS3D0B (D15-) 35 RS-644 Input

70 OS3D0 (D15+) 16 RS-644 Input

19 OS3D1B (D14-) 34 RS-644 Input

20 OS3D1 (D14+) 15 RS-644 Input

71 OS3D2B (D13-) 33 RS-644 Input

72 OS3D2 (D13+) 14 RS-644 Input

21 OS3D3B (D12-) 32 RS-644 Input

22 OS3D3 (D12+) 13 RS-644 Input

73 OS3D4B (D11-) 31 RS-644 Input

74 OS3D4 (D11+) 12 RS-644 Input

23 OS3D5B (D10-) 30 RS-644 Input

24 OS3D5 (D10+) 11 RS-644 Input

76 OS3D6B (D9-) 29 RS-644 Input

77 OS3D6 (D9+) 10 RS-644 Input

26 OS3D7B (D8-) 28 RS-644 Input

27 OS3D7 (D8+) 9 RS-644 Input

78 OS4D0B (D7-) 27 RS-644 Input

79 OS4D0 (D7+) 8 RS-644 Input

28 OS4D1B (D6-) 26 RS-644 Input

29 OS4D1 (D6+) 7 RS-644 Input

80 OS4D2B (D5-) 25 RS-644 Input

81 OS4D2 (D5+) 6 RS-644 Input

30 OS4D3B (D4-) 24 RS-644 Input

31 OS4D3 (D4+) 5 RS-644 Input

82 OS4D4B (D3-) 23 RS-644 Input

83 OS4D4 (D3+) 4 RS-644 Input

32 OS4D5B (D2-) 22 RS-644 Input

33 OS4D5 (D2+) 3 RS-644 Input

84 OS4D6B (D1-) 21 RS-644 Input

85 OS4D6 (D1+) 2 RS-644 Input

34 OS4D7B (D0-) 20 RS-644 Input

35 OS4D7 (D0+) 1 RS-644 Input


PIXCI D3X 100 Pin Interface Connections and Signals—Part 2/3


Interface Signal Camera Interface
100 Pin Name 15 Pin Signal
MALE PLUG Type

39 EXSYNCB (EXP-) 4 RS-644 Output

40 EXSYNC (EXP-) 12 RS-644 Output

89 PRINB (PRIN-) 13 RS-644 Output

90 PRIN (PRIN+) 5 RS-644 Output

1 SHIELD COVER GND


PIXCI D3X 100 Pin Interface Connections and Signals—Part 3/3


 

 

 

3. Software Installation

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.

 

3.1. For Windows 95, 98, ME

  1. Install Files:

    1. If XCAP is provided on diskette(s):

      1. Insert XCAP diskette #1 into the A: or B: drive.

      2. Execute the ''SETUP'' program, from a command prompt, or via the Windows ''Start'', ''Run'':
            > A:SETUP
        or
            > B:SETUP
        

      3. Follow the installation program's directions, such as to select an installation directory, and insert additional diskettes (depending upon version) as instructed. The default installation directory is C:\XCAP or C:\Program Files\EPIX\XCAP\XCAP.

    2. If XCAP is provided on a compact disk (CD):

      1. If your computer is set to allow automatic execution of loaded CDs, the CD's interactive index program will be executed automatically. Otherwise, execute the index program, from a command prompt, or via the Windows ''Start'', ''Run'':
            > Z:SETUP       (replace Z with drive letter for your CD)
        

      2. Select ''Setup PIXCI(R) Imaging Software'' and ''XCAP Imaging Application''. Click ''OK''.

      3. Follow the installation program's directions, such as to select an installation directory. The default installation directory is C:\XCAP or C:\Program Files\EPIX\XCAP\XCAP.

    3. If XCAP is provided via the internet:

      1. Download:
        ftp.epixinc.com/software/xcap_v30/XCAPWIN32.EXE (for 32 bit Windows)
        
        from the EPIX, Inc. ftp site.

      2. Execute the downloaded program, from a command prompt, or via the Windows ''Start'', ''Run'':
        > XCAPWIN32.EXE     (for 32 bit Windows)
        > XCAPWIN64.EXE     (for 64 bit Windows)
        

      3. Follow the installation program's directions, such as to select an installation directory. The default installation directory is C:\XCAP or C:\Program Files\EPIX\XCAP\XCAP.

      4. Delete the downloaded .EXE file from your computer's hard drive.

    4. The installation procedure creates a new program group, containing XCAP and several .TXT files. The *.TXT files contain these installation instructions, a list of distributed files, corrections or additions to this manual, or other up-to-date information. The PCITIPS.TXT file provides the PC Configuration Tips, with tips for resolving hardware and software conflicts.

  2. Create Shortcut - Drag & Drop (optional):

    1. From the program group created by the installation program, click and drag the icon for XCAP over to the desktop and drop.

  3. Create Shortcut - Manual (optional):

    1. Right click on the Desktop.[1]

    2. Select ''New''.

    3. Select ''Shortcut''.

    4. Set:
          Command Line:   InstallDir \ XCAPWXX
          Name:           XCAP
      
      replacing ''InstallDir'' with the name of the installation directory chosen above. Select ''OK''.

  4. Install Authorization Key (for XCAP-Plus, XCAP-Std, and XCAP-Ltd):

    1. XCAP-Plus, XCAP-Std, and XCAP-Ltd, but not XCAP-Lite, are provided with either a printer port authorization key or a USB authorization key.

      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.

    2. Run the authorization key utility program provided with XCAP by ''Start'', ''Run'':
          > C:\XCAP\HARDLOCK\HLDINST -install
      

    3. Or, in command prompt mode, switch to the chosen installation directory:
          > CHDIR C:\XCAP\HARDLOCK
      
      and execute:
           HLDINST  -install
      
      to run the authorization key utility program.

    4. For USB port authorization keys, in some versions of Windows 95 and 98, it is also necessary to:
          Start
          Settings
          Control Panel
          Add New Hardware
          ...
      

    5. Note that support for the USB port authorization key under Windows 95 requires OSR2 or later with the USB supplement.

  5. Install PIXCI® Imaging Board Driver:

    1. Under Windows 95, 98, and ME, the Windows' Device Manager must be used for initial installation of the PIXCI® driver.

      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''.

  6. Set Frame Buffer Memory Size (optional):

    1. By default, 4 MBytes of frame buffer memory is allocated.

    2. Under Windows 95, 98, and ME, frame buffer memory must be allocated during Windows' initialization, as specified in the Windows' 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.

  7. Configure Graphics Display (S/VGA):

    1. A ''High Color (16 bit or 65536 Color)'', ''True Color (24 bit or 16777216 Color)'', or ''True Color (32 bit)'' setting for the graphics display system (S/VGA) is required for proper display of images and overlay graphics. The ''True Color (24 bit or 16777216 Color)'' or ''True Color (32 bit)'' is suggested for higher quality, and quicker, display of images and overlay graphics. This may be checked and/or modified via Windows ''Start'', ''Control Panel'', ''Display'', ''Settings''.

    2. In Windows 95, under ''Control Panel'', ''Display'', ''Plus!'', the ''Show window contents while dragging'' must be disabled (this feature is not present in older versions of Windows 95). Or in Windows 98/ME, under ''Control Panel'', ''Display'', ''Effects'', the ''Show window contents while dragging'' must be disabled.

    3. After changing the settings a full shutdown and CTRL+ALT+DEL reboot should be used. The quick restart offered by older versions of Windows 95, and the ''hot'' graphics display S/VGA reconfiguration performed by newer versions of Windows 95, may not re-initialize all devices properly.

  8. Reboot Windows.

  9. XCAP is now ready to run, by clicking the optional shortcut, or by clicking ''Start'', ''Programs'', ''XCAP Imaging'', and finally ''XCAP for Windows''.

 

3.2. Windows 95, 98, ME - Esoterica

3.2.1. Windows 95, 98, ME - Manual Installation

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.

  1. The EPIXXCW5.VXD (or EPIXXC32.VXD for version 2.0 and earlier) must be copied to the Windows SYSTEM directory, typically:
        C:\WINDOWS\SYSTEM
    

  2. Using the Registry Editor (REGEDIT) provided with Windows, create an entry such as:
        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+)
    

  3. Using the Registry Editor, edit the existing entry for PIXCI® SV2 or PIXCI® SV3:
    (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 entry for PIXCI® SV4:
    (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® SV5, SV5A, or SV5B:
    (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 entries for PIXCI® SV6:
    (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® D, PIXCI® D24, or PIXCI® D32:
    (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® A:
    (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® CL3SD:
    (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® CL1:
    (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® CL2:
    (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® D2X:
    (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® D3X:
    (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® E1:
    (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® E4:
    (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® E1DB:
    (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® E4DB:
    (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_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_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® EL1:
    (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® EL1DB:
    (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® SI:
    (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_**
    
    or the existing entry for PIXCI® SI4:
    (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_**
    
    where the **'s may be any digits (assigned and created by Windows after detection of the PIXCI® imaging board).[2] This entry must contain:
        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.

  4. Reboot Windows.

3.2.2. Windows 95, 98 - Forceful Frame Buffer Memory Allocation

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:

  1. In C:\CONFIG.SYS, add a line:[3]
        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.

  2. Edit the Windows' SYSTEM.INI file, add a section:
        [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.

  3. Reboot Windows.

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.