Like many who have posted on this site, I have had problems with NetMeeting crashing. In my case, I had to work hard to discover an unusual solution. Perhaps it may help other readers, too. I used a cybertainment PCI video capture card containing a Brooktree 878 chip in a 200 MHz Pentium 2 computer with 96 Megs of ram running Windows 95a. When I ran NetMeeting and established a connection with another user, the computer would completely freeze several minutes after beginning a video conference. This problem occurred every time and rebooting was mandatory. This malfunction also took place when I was offline and previewing my own video in the video window. The computer usually hung when it became busy performing functions with other programs. After much investigation, I discovered a file labelled "msnetmtg.inf" in the C:\WINDOWS\INF folder. Some of the text in that file discloses entries that are made in the Windows registry during NetMeeting installation. One group of registry entries (; Capture Devices) is a long list of cameras and capture cards with which NetMeeting is compatible. Each camera is assigned four operating parameters in these registry entries. One of those parameters for each camera is designated "dwStreamingMode." In the .inf file, the programmer entered remarks for three cameras (Kodak DVC323, TopCam, and ATI Video Basic Capture Driver) indicating that streaming mode had been disabled due to 100% CPU usage. In the windows registry, the dwStreamingMode key for each of those cameras is assigned the value 01 00 00 00. For many other cameras, the value is 00 00 00 00, including the Brooktree PCI Video Capture Driver with which I was having such trouble. I hypothesized that my troubles may be due to high CPU usage and that disabling the streaming may eliminate the problem. I further reasoned that changing the registry key for my camera from "00 00 00 00" to "01 00 00 00" would disable the streaming. I opened regedit.exe and found my camera at the following location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Conferencing\CaptureDevices and modified the registry to reflect the new dwStreamingMode value (01 00 00 00). After doing this, I performed a 1 1/2 hour video conference with a chat partner in Puerto Rico. During the conference, I transmitted and received both video and audio simultaneously, in addition to running ICQ Lite in my Netscape browser. Absolutely no problems occurred and I believe this is due to my registry modification. Perhaps those who are having problems with NetMeeting hanging should check the windows registry for their particular video capture device used by NetMeeting and see whether streaming mode has been disabled. (If a user decides to attempt to modify the registry in order to try this solution, it would be a safe idea to back up the registry by exporting the registry to a text file before making any changes.) I have not seen this suggestion anywhere on the web and perhaps this new idea will help some people.