NetMeeting 2.11 Netmeet.txt File Contents (1 of 2) (220593)

MORE INFORMATION

------------------------------------------------------------
                README for Microsoft NetMeeting 2.11
                              November 1998
      ------------------------------------------------------------

             (c) Copyright Microsoft Corporation, 1998


This document provides complementary or late-breaking information 
to supplement existing documentation.


------------------------
HOW TO USE THIS DOCUMENT
------------------------

To view Netmeet.txt on screen in Notepad, maximize the Notepad 
window.

To print Netmeet.txt, open it in Notepad or another word 
processor, and then use the Print command on the File menu.


CONTENTS
========

SYSTEM REQUIREMENTS AND SETUP
USING NETMEETING
PLACING A CALL
RECEIVING A CALL
SHARING AN APPLICATION
WHITEBOARD
CHAT
FILE TRANSFER
AUDIO COMMUNICATION
HANGING UP
VIDEO
GENERAL KNOWN ISSUES
WINDOWS NT ISSUES


SYSTEM REQUIREMENTS AND SETUP
=============================

Microsoft(R) NetMeeting(R) enables real-time audio, video, and 
data communication over the Internet. 

In order to use NetMeeting, you must have the following
configuration:

- Microsoft Windows(R) 95 or Windows(R) 98
- At least a 486/66 processor with 8 megabytes of RAM 
  (Pentium with 12 MB of RAM recommended)

	--or--

- Microsoft Windows NT(R) 4.0
- At least a 486/66 processor with 16 megabytes of RAM 
- Microsoft Windows NT 4.0 Service Pack 3 or later required to enable 
  sharing applications on Windows NT


IMPORTANT NOTES:


  * NetMeeting 2.11 does not run on Windows 3.1 or beta 
    versions of Windows 98 older than Beta 3. 

  * It is strongly recommended that you uninstall earlier beta 
    versions of NetMeeting before installing NetMeeting 2.11.

- If you use special characters, such as "\\" or double-byte 
  characters, when typing the installation location for NetMeeting 
  during setup, NetMeeting may not install correctly.

- NetMeeting no longer supports placing calls over IPX or over 
  PSTN.

- NetMeeting works best with a fast Internet connection (a 28.8k-
  baud or faster modem or a local area network).

- To use the audio features of NetMeeting, you need a sound card, 
  speakers, and a microphone.

- To send video with NetMeeting, you need either a video-capture 
  card and camera or a video camera that connects through your 
  computer's parallel (printer) port. You will not be able to 
  send video on some computers with a processor slower than a 
  Pentium.

  Computers with a bidirectional (ECP or EPP) parallel port will 
  perform noticeably better with parallel port video cameras than 
  computers with a unidirectional parallel port.

  Cameras that connect to a video-capture card will use less of 
  your computer's processor than cameras that connect through your 
  computer's parallel port. It is recommended that you do not use 
  a color parallel port camera unless your computer is at least a 
  Pentium 133.

- The application-sharing feature may not perform well while you 
  are using audio and video and are connected over a slow 
  connection. Additionally, you might experience "choppy" audio 
  while using video.

  The default setting for video over a 28.8-baud modem connection 
  is medium quality. To change this setting, click the Tools menu, 
  click Options, click the Video tab, and then change the Video 
  Quality option.

- Windows NT users will be able to share applications if they have
  installed Service Pack 3 or later for Windows NT 4.0. 

For more information about NetMeeting, including the NetMeeting 
Resource Kit, see http://www.microsoft.com/netmeeting/.

For the NetMeeting Software Development Kit (SDK), see  
http://www.microsoft.com/netmeeting/sdk.

For information about product support, see the Support.txt
file in your Windows or NetMeeting program folder.

To uninstall NetMeeting
-----------------------
1. In Control Panel, double-click the Add/Remove Programs icon.
2. On the Install/Uninstall tab, click NetMeeting, and
   then click Add/Remove Programs.
3. If a dialog box appears asking if you want to restart your 
   computer, click Yes.

	-or-

1. In Control Panel, double-click the Add/Remove Programs icon.
2. On the Windows Setup tab, click Communications, and then click 
Details.
3. Clear the NetMeeting check box.


