CMU 1394 Digital Camera Driver

Installation
Main | Download | Compatibility | Installation | Support | Documentation | FAQ

Installation

As of version 6.4, installation is by self-extracting executable.  Thereafter, if you must install the driver by hand, use the following procedure on Windows 2000 or XP:
  1. Make sure your camera is plugged in.
  2. Open the Device Manager through the Computer Management Console. It may be found in the Control Panel under Administrative Tools
  3. From the list of available device types, select Imaging devices.  If you are installing this driver over top of a previous version, your digital camera will be listed as "CMU 1394 Digital Camera Device".  If not, it will typically be listed as "Sony 1394 CCM-DS250 Desktop Camera". or as "Generic 1394 Digital Camera #n" under winXP. Right-click it and select Properties 
  4. In the properties panel, select the Driver tab, and then click Update Driver.
  5. Follow the on screen instructions, do NOT use the search option. Use the "Display a list of..." option instead
  6. Click on the "Have Disk..." button, point the directory to where 1394Camera.inf is stored (e.g. C:\Program Files\CMU\1394Camera\driver\).
  7. Ignore the warnings about the driver not being digitally signed or that windows can't be sure the driver will work. 
  8. When installation is finished, verify in the driver tab that the provider is "Carnegie Mellon University" and that the version is "6.4.0.108". Also verify that your camera is now listed in the device manager as "CMU 1394 Digital Camera Device".  The name doesn't seem to change properly under winXP... go figure.
The procedure for 98 or ME is nearly the same, except the device manager is on a tab in the "System" Control Panel applet and some of the buttons have different names.
For some reason, 98 and ME have trouble finding 1394camera.dll. If you encounter this, just click "skip file" and put 1394camera.dll into c:\windows\system\ yourself

Notes for Previous Users

  • The storage size of the C1394Camera class has changed, so you must recompile your projects in order to avoid memory referencing errors.
  • The prototypes of many of the exported functions have changed, so chances are your apps won't work right away anyway.
  • You no longer need to put your 1394 host controller into diagnostic mode. If it is in diagnostic mode (as per the instructions for the installation of version 4.1), I recommend you turn diagnostic mode back off.
  • Most of the functions now return error codes rather than popping up message boxes. Make use of them.

Previous Distribution Contents (6.3 and earlier)

When unzipping the distribution, you should use the "Use Folder Names" option to extract the files into the correct folders. Winzip should then extract the following files into the corresponding directories relative to the target directory.
1394camera.dll   \ The Compiled Library
1394camera.inf   \ Driver Installation Script
1394cmdr.sys   \ Driver Binary
1394CameraDemo.exe
 \
 Demo Application
1394camera.chm
 \
 Help File
lgpl.txt
 \
 GNU LGPL
1394Camera.h   \include\
1394CameraControl.h   \include\
1394CameraControlSize.h   \include\
1394CameraControlTrigger.h   \include\
1394camapi.h   \include\
1394Camera.lib   \lib\
1394camera.exp   \symbols\
1394camera.pdb   \symbols\
1394cmdr.map   \symbols\
1394cmdr.sym   \symbols\

The zip file also includes a folder, 1394CameraDemo, that contains a Visual Studio workspace and source code for the 1394CameraDemo application.

Library and Headers

  • You should copy the contents of the \include\ subdirectory to somewhere on your include path, typically "C:\Program Files\Microsoft Visual Studio\VC98\Include" Be sure to overwrite any previous versions of those files
  • You should copy the contents of the \lib\ subdirectory to somewhere on your link path, typically "C:\Program Files\Microsoft Visual Studio\VC98\Lib" Be sure to overwrite any previous versions of those files.
  • The contents of the \symbols\ directory are provided to assist in debugging and should be placed wherever your preferred debugger can find them.

The demo application will not compile until the library and headers are on the VC link and include paths.