1. Install drivers from webcam CD
Control can use native webcam app or our wrapper, using wrapper is more userfriendly and can work with different cameras without making changes to ccreg, but give us less control over the camera
(If we are going to use native webcam app, skip next step and go to 4)
2. Install webcam wrapper application from sam:/ccdev/WEBCAM.INSTALL
This application uses .NET 2 framework. If it is not already installed install it: run dotnexfx.exe from the same place
(Note: setup will detect if it is not installed and will try to install it but it much faster to install it manually, also auto install can fail due to security setting, but manuall seems to be working on all tested win boxes)
- Run setup.exe, answer yes to all. (Note: once installed it will try to start application and if camera is not connected there will be err msg, just ignore it)
Copy sam:/ccdev/WEBCAM.INSTALL/Webcam_latest_version/Webcam.exe.deploy into C:/cc/std/binw/webcam.exe (This is king of kludge to launch .NET app from our old style program) It is not neccessary to be C:/cc/binw/webcam.exe but MUST be on local drive
3. run ccreg and set full path to application that we are going to use:
webcam wrapper (something like C:\cc\std\binw\webcam.exe)
- we can copy it to C:\cc\std\binw or some another place to avoid such long path, do not create a link, make a copy.
or native web cam app like C:\Program Files\LogiTech\QuicCam.exe.
NOTE: use full path with extension and use .exe file only, it is NOT possible to launch link or appref-ms from control
4. set tmpimg directory where we are going to keep temp files and make sure that it is actually exist (CCDIR/COMPNAME/tmpimg is
- preferred palce) Make sure that company dir has subdirs like tmp and images.
MAKING CHANGES TO WEBCAM WRAPPER
Source project form webcam wrapper is on sam:/ccdev/webcam_win32_app. It is VB code, so MS VB 2005 express edition would be fine. Or use something else...