Warnings and Known Bugs
-----------------------
- If you uninstall Windows NT Service Pack 3 or later after installing 
  NetMeeting 2.11, you will receive an error message when you 
  restart your computer. To prevent this, carry out the following 
  steps:

  1. Close the error message window.
  2. In the Display properties dialog box, click Cancel. 
  3. In Control Panel, click the Devices icon.
  4. Click mnmdd, and then click the Startup button.
  5. Change the Startup Type from System to Disabled, and then 
     click OK.
  6. Restart your computer so the change can take effect.

- If, after enabling application sharing on the NT version of NetMeeting, 
  your computer faults, you may have an incompatible display driver 
  and will need to do one of the following:

  - Uninstall / reinstall NetMeeting and not enable application sharing
  - Upgrade the driver
  - Use a generic display driver
  - Install a different video adapter
  - Install the current release of the NT Service Pack.


USING NETMEETING
==========================

- NetMeeting includes support for the H.323 audio and video conferencing
  standard. NetMeeting can be used to place calls to and receive calls
  from products that are H.323-compatible, including the Intel Internet
  Video Phone. With appropriate equipment and services that are currently
  under development by third parties, NetMeeting can place a call to 
  a telephone using an H.323 gateway.

- Microsoft maintains the following directory servers on the 
  Internet:

  ils.microsoft.com
  ils1.microsoft.com
  ils2.microsoft.com
  ils3.microsoft.com
  ils4.microsoft.com
  ils5.microsoft.com

  You can use one of these even if it does not appear in the list 
  of servers in the wizard.

  You can also use the following directory servers not maintained 
  by Microsoft:

  ils.four11.com
  ils.business.four11.com
  ils.family.four11.com

  NOTE
  * You will not be able to use these servers to locate people on 
    the Internet if you connect to the Internet through a proxy 
    server that does not support Remote WinSock. 

- Audio and video work only over TCP/IP and with one other person 
  at a time. 

- If you use this version of NetMeeting to call someone who 
  is using NetMeeting 2.0, the call-switching feature may not work 
  correctly.

- This version of NetMeeting enables up to 32 users to share an 
  application. However if a computer running NetMeeting 2.0 is in 
  the conference and more than three users are sharing, that computer 
  will not be able to host an application. In addition, you can be 
  connected to only one other person with audio and video at a time.

  The total number of people who can successfully participate 
  in your meeting will vary based on available network bandwidth 
  and the speed of the participants' computers.

- Some activities cause large amounts of data to be sent between 
  the computers in your meeting (for example, speaking and sharing 
  several applications while transferring a large file). In extreme 
  cases, this might cause computers in the meeting to become very 
  slow. To remedy this, stop one or more of the meeting activities.

- If you try to make a TCP/IP call on your local area network or 
  through a proxy server and MSN or Dial-Up Networking displays a 
  connection dialog box, you can disable this by clicking the 
  Internet icon in Control Panel and then making sure that Auto-
  Dial is not selected.

- Sharing of DirectX, OpenGL, MS-DOS(R), and graphics-intensive 
  games and AVIs does not work well and is not supported. 

- If different computers have different screen resolutions during 
  a meeting, the shared windows can be as large as the highest 
  resolution desktop allows. Users with lower resolution desktops 
  must scroll to view windows that don't fit their screens.

- You must have a 32-bit TCP/IP stack and Windows sockets 
  interface to use NetMeeting with TCP/IP. NetMeeting has 
  been tested with the 32-bit TCP/IP and Windows sockets built 
  into Windows 95, Windows 98, Windows NT 4.0, and Windows NT 5.0.

- Application-sharing, Whiteboard, and Chat might not work 
  properly between computers with different language settings 
  and keyboard layouts.

- NetMeeting supports using Windows 95, Windows 98, Windows NT 4.0
  with Service Pack 3 or later, and Windows NT 5.0 system policies
  to set default configurations in a corporate environment. 

  NetMeeting system policies are documented, and a system policy file
  is included in the NetMeeting Resource Kit. For more information
  about the NetMeeting Resource Kit, see
  http://www.microsoft.com/netmeeting/reskit.

