Leaked source code of windows server 2003
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

823 lines
31 KiB

  1. ------------------------------------------------------------
  2. README for Microsoft NetMeeting 2.1
  3. October 1997
  4. ------------------------------------------------------------
  5. (c) Copyright Microsoft Corporation, 1997
  6. This document provides complementary or late-breaking information
  7. to supplement existing documentation.
  8. ------------------------
  9. HOW TO USE THIS DOCUMENT
  10. ------------------------
  11. To view Netmeet.txt on screen in Notepad, maximize the Notepad
  12. window.
  13. To print Netmeet.txt, open it in Notepad or another word
  14. processor, and then use the Print command on the File menu.
  15. CONTENTS
  16. ========
  17. SYSTEM REQUIREMENTS AND SETUP
  18. USING MICROSOFT NETMEETING
  19. PLACING A CALL
  20. RECEIVING A CALL
  21. SHARING AN APPLICATION
  22. WHITEBOARD
  23. CHAT
  24. FILE TRANSFER
  25. AUDIO COMMUNICATION
  26. HANGING UP
  27. VIDEO
  28. GENERAL KNOWN ISSUES
  29. WINDOWS NT ISSUES
  30. SYSTEM REQUIREMENTS AND SETUP
  31. =============================
  32. Microsoft(R) NetMeeting(R) enables real-time audio, video, and
  33. data communication over the Internet.
  34. In order to use Microsoft NetMeeting, you must have the
  35. following configuration:
  36. - Microsoft Windows(R) 95 or Windows(R) 98
  37. - At least a 486/66 processor with 8 megabytes of RAM
  38. (Pentium with 12 MB of RAM recommended)
  39. --or--
  40. - Microsoft Windows NT(R) version 4.0
  41. - At least a 486/66 processor with 16 megabytes of RAM
  42. - Microsoft Windows NT 4.0 Service Pack 3 required to enable
  43. sharing applications on Windows NT
  44. IMPORTANT NOTES:
  45. * NetMeeting does not run on Windows version 3.1 or beta
  46. versions of Windows 98 older than Beta 3.
  47. * It is strongly recommended that you uninstall earlier beta
  48. versions of Microsoft NetMeeting before installing NetMeeting
  49. 2.1.
  50. - If you use special characters, such as "\\" or double-byte
  51. characters, when typing the installation location for NetMeeting
  52. during setup, NetMeeting may not install correctly.
  53. - NetMeeting no longer supports placing calls over IPX or over
  54. PSTN.
  55. - NetMeeting works best with a fast Internet connection (a 28.8k-
  56. baud or faster modem or a local area network).
  57. - To use the audio features of NetMeeting, you need a sound card,
  58. speakers, and a microphone.
  59. - To send video with NetMeeting, you need either a video-capture
  60. card and camera or a video camera that connects through your
  61. computer's parallel (printer) port. You will not be able to
  62. send video on some computers with a processor slower than a
  63. Pentium.
  64. Computers with a bidirectional (ECP or EPP) parallel port will
  65. perform noticeably better with parallel port video cameras than
  66. computers with a unidirectional parallel port.
  67. Cameras that connect to a video-capture card will use less of
  68. your computer's processor than cameras that connect through your
  69. computer's parallel port. It is recommended that you do not use
  70. a color parallel port camera unless your computer is at least a
  71. Pentium 133.
  72. - The application-sharing feature may not perform well while you
  73. are using audio and video and are connected over a slow
  74. connection. Additionally, you might experience "choppy" audio
  75. while using video.
  76. The default setting for video over a 28.8-baud modem connection
  77. is medium quality. To change this setting, click the Tools menu,
  78. click Options, click the Video tab, and then change the Video
  79. Quality option.
  80. - Windows NT users will be able to share applications if they have
  81. installed Service Pack 3 for Windows NT 4.0.
  82. For more information about NetMeeting, including the NetMeeting
  83. Resource Kit, see http://www.microsoft.com/netmeeting/.
  84. For the NetMeeting Software Development Kit (SDK), see
  85. http://www.microsoft.com/netmeeting/sdk.
  86. For information about product support, see the Support.txt
  87. file in your Windows or NetMeeting program directory.
  88. To uninstall Microsoft NetMeeting
  89. ---------------------------------
  90. 1. In Control Panel, double-click the Add/Remove Programs icon.
  91. 2. On the Install/Uninstall tab, click Microsoft NetMeeting, and
  92. then click Add/Remove Programs.
  93. 3. If a dialog box appears asking if you want to restart your
  94. computer, click Yes.
  95. -or-
  96. 1. In Control Panel, double-click the Add/Remove Programs icon.
  97. 2. On the Windows Setup tab, click Communications, and then click
  98. Details.
  99. 3. Clear the Microsoft NetMeeting check box.
  100. Warnings and Known Bugs
  101. -----------------------
  102. - If you uninstall Windows NT Service Pack 3 after installing
  103. NetMeeting 2.1, you will receive an error message when you
  104. restart your computer. To prevent this, carry out the following
  105. steps:
  106. 1. Close the error message window.
  107. 2. In the Display properties dialog box, click Cancel.
  108. 3. In Control Panel, click the Devices icon.
  109. 4. Click mnmdd, and then click the Startup button.
  110. 5. Change the Startup Type from System to Disabled, and then
  111. click OK.
  112. 6. Restart your computer so the change can take effect.
  113. USING MICROSOFT NETMEETING
  114. ==========================
  115. - Microsoft NetMeeting includes support for the H.323 audio
  116. and video conferencing standard. NetMeeting can be used to
  117. place calls to and receive calls from products that are H.323-
  118. compatible, including the Intel Internet Video Phone. With
  119. appropriate equipment and services that are currently under
  120. development by third parties, NetMeeting can place a call to
  121. a telephone using an H.323 gateway.
  122. - Microsoft maintains the following directory servers on the
  123. Internet:
  124. ils.microsoft.com
  125. ils1.microsoft.com
  126. ils2.microsoft.com
  127. ils3.microsoft.com
  128. ils4.microsoft.com
  129. ils5.microsoft.com
  130. You can use one of these even if it does not appear in the list
  131. of servers in the wizard.
  132. You can also use the following directory servers not maintained
  133. by Microsoft:
  134. ils.four11.com
  135. ils.business.four11.com
  136. ils.family.four11.com
  137. NOTE
  138. * You will not be able to use these servers to locate people on
  139. the Internet if you connect to the Internet through a proxy
  140. server that does not support Remote WinSock.
  141. - Audio and video work only over TCP/IP and with one other person
  142. at a time.
  143. - If you use this version of NetMeeting to call someone who
  144. is using NetMeeting 2.0, the call-switching feature may not work
  145. correctly.
  146. - This version of NetMeeting enables up to 32 users to share an
  147. application. However if a computer running NetMeeting 2.0 is in
  148. the conference and more than three users are sharing, that computer
  149. will not be able to host an application. In addition, you can be
  150. connected to only one other person with audio and video at a time.
  151. The total number of people who can successfully participate
  152. in your meeting will vary based on available network bandwidth
  153. and the speed of the participants' computers.
  154. - Some activities cause large amounts of data to be sent between
  155. the computers in your meeting (for example, speaking and sharing
  156. several applications while transferring a large file). In extreme
  157. cases, this might cause computers in the meeting to become very
  158. slow. To remedy this, stop one or more of the meeting activities.
  159. - If you try to make a TCP/IP call on your local area network or
  160. through a proxy server and MSN or Dial-Up Networking displays a
  161. connection dialog box, you can disable this by clicking the
  162. Internet icon in Control Panel and then making sure that Auto-
  163. Dial is not selected.
  164. - Sharing of DirectX, OpenGL, MS-DOS(R), and graphics-intensive
  165. games and AVIs does not work well and is not supported.
  166. - If different computers have different screen resolutions during
  167. a meeting, the shared windows can be as large as the highest
  168. resolution desktop allows. Users with lower resolution desktops
  169. must scroll to view windows that don't fit their screens.
  170. - You must have a 32-bit TCP/IP stack and Windows sockets
  171. interface to use NetMeeting with TCP/IP. NetMeeting has
  172. been tested with the 32-bit TCP/IP and Windows sockets built
  173. into Windows 95 and Windows NT version 4.0.
  174. - Application-sharing, Whiteboard, and Chat might not work
  175. properly between computers with different language settings
  176. and keyboard layouts.
  177. - Microsoft NetMeeting supports using Windows 95 and Windows NT
  178. version 4.0 system policies to set default configurations in
  179. a corporate environment.
  180. Microsoft NetMeeting system policies are documented, and a
  181. system policy file is included in the NetMeeting Resource Kit.
  182. For more information about the NetMeeting Resource Kit, see
  183. http://www.microsoft.com/netmeeting/reskit.
  184. - If NetMeeting hangs when it starts, check to see whether
  185. there are damaged fonts in your Fonts folder.
  186. - If you are using Internet Explorer 4.0 in Offline mode and
  187. you try to start NetMeeting, NetMeeting will not automatically
  188. connect to the Internet. To work around this problem, dial
  189. up using RAS (for Windows NT computers) or Dial-Up Networking
  190. (for Windows 95 computers). Or, in Internet Explorer, click the
  191. File menu, and then click Work Offline to clear the check mark.
  192. - NetMeeting does not function properly over SLIRP connections
  193. or other simulated SLIP/PPP connections.
  194. PLACING A CALL
  195. ==============
  196. You can place Microsoft NetMeeting calls to multiple users. Any
  197. person in a meeting can place NetMeeting calls to other people.
  198. In addition, other people can join a NetMeeting call in progress
  199. by calling one of the participants.
  200. Warnings and Known Bugs
  201. -----------------------
  202. - If you cannot connect to someone by using their computer name,
  203. try using their IP address.
  204. - If you click someone's name in the Web directory and get a
  205. message asking whether you would like to open or save the file,
  206. select open file.
  207. - If you click someone's name in the Web directory and get a
  208. message saying that the file type is unrecognized, you need
  209. to configure your browser to associate the ILS directory files
  210. with Microsoft NetMeeting.
  211. For instructions on how to do this, refer to your browser
  212. documentation. You will need the following information:
  213. MIME file type: "text/iuls"
  214. Command line: "rundll32.exe msconf.dll,NewMediaPhone %l"
  215. MIME file type: "text/h323"
  216. Command line: "rundll32.exe msconf.dll,NewMediaPhone %l"
  217. - Some ISDN devices are configured to automatically connect to
  218. the network. This might cause the ISDN device to try to connect
  219. to the network while NetMeeting is running. To stop this from
  220. happening, turn off Auto-Dial on the ISDN device.
  221. - If you do not see your name in the directory, you might not be
  222. logged on, or you might be logged on to a different directory
  223. server. To change the directory server you log on to, click the
  224. Tools menu, click Options, click Calling, and then change your
  225. Server Name.
  226. To log on to the directory server, click the Call menu, and
  227. then click Log On To [your directory server].
  228. - If you have an active network connection using a network card
  229. and a second active connection using a second network card,
  230. you might not be able to connect to the directory.
  231. - If you experience connection problems when dialing via a null
  232. modem connection, try lowering the baud rate for your modem.
  233. - Some conference bridges (also known as Multipoint Conferencing
  234. Units, or MCUs) are case-sensitive, so when you type the
  235. conference name to place a call, you may need to use the same
  236. capitalization as that shown on the bridge.
  237. - To receive calls over a null modem cable, click the Tools menu,
  238. click Options, and then click the Protocols tab. Select the
  239. Null Modem protocol, and then click Properties. Select the COM
  240. port to which the null modem cable is connected.
  241. - NetMeeting does not detect incoming calls on a COM port to
  242. which a null modem cable is connected. To receive calls over
  243. a null modem cable, you must place a call on the COM port.
  244. - Changes made to the COM port properties in NetMeeting apply
  245. only in NetMeeting. It is recommended that you do not change
  246. the COM port settings while you are placing or participating
  247. in a NetMeeting call.
  248. - NetMeeting uses the COM port typed into the New Call dialog box
  249. to place the call, not the COM port specified in the Null Modem
  250. Protocol Properties dialog box.
  251. - NetMeeting can use only COM1 and COM2 to place and receive null
  252. modem calls.
  253. - Null modem calls at high baud rates may not work.
  254. - If you connect to someone through a proxy server, you may need
  255. to manually connect audio and video after joining the call.
  256. RECEIVING A CALL
  257. ================
  258. You are ready to receive incoming calls if you are running
  259. Microsoft NetMeeting and have not selected Do Not Disturb on
  260. the Call menu.
  261. Warnings and Known Bugs
  262. -----------------------
  263. - If you are not able to receive calls, it may be because your IP
  264. address is registered incorrectly with the directory service.
  265. You can prevent this by releasing the LAN IP address before
  266. connecting to the Internet. To release the IP address, do the
  267. following:
  268. On Windows 95 Click the Start menu, click Run, and
  269. then type Winipcfg.exe
  270. On Windows NT Click the Start menu, click Run, and
  271. then type Ipconfig /release
  272. SHARING AN APPLICATION
  273. ======================
  274. Any person in a meeting can share an application with the other
  275. participants. When you share an application, other people can
  276. see the application. When you Collaborate, other people can both
  277. see and use the application.
  278. Warnings and Known Bugs
  279. -----------------------
  280. - Windows NT users will be able to share applications if they
  281. have installed Service Pack 3 for Windows NT 4.0.
  282. - If NetMeeting is installed in a directory where the path
  283. contains extended characters, application sharing might not
  284. work.
  285. - Sharing one Windows Explorer window shares all of them. If you
  286. run a program while sharing Windows Explorer, the program will
  287. also be shared.
  288. Examples of Windows Explorer windows include Control Panel,
  289. Briefcase, the Received Files folder, or any Windows Explorer
  290. folder.
  291. - Internet Explorer 4.0 users: If you share a Windows Explorer
  292. window, with collaboration enabled, and the person with whom
  293. you are collaborating closes the window, all applications and
  294. windows that you open afterwards will be shared.
  295. To undo sharing in this situation, open a Windows Explorer
  296. window again, and un-share it.
  297. - When you share an application and collaborate, remote users
  298. can use the File Open and File Save dialog boxes in your
  299. application to gain access to or delete files on your computer
  300. or network.
  301. To stop someone from using your shared program while you do
  302. not have control of the cursor, press ESC.
  303. To stop someone from using your shared program while you do
  304. have control of the cursor, click the Stop Collaborating
  305. button.
  306. It is recommended that you do not leave your computer unattended
  307. while sharing an application and collaborating.
  308. - When you launch another application from within the application
  309. you are sharing (such as a Microsoft Excel spreadsheet from
  310. within Microsoft Word), there's a possiblity that the recently
  311. launched application won't be shared properly.
  312. - You cannot drag an object onto a shared application or drag an
  313. object from a shared application to the desktop.
  314. - When you share an application with an Input Method Editor
  315. (IME), you should show the IME status bar so that other
  316. people can use the mouse to activate the IME.
  317. If the IME does not support showing the status bar, or if other
  318. people are having trouble activating the IME, you should
  319. activate and deactivate the IME for them.
  320. - If the IME window fails to repaint during a meeting, you can
  321. cause it to repaint by clicking anywhere on the desktop.
  322. - You may not be able to share applications on a computer with a
  323. product installed that has application sharing or remote
  324. control features.
  325. WHITEBOARD
  326. ==========
  327. The Whiteboard enables you to draw simultaneously with other
  328. people. Everyone in the meeting can see what is drawn on the
  329. Whiteboard. When one person in a meeting runs Whiteboard, it
  330. appears on everyone's screen.
  331. Warnings and Known Bugs
  332. -----------------------
  333. - On a computer running Windows NT, if the directory in which
  334. NetMeeting is installed contains spaces in its name, you
  335. will not be able to run Whiteboard or Chat.
  336. - Whiteboard does not maximize to the full size of an 1152 by
  337. 864 or larger display.
  338. CHAT
  339. ====
  340. Chat enables you to type messages for other users to see. When
  341. one person in a meeting runs Chat, it appears on everyone's
  342. screen.
  343. Chat files are stored with the .txt file extension. If Microsoft
  344. Notepad, or another program that can read files in .txt format,
  345. is installed on your computer, it can be used to open Chat files.
  346. Warnings and Known Bugs
  347. -----------------------
  348. - On a computer running Windows NT, if the directory in which
  349. NetMeeting is installed contains spaces in its name, you will
  350. not be able to run Whiteboard or Chat.
  351. FILE TRANSFER
  352. =============
  353. - Files dragged onto the list of people on the Current Call tab
  354. are sent to all the people in the meeting.
  355. - To send a file to a specific person, right-click that person's
  356. name in the list of people in the meeting, and then click Send
  357. File.
  358. - To send a file to everyone in the meeting, click the Tools
  359. menu, click File Transfer, and then click Send File.
  360. Warnings and Known Bugs
  361. -----------------------
  362. - If you try to send a shortcut to a file, the actual file will
  363. be sent instead.
  364. - Exchanging files with Intel ProShare 2.0 does not always work
  365. properly.
  366. AUDIO COMMUNICATION
  367. ===================
  368. - Audio is supported only over TCP/IP and with one other person.
  369. - Sound quality can vary significantly depending on your sound
  370. card and microphone.
  371. - Using full-duplex audio can require both more bandwidth and
  372. more CPU than using half-duplex audio, and therefore may result
  373. in poor sound quality.
  374. - If you modify your sound card device driver in any way, such
  375. as upgrading to a full-duplex driver, you will need to run the
  376. Audio Tuning Wizard again in order for NetMeeting to work
  377. correctly.
  378. Warnings and Known Bugs
  379. -----------------------
  380. - If you are using a Videum (Winnov) video-capture card and
  381. have the new 2.0 drivers, you can change the audio input for
  382. the card by opening the Videum Configure program (under the
  383. Winnov Videum program group) and selecting the desired audio
  384. input for the video input being used with Netmeeting. The default
  385. is to use the Camera microphone for the MXC video connection
  386. and Line Input for all other video connections. After you do
  387. this, the correct audio input will be selected when you start
  388. NetMeeting.
  389. - Audio input for users of Winnov cameras will automatically be
  390. switched whenever video is in use. If your video is connected
  391. using the MXC connection, the camera input will be used for
  392. audio. If your video is connected using the Composite or
  393. S-Video connection, the Line Input will be used for audio.
  394. You can solve this problem by upgrading to the new 2.0 drivers
  395. and by using the Videum Configuration application.
  396. - Users of Microsoft NetMeeting and Intel Internet Video Phone
  397. can talk to each other only if both users have a computer with
  398. a Pentium processor.
  399. - If you have a SoundBlaster sound card with full-duplex sound
  400. enabled, and you have problems with your computer locking up
  401. when using NetMeeting, you may need to update your Sound-
  402. Blaster drivers.
  403. - You may receive a message in the Audio Tuning Wizard that
  404. explains that your sound card is unsupported. This occurs when
  405. the sound card does not support some of the features required
  406. for it to be supported by NetMeeting. The audio features in
  407. NetMeeting may work even if you get this message, but you might
  408. experience poor audio quality.
  409. If your sound card is unsupported, you might want to contact
  410. the manufacturer to find out if newer sound card drivers are
  411. available.
  412. - If you are experiencing "choppy" full-duplex sound quality, try
  413. switching NetMeeting to half-duplex sound quality. To do this,
  414. carry out the following steps:
  415. 1. Make sure that you are not in a NetMeeting call.
  416. 2. On the Tools menu, click Options.
  417. 3. On the Audio tab, clear the Enable Full Duplex Audio check
  418. box.
  419. It is recommended that you not switch between full-duplex and
  420. half-duplex audio while in a meeting with audio.
  421. - If you are having problems with your audio quality or sound
  422. card when using NetMeeting, the problems could be related to
  423. your hardware configuration or driver installation. To see
  424. the latest support information, click the Help menu, and then
  425. click Online Support.
  426. - If your computer has more than one audio device, you should
  427. make sure that the audio devices selected in the Audio Tuning
  428. Wizard match the selections in the Multimedia properties in
  429. Control Panel.
  430. - If you upgrade your computer's processor, you should re-run
  431. the audio tuning wizard.
  432. - Full-duplex audio might not work with Media Vision Pro Audio
  433. Spectrum 16 sound cards.
  434. - Computers with a 486 processor will not be able to use audio
  435. with other software based on the H.323 audio conferencing
  436. standard over a Dial-Up Networking (modem) connection. They
  437. will be able to use audio with other NetMeeting users over
  438. a Dial-Up Networking connection or with other H.323-based
  439. audio conferencing products over a local area network (LAN).
  440. - When you are in an audio conference using NetMeeting, an
  441. application that has the ability to record sound, such as
  442. Microsoft PowerPoint, will appear to be recording sound
  443. as instructed. However, since NetMeeting is already using
  444. the sound card, the other application is not actually
  445. recording.
  446. - If you have a Tecra 740, you may need to manually set
  447. the microphone volume level in the Multimedia properties
  448. in Control Panel.
  449. - If you experience poor audio quality, try clearing the
  450. Microphone check box and then selecting it again.
  451. - If you are using a Gravis Ultrasound sound card and you
  452. are experiencing choppy audio quality, try the following:
  453. 1. Make sure that you are not in a NetMeeting call.
  454. 2. On the Tools menu, click Options.
  455. 3. On the General tab, in the Network bandwidth section,
  456. select a bandwidth setting that is slower than the
  457. current selection.
  458. HANGING UP
  459. ==========
  460. When you hang up, you disconnect anyone you called or anyone
  461. who called you. If the disconnected users have invited or
  462. accepted other users into the meeting, they are also disconnected.
  463. Audio connections between people might not be disconnected.
  464. Warnings and Known Bugs
  465. -----------------------
  466. - If you are using a 56 kps modem in a NetMeeting call with two
  467. or more other people, hanging up may not work correctly.
  468. Switching audio and video during the call may also cause one
  469. or more participants to be disconnected.
  470. VIDEO
  471. =====
  472. - To use the video features of NetMeeting, you need either a
  473. video-capture card and camera or a video camera that connects
  474. through your computer's parallel (printer) port. Sending video
  475. does not work on some computers that have a processor slower
  476. than a Pentium.
  477. - Video is supported only over TCP/IP and with only one other
  478. person at a time.
  479. - Running video in a multiuser meeting can negatively impact
  480. performance on all the computers in the meeting. For example,
  481. opening a video window while sharing an application can make
  482. it difficult for others to take control of the application.
  483. - If you have more than one video device installed, or you have
  484. not properly uninstalled a video device that was previously
  485. installed, you might not be able to use video.
  486. - If your video device is not properly uninstalled and you have
  487. enabled video in NetMeeting, the remaining camera software
  488. may warn you repeatedly that it cannot find the camera.
  489. - If your computer's processor is slower than a Pentium, sending
  490. video may result in poor audio and video quality.
  491. - Computers with a bidirectional (ECP or EPP) parallel port will
  492. perform noticeably better with parallel video cameras than
  493. computers with a unidirectional parallel port.
  494. - Cameras that connect to a video-capture card will use less of
  495. your computer's processor than cameras that connect through
  496. your computer's parallel port. It is recommended that you not
  497. use a color parallel port camera unless your computer is at
  498. least a Pentium 133.
  499. - If you disconnect your camera while using the video features
  500. in NetMeeting, your camera's software may display messages
  501. telling you that the camera is not responding. To disable
  502. these messages, click the Tools menu, click Options, click
  503. Video, and then clear the Automatically Send Video At The
  504. Start Of Each Call check box.
  505. - It is recommended that you not run another program that uses
  506. video while running NetMeeting.
  507. - If some areas of your video window contain the wrong colors,
  508. your camera might be aimed at an area with insufficient light.
  509. Some video drivers might provide a low-light filter option.
  510. - If you are using the video features in a dark area, some
  511. cameras will cause your computer to become extremely slow
  512. and unresponsive.
  513. - If you use a Black and White Connectix Camera, it is
  514. recommended that you use the version 2.1 update (or newer)
  515. of the video drivers. You can download drivers from
  516. http://www.connectix.com.
  517. - Audio input for users of Winnov cameras will automatically be
  518. switched whenever video is in use. If your video is connected
  519. using the MXC connection, the camera input will be used for
  520. audio. If your video is connected using the Composite or
  521. S-Video connection, the Line Input will be used for audio.
  522. - With some cameras, you may be able to reduce CPU usage by
  523. manually adjusting the settings in the Source and Format
  524. dialog boxes instead of letting the video driver software
  525. do it automatically.
  526. GENERAL KNOWN ISSUES
  527. ====================
  528. - You cannot run ReachOut 5.0 on computers on which Microsoft
  529. NetMeeting is installed.
  530. - To find the name that NetMeeting uses as your NetBIOS name,
  531. carry out the following steps:
  532. 1. In Control Panel, click the Network icon, and then click the
  533. Identification tab.
  534. 2. Select the Computer Name text box.
  535. - If you use User Profiles for multiple users to maintain your
  536. Windows preferences on all the computers on a network, you
  537. might have to run the Audio Tuning Wizard again when you switch
  538. computers.
  539. - Both Microsoft FrontPage and Microsoft NetMeeting currently use
  540. the same file type (.cnf). NetMeeting uses this file type for
  541. Speed Dials.
  542. - When you are in a meeting, your Clipboard is shared with
  543. everyone else in the meeting. This enables you to paste objects
  544. other people cut or copy to the Clipboard into your local
  545. programs. You can set a system policy that disables Clipboard
  546. sharing.
  547. - If you are running Windows 95 Version 4.00.950B, and you cancel
  548. the Dial-Up Networking dialog box that appears when you start
  549. NetMeeting, NetMeeting appears to stop responding; however,
  550. NetMeeting will work properly after about two minutes. However,
  551. you will not be logged onto the directory server until you manually
  552. connect to your Internet service provider and then on the Call
  553. menu, choose Log On To [your directory server].
  554. - If you create a SpeedDial shortcut, clicking Send To Mail
  555. Recipient will work only if your e-mail program is MAPI-aware
  556. (for example, Microsoft Outlook Express).
  557. - You can return calls by using the History tab only if
  558. the person who called you was using NetMeeting 2.0 or
  559. NetMeeting 2.1.
  560. - If you are using NetMeeting over a 28.8 kbp connection, you may
  561. be able to get better audio and video quality by clicking the
  562. Tools menu, clicking Options, and then choosing ISDN or Local
  563. Area Network from the Network Bandwidth section.
  564. WINDOWS NT ISSUES
  565. =================
  566. - If you use Windows NT, you will be able to share applications
  567. if you have installed Service Pack 3 for Windows NT 4.0.
  568. - Enabling Application Sharing on Windows NT may negatively
  569. affect the performance of your display driver. This will affect
  570. the rate at which information is drawn on the screen.
  571. - Some Creative Labs SoundBlaster drivers (specifically those
  572. posted on their Web site January 15, 1997) are not compatible
  573. with NetMeeting. SoundBlaster drivers that come with Windows
  574. NT 4.0. do work with NetMeeting, as do the more recently
  575. posted drivers, which also support full-duplex audio.
  576. - If you use Windows NT, you will experience problems if
  577. you share a 32-bit application and then insert an object
  578. that is a package. This opens the Object Packager, which is
  579. automatically shared and will subsequently fault. This fault
  580. will not cause the original shared application or NetMeeting
  581. to fault, only the Object Packager.
  582. - If you enabled the floating point workaround during
  583. installation of Windows NT on a computer that is equipped
  584. with a flawed Intel Pentium chip, NetMeeting audio quality
  585. will be poor, or audio will not work at all.
  586. - When you share a 16-bit application, all the 16-bit applications
  587. that are running on your computer will also automatically be
  588. shared.
  589. - If you are using NetMeeting on Windows NT and you are unable to
  590. receive a call, restart your computer and try again.
  591. - If you do not have a sound card, you will need to manually
  592. specify the bandwidth of your connection. To do this, click
  593. the Tools menu, click Options, and then click Network Bandwidth.
  594. - You may need to uninstall Dial-Up Networking in order to log
  595. on to a Directory Server via a proxy.
  596. - If, after placing a call, you see a message for more than one
  597. minute that NetMeeting is waiting for a response from the
  598. other person, quit NetMeeting and then try to contact the
  599. person again.
  600. - If you are unable to see a video image in NetMeeting, it is
  601. recommended that you upgrade to DirectDraw 3.0 or newer.
  602. - If you suspend your computer, or if it is set to suspend
  603. automatically, you should quit and then restart NetMeeting
  604. after resuming.
  605. - If you receive a SpeedDial in an e-mail message, your mail
  606. program may convert it to a text (.txt) file. You will be
  607. able to use it as a SpeedDial if you rename it with a .cnf
  608. extension.