Windows:

• System software: Windows 98 or higher.
• Processor speed: 333 MHz or better; a Pentium 2 or better.
• System RAM: minimum of 64 Mb.

Macintosh:

• System software: MacOS X (version 10.1 or higher)
• Processor speed: 233 MHz or better; a G3 or better.
• System RAM: minimum of 128 Mb (depending on the model, a small portion can be virtual, no more than 32 Mb).

All computers:

• Screen size/resolution: 800x600 pixels minimum.

Web Browser and Plug-ins

• System Requirements
• Browser Requirements
• Browser Plugins
• Internet Connection
• Network Ports

BROWSER

The minimum browser requirements for KREC are:

• Internet Explorer 5 or higher.
• Netscape Navigator 7.x or higher
• On Mac OS X only: Safari 1.2.1

To check your browser version under Windows, select "About..." from the browser's "Help" menu. To check on a Macintosh, select "About [browsername]" from the browser's application menu. You can upgrade your browser by going to the appropriate web page:

• Download Internet Explorer: http://www.microsoft.com/windows/ie/downloads
• Download Netscape Navigator: http://www.netscape.com/download/
• Download Safari: Use the Softare Update feature under the Apple menu to check for new versions.

BROWSER PLUG-INS

Your browser must also have plug-ins for Shockwave or Flash, and the appropriate media type. If Screen Sharing will be used, you also need Java; Mac OS X users should download the latest Java via Software Update, while the best option for Windows users is Sun Java, which can be downloaded here:

• Download Sun Java: http://java.com/en/download/

About media type: The following specifies the media types and versions supported by KREC, although your event may have more specific requirements. Check with the event coordinator if you are not sure what the requirements are. All media requires certain codecs, which you may or may not have installed already (especially if they are new). Your media player may not able to download a codec automatically if the media player preferences are not set appropriately. Proxy server settings may also pose an issue. Check the "Help" menu within the standalone media player. For Windows Media, you can also find some tips here: I cannot see video or hear audio in a presentation.

• Real Player 6.0 or higher: http://www.real.com/player/
• Windows Media 7.0 or higher: http://windowsmedia.com/download
• QuickTime 5.0 or higher: http://www.apple.com/quicktime/download/
• Shockwave 8.5.1 or higher: http://www.macromedia.com/shockwave/download/
• Flash 6.0 or higher: http://www.macromedia.com/go/getflashplayer/

Note to Mac OS X users: if you have trouble using Shockwave 8.5.1, update to the latest version (10.1 as of this writing).

If you are not sure your computer has all the necessary web browser plug-ins installed to use KREC, try the preflight page mentioned at the beginning of this entry.

A 56k modem connection is the minimum speed required, although actual requirements depend on the media bitrate(s) used in your particular presentation, assuming media is used at all. 56k should handle audio-only fine; video performance, however, may be inconsistent even when optimized for 56k, due to the nature of modem connections (higher bitrates will probably not play at all). For optimal viewing, a higher connection speed is recommended (cable, DSL, T1, etc).

In addition, one or more network ports need to be open for communication between your computer and the KREC server hosting the presentation. At a minimim, port 80 must be open for web traffic. Whether or not other ports are needed depends on which KREC features and media types are used in the presentation. This is usually only an issue when there is a firewall between the two machines. The most commonly used ports include:

• 1626 - preferred to enable the most efficient communication between the Player and KREC server (although a "firewall mode" provides a work-around).
• 1755 - if Windows Media is used.
• 660x - if the Screen Sharing feature is used; this can be within a certain range, so ask the event coordinator.

What network ports are required for KREC?

The exact ports that must be open on a network depend on:

• Which KREC features you use.
• Which media type you use.
• Your network location in relation to the KREC server.
• The location of others outside your organization who must access the KREC server, if any.

If you have a closed network behind a firewall and plan to use your own KREC mainly within that network, you may only need to open a port to enable remot login (so that Avacast can provide timely support and server updates). If you plan to access an KREC server on a network different than your own (e.g. you are an ASP client) or you want to allow external users to access an KREC server at your location (e.g. you are offering online classes to the public), you may need to open more ports to enable login for both end users and Administrators, allow streaming, allow KREC sharing, etc.

• 13 - TCP - for Atomic Clock Sync (optional) See note#3
• 21 - TCP - for FTP (for server maintenance and/or archiving) See note#5
• 25 - TCP - for SMTP (to use VOD email feature - optional) See note#6
• 80 - TCP - for the web server
• 123 - UDP – for the Windows Time service See note#3 (optional)
• 1626 - TCP - for KREC messaging; required by the Administrator and Super Administrator See note#4
• 1627 - TCP - for more efficient Flash Player performance/communication (new with version 5.0)
• 1755 - UDP and TCP - for Windows Media streaming See note#1
• 1935 - TCP for Multipoint media streaming (new with version 5.0) See note#7
• 3389 - TCP - for RDP, i.e. Remote Desktop (if this will be used for remote login - can use VNC instead)
• 554 - TCP - for Real Media or QuickTime RTSP See note#1
• 5900 - TCP - for VNC, i.e. Virtual Network Computing (for remote login -- can use RDP instead)
• 7070 - UDP - alternative for Real Media or QuickTime RTSP See note#1
• 8000 - TCP - for remote control of KREC custom WMP encoder (can be changed)
• 8001 - TCP - for remote control of KREC custom Real encoder
• 8080 - TCP - for the Windows Media encoder-to-streaming server communication (can be changed)
• 6101-6199 - TCP - for Screen Sharing clients See note#2
• 5501-5599 - TCP - for Screen Sharing hosts See note#2