If you don't find the answer to your question here or in readme.txt or cuseeme.txt, you can join the mail list cu-seeme-L. See README.TXT for info. Rich Kennerly (rbk1@cornell.edu).
See COMPAT.TXT.
The latest copy of COMPAT.TXT is available via FTP at cu-seeme.cornell.edu/pub/CU-SeeMe and on the web at: http://cu-seeme.cornell.edu/PC.CU-SeeMeCurrent.html
Here are the steps to take to install a QuickCam with Window '95
msvideo=quickcam.drv
If you've had another capture driver installed you might see another driver listed as msvideo and another entry, msvideo1=quickcam.drv. In this case you should switch the quickcam to be msvideo and the other driver to be msvideo1.
Hostname Requirement for Windows CU-SeeMe.
Your Windows machine will need a hostname. CU-SeeMe for Windows
will not work without it (this requirement may disappear soon).
The way to provide a hostname is to make an entry into the hosts file
called "hosts" (with no extension): The format for the hosts file is:
your-IP-address name-for-your-PC
For example, you might decide to use the hostname WillieBob. If
your IP address was 128.32.64.88, the entry in your hosts file would
look like:
128.32.64.88 WillieBob
Your HOSTS file should be in your Windows Sockets directory (the same directory that contains your 'winsock.dll'). This directory must be in the PATH before windows is started. Note: the HOSTS file needs to be accessed by the Winsock stack, not CU-SeeMe - putting the HOSTS file in the directory with CU-SeeMe will not accomplish anything.
If you don't already have a hostname for your PC, you may want to contact your network administrator about getting one assigned. If your host name is defined in a Domain Name Server (DNS) accessible to your PC, you won't need to have a HOSTS file. Keep in mind, in this case, that if you can't reach your DNS, you'll get the "GetHostByName() Error" message.
While this issue has been a problem for many it has worked on all stacks after some work (The FTP software hitch mentioned below took many phone calls to a very patient user at NSF before solving).
Things to verify:
Possible stumbling blocks:
Assuming that you have tested other winsock network applications so you know you have basic network connectivity, there are several possible reasons why you might be getting this response:
It can be difficult to determine whether or not there is a firewall in place on your network. If you can telnet to a reflector host (even though you can't log on) but CU-SeeMe doesn't work then it could be a firewall. You can contact your network provider to see if there are any restrictions on the traffic passing in and out of your network. CU-SeeMe uses UDP (not TCP) on UDP port 7648. You can ask your network provider to allow UDP traffic on port 7648 to get through the 'firewall'.
"TIA will not work with CU-See me because CU-SeeMe needs an IP address of the machine you are connecting with. TIA does not give your machine an IP address but gives you the IP address of the machine you are connecting to, so instead of trying to connect back to your machine CU-SeeMe is connecting back to your providers machine (the machine that you are running tia on). In order for CU-SeeMe to work you need a PPP or SLIP account where you have your own individual IP address."
Sometimes a video capture card (especially Creative Labs Video Blasters) can be installed in the system and the Video Capture program supplied by Creative Labs works fine. But, CU-SeeMe does not generate a local video picture and the 'File-Video Devices' option is greyed out.
Edit your system.ini file in the /windows directory and, in the [drivers] section, make sure there's an entry for msvideo=. For example, one user with a blaster FS200 has the entry:
msvideo=fs200cap.drv
in system.ini. Check your installation guide to see what it should be for your model. This entry is needed for software to locate the driver; apparently the Creative labs software itself does not require this.
For Windows '95 you should also check:
Some Winsock stacks, especially Lan WorkPlace for Dos, often report this error. The error 11004 means that your winsock stack either does not support UDP or is not set up to do so. Check the configuration options for your network installation to make sure UDP is enabled if possible. If you're using LAN WP see the other FAQ answer for LAN WP.
We received a report about an IMPORTANT configuration detail required for CU-SeeMe. In the NET.CFG file you can specify the number of sockets for TCP and UDP. You must change this number to 30 or less in order for CU-SeeMe to work:
tcp_sockets 30
udp_sockets 30
raw_sockets 1
Audio will only work if you've got enough bandwidth to support it. At this point, you need to have at least a 28.8K modem, ISDN at 64K or 128K, or a faster network connection to the Internet. If you have a 28.8K modem you STILL will only receive audio if the sender has set their audio encoding method to DeltaMod 16K. Unfortunately, at this point, there's no way to tell what method they're using - you just won't hear them (or perhaps you'll hear pops and tiny segments of sound).
IMPORTANT NOTE: If your computer is audio capable but you DON'T have a camera you can only choose the audio encoding method by editting CUSEEME.INI. The two choices for audio encoding method are:
[Audio Settings]
Encoding Method=Delta-Mod (16 Kb/s)
--or--
Encoding Method=Intel DVI (32 Kb/s)
If you are using a MODEM at 28.8 or less you MUST use Delta-Mod
encoding!!!!
Especially for Win'95 users, sometimes the local window does not appear anywhere on the screen even though the camera still works and you're sending video. The File / Video Format... dialog still works.
For some reason, the local video window is off-screen. You might find it under the task bar (Windows '95) in the lower right corner. Or, you can edit the /windows/cuseeme.ini file and remove or edit the settings for [Video Position] for Window0=x,y.