- If NetMeeting hangs or faults when it starts, check to see if
  you have a damaged font in your fonts folder or if you have 
  an incompatible font installed such as the Franklin Gothic Book 
  font or the fonts installed by HP Fonts for Family.

- If you are using Internet Explorer 4.0 in Offline mode and 
  you try to start NetMeeting, NetMeeting will not automatically
  connect to the Internet. To work around this problem, dial 
  up using RAS (for Windows NT computers) or Dial-Up Networking 
  (for Windows 9x computers). Or, in Internet Explorer, click the 
  File menu, and then click Work Offline to clear the check mark.

- NetMeeting does not function properly over SLIRP connections 
  or other simulated SLIP/PPP connections.


PLACING A CALL
==============

You can place NetMeeting calls to multiple users. Any person in a
meeting can place NetMeeting calls to other people. In addition,
other people can join a NetMeeting call in progress by calling one
of the participants.

Warnings and Known Bugs
-----------------------
- If you cannot connect to someone by using their computer name, 
  try using their IP address.

- If you click someone's name in the Web directory and get a 
  message asking whether you would like to open or save the file, 
  select open file.

- If you click someone's name in the Web directory and get a 
  message saying that the file type is unrecognized, you need 
  to configure your browser to associate the ILS directory files 
  with NetMeeting.

  For instructions on how to do this, refer to your browser 
  documentation. You will need the following information:

  MIME file type: "text/iuls"
  Command line: "rundll32.exe msconf.dll,NewMediaPhone %l"

  MIME file type: "text/h323"
  Command line: "rundll32.exe msconf.dll,NewMediaPhone %l"

- Some ISDN devices are configured to automatically connect to 
  the network. This might cause the ISDN device to try to connect 
  to the network while NetMeeting is running. To stop this from 
  happening, turn off Auto-Dial on the ISDN device.

- If you do not see your name in the directory, you might not be 
  logged on, or you might be logged on to a different directory 
  server. To change the directory server you log on to, click the 
  Tools menu, click Options, click Calling, and then change your 
  Server Name. 

  To log on to the directory server, click the Call menu, and 
  then click Log On To [your directory server].

- If you have an active network connection using a network card 
  and a second active connection using a second network card, 
  you might not be able to connect to the directory.

- If you experience connection problems when dialing via a null
  modem connection, try lowering the baud rate for your modem.

- Some conference bridges (also known as Multipoint Conferencing 
  Units, or MCUs) are case-sensitive, so when you type the 
  conference name to place a call, you may need to use the same 
  capitalization as that shown on the bridge.

- To receive calls over a null modem cable, click the Tools menu, 
  click Options, and then click the Protocols tab. Select the 
  Null Modem protocol, and then click Properties. Select the COM 
  port to which the null modem cable is connected.

- NetMeeting does not detect incoming calls on a COM port to 
  which a null modem cable is connected. To receive calls over 
  a null modem cable, you must place a call on the COM port.

- Changes made to the COM port properties in NetMeeting apply 
  only in NetMeeting. It is recommended that you do not change 
  the COM port settings while you are placing or participating 
  in a NetMeeting call.

- NetMeeting uses the COM port typed into the New Call dialog box 
  to place the call, not the COM port specified in the Null Modem 
  Protocol Properties dialog box.

- NetMeeting can use only COM1 and COM2 to place and receive null 
  modem calls.

- Null modem calls at high baud rates may not work.

- If you connect to someone through a proxy server, you may need 
  to manually connect audio and video after joining the call.


RECEIVING A CALL
================

You are ready to receive incoming calls if you are running 
NetMeeting and have not selected Do Not Disturb on the Call menu.

Warnings and Known Bugs
-----------------------
- If you are not able to receive calls, it may be because your IP 
  address is registered incorrectly with the directory service. 
  You can prevent this by releasing the LAN IP address before 
  connecting to the Internet. To release the IP address, do the 
  following:

  On Windows 9x    Click the Start menu, click Run, and 
			 then type Winipcfg.exe

  On Windows NT    Click the Start menu, click Run, and 
 			 then type Ipconfig /release

SHARING AN APPLICATION
======================

