FAQ

Keeping the program window on the desktop (not minimized or iconized) should prevent the driver from freezing.

KABcam defaults to a 45 second timeout value when connecting to an FTP server. To increase the FTP timeout value:

1. Exit KABcam.
2. Using NOTEPAD open the KABCAM.INI file located in your WINDOWS directory (or WINNT if you are running NT or Windows 2000).
3. Locate the heading [UploadOptions].
4. Beneath the heading add the following line, relacing 45 with the desired timeout value (in seconds). FTPTimeOut=45
5. Save the file.
6. Sart KABcam.

KABcam supports using multiple capture devices by allowing you to run multiple instances of KABcam using different configuration files for each device. By default KABcam will use a configuration file named KABCAM.INI located in your WINDOWS (or WINNT) directory. By specifying a different configuration name on the command line KABcam will create/use a different configuration. For instance, by starting KABcam as follows: KABCAM.EXE KABCAM2 KABcam will create/use a configuration file named KABCAM2.INI. DO NOT include the extension (.INI) on the command line. A few important notes...

• This feature is provided as is... It may not work for everyone.
• Before creating a new configuration you must close all instances of KABcam.
• For each configuration you must specify a different capture device.
• For each configuration you must specify a different JPG filename.
• It is not advisable to run multiple instances of KABcam if you are using the auto-dialup mode. It may result in one copy hanging up while another is uploading.
• Capture devices typically reduce system performance, multiple capture devices running at once may bring your system to it's knees. (This is  especially true of USB cameras)
• It is very likely that some capture devices will not operate at the same time as others.

 

A Failed to capture image or Invalid Instruction error when uploading or capturing an image indicates that the camera or capture device is set to an image format not supported by KABcam. KABcam supports RGB images at 8, 16, 24 and 32 bit color. Some users have reported that MPEG formats also work. KABcam does not support most YUV image formats. To change the image format: 1. Click on Setup and then the Image tab. 2. Click the Format button under Capture Properties. If your camera or capture device does not show RGB images as an option, try selecting different formats until you find one that works.

There are several known issues with Microsoft's FTP server. The links below may help with some of the issues. Access denied when attempting to PUT files on FTP Server http://support.microsoft.com/support/kb/ar...s/Q182/6/26.ASP 550 Error Message http://support.microsoft.com/support/kb/ar...s/Q238/6/44.ASP Lock error when deleting a file on the FTP Server http://support.microsoft.com/support/kb/ar...s/Q186/8/02.ASP

FTP Reply Codes 100 Series - The requested action is being initiated, expect another reply before proceeding with a new command. 110 Restart marker reply. 120 Service ready in nnn minutes. 125 Data connection already open; transfer starting. 150 File status okay; about to open data connection. 200 Series - The requested action has been successfully completed. 200 Command okay. 202 Command not implemented, superfluous at this site. 211 System status, or system help reply. 212 Directory status. 213 File status. 214 Help message. 215 NAME system type. 220 Service ready for new user. 221 Service closing control connection. 225 Data connection open; no transfer in progress. 226 Closing data connection. 227 Entering Passive Mode (h1,h2,h3,h4,p1,p2). 230 User logged in, proceed. 250 Requested file action okay, completed. 257 'PATHNAME' created. 300 Series- The command has been accepted, but the requested action is being held in abeyance, pending receipt of further information. 331 User name okay, need password. 332 Need account for login. 350 Requested file action pending further information. 400 Series - The command was not accepted and the requested action did not take place, but the error condition is temporary and the action may be requested again. 421 Service not available, closing control connection. 425 Can't open data connection. 426 Connection closed; transfer aborted. 450 Requested file action not taken. 451 Requested action aborted: local error in processing. 452 Requested action not taken. 500 Series - The command was not accepted and the requested action did not take place. 500 Syntax error, command unrecognized. 501 Syntax error in parameters or arguments. 502 Command not implemented. 503 Bad sequence of commands. 504 Command not implemented for that parameter. 530 Not logged in. 532 Need account for storing files. 550 Requested action not taken. 551 Requested action aborted: page type unknown. 552 Requested file action aborted. 553 Requested action not taken.

This information is provided 'as-is'. KAB Software is unable to provide support for this technique. Though KABcam itself does not have the capability of running as a service under Windows NT,2000 or XP, it can be accomplished using the AppToService utility from Basta Computing. Before configuring KABcam to run as a service using AppToService you must first make sure the the 'Run when Window starts' and 'Hide when minimized' options are disabled. NOTE: Some USB cameras depend on the preview window for automatically adjusting the image brightness. If KABcam is run as a service the preview window will not be visible and this may impact the quality/brightness of the image.

KABcam supports cameras and capture devices that use VFW (Video for Windows) drivers. Most cameras and capture devices support VFW, however there are a small number that do not. Microsoft provides a small program called VidCap which can be used to determine if a camera or capture device uses VFW drivers. If VidCap recognizes a camera or device you can be reasonably sure KABcam will recognize it as well. You can download VidCap from ftp://ftp.kabsoftware.com/pub/vidcap32.exe

Lydia Email Agent is no longer available for sale, however we will continue to provide technical support for the foreseeable future.

If the email address that you entered in the 'To' box is correct and the name of the SMTP server for the account you are sending 'From' is correct, the problem is that the SMTP server is rejecting the email message and refusing to send it out. This can happen when you connect to a one ISP and try to send out email using the SMTP server of another ISP. ISP's usually use one of two methods to restrict access to their SMTP severs to prevent Spam from being sent through their mail servers. One of the ways is to verify that the computer is on the ISP's local network. When you dial your modem and connect to your ISP, your computer is given an IP address that identifies you as being a part of that ISP's network. If you have two ISPs and dial up to one and then connect to the other's mail server, it may prevent you from relaying mail because your computer is not identified as being on the local network for the provider whose mail server you are sending through. Another way to restrict access is to insist on a local domain return address. If you connect to the mail server for 'domain.com' it may only allow you to send mail that is from 'username@domain.com' -- if you try to send from another account and have the return address of 'username@anotherdomain.com' it may restrict you from relaying to another server. For additional information please contact your ISP and ask them how they handle relaying email.