Any person in a meeting can share an application with the other 
participants. When you share an application, other people can 
see the application. When you Collaborate, other people can both 
see and use the application.

Warnings and Known Bugs
-----------------------
- Windows NT users will be able to share applications if they 
  have installed Service Pack 3 or later for Windows NT 4.0.

- If NetMeeting is installed in a folder where the path 
  contains extended characters, application sharing might not 
  work.

- Sharing one Windows Explorer window shares all of them. If you 
  run a program while sharing Windows Explorer, the program will 
  also be shared.

  Examples of Windows Explorer windows include Control Panel, 
  Briefcase, the Received Files folder, or any Windows Explorer 
  folder.

- Internet Explorer 4.0 users: If you share a Windows Explorer 
  window, with collaboration enabled, and the person with whom 
  you are collaborating closes the window, all applications and 
  windows that you open afterwards will be shared.

  To undo sharing in this situation, open a Windows Explorer 
  window again, and un-share it.

- When you share an application and collaborate, remote users 
  can use the File Open and File Save dialog boxes in your 
  application to gain access to or delete files on your computer 
  or network.

  To stop someone from using your shared program while you do 
  not have control of the cursor, press ESC.

  To stop someone from using your shared program while you do 
  have control of the cursor, click the Stop Collaborating 
  button.

  It is recommended that you do not leave your computer unattended 
  while sharing an application and collaborating.

- When you launch another application from within the application 
  you are sharing (such as a Microsoft Excel spreadsheet from 
  within Microsoft Word), there's a possibility that the recently 
  launched application won't be shared properly.

- You cannot drag an object onto a shared application or drag an 
  object from a shared application to the desktop.

- When you share an application with an Input Method Editor 
  (IME), you should show the IME status bar so that other 
  people can use the mouse to activate the IME.

  If the IME does not support showing the status bar, or if other 
  people are having trouble activating the IME, you should 
  activate and deactivate the IME for them.

- If the IME window fails to repaint during a meeting, you can 
  cause it to repaint by clicking anywhere on the desktop.

- You may not be able to share applications on a computer with a 
  product installed that has application sharing or remote 
  control features.



WHITEBOARD
==========

The Whiteboard enables you to draw simultaneously with other 
people. Everyone in the meeting can see what is drawn on the 
Whiteboard. When one person in a meeting runs Whiteboard, it 
appears on everyone's screen.

Warnings and Known Bugs
-----------------------
- On a computer running Windows NT, if the folder in which 
  NetMeeting is installed contains spaces in its name, you 
  will not be able to run Whiteboard or Chat.

- Whiteboard does not maximize to the full size of an 1152 by 
  864 or larger display.


CHAT
====

Chat enables you to type messages for other users to see. When 
one person in a meeting runs Chat, it appears on everyone's 
screen.

Chat files are stored with the .txt file extension. If Microsoft 
Notepad, or another program that can read files in .txt format, 
is installed on your computer, it can be used to open Chat files.

Warnings and Known Bugs
-----------------------
- On a computer running Windows NT, if the folder in which 
  NetMeeting is installed contains spaces in its name, you will 
  not be able to run Whiteboard or Chat.


FILE TRANSFER
=============

- Files dragged onto the list of people on the Current Call tab 
  are sent to all the people in the meeting. 

- To send a file to a specific person, right-click that person's 
  name in the list of people in the meeting, and then click Send 
  File. 

- To send a file to everyone in the meeting, click the Tools
  menu, click File Transfer, and then click Send File.


Warnings and Known Bugs
-----------------------

- If you try to send a shortcut to a file, the actual file will 
  be sent instead.

- Exchanging files with Intel ProShare 2.0 does not always work 
  properly.


AUDIO COMMUNICATION
===================

- Audio is supported only over TCP/IP and with one other person.

- Sound quality can vary significantly depending on your sound 
  card and microphone. 

- Using full-duplex audio can require both more bandwidth and 
  more CPU than using half-duplex audio, and therefore may result 
  in poor sound quality.

- If you modify your sound card device driver in any way, such 
  as upgrading to a full-duplex driver, you will need to run the 
  Audio Tuning Wizard again in order for NetMeeting to work 
  correctly.