Accessibility
 
Home / Products / FlashCom / Support / Release Notes
 
Macromedia Flash Communication Server MX 1.0 release notes
This document addresses issues, primarily for Macromedia Flash Communication Server MX developers, which are not discussed in the Macromedia Flash Communication Server MX documentation. This document may be updated periodically as more information becomes available.
System requirements
Known issues in Macromedia Flash Communication Server MX

Reporting a bug to the Macromedia Flash Communication Server MX team

System requirements

Platform    Requirements
For Development:
Windows  
  • Flash MX
  • Windows XP Professional, Windows XP Home, Windows 2000 Professional or Windows NT 4.0 Workstation SP6 or later.
    (Windows 98/ME supported for application authoring only).
  • 64 MB Available RAM (128 MB Recommended)
  • 50 MB of available disk space
  • CD-ROM Drive
Macintosh
(Application authoring only)
 
  • Flash MX
  • 64 MB Available RAM (128 MB Recommended)
  • 10 MB of available disk space
  • CD-ROM Drive
For Deployment:
   
  • Windows 2000 Server, Windows NT 4.0 Server (SP6 or later), Windows XP Professional, Windows XP Home, Windows 2000 Professional or Windows NT 4.0 Workstation SP6 or later.
  • Pentium III 500 MHz processor or better (dual Pentium 4 or better recommended)
  • 256 MB Available RAM (512 MB recommended)
  • 50 MB of available disk space
  • CD-ROM Drive

Known issues in Macromedia Flash Communication Server MX 1.0

If you have either the Microsoft IIS 4.0 or higher or Apache web server installed, FlashCom will ask if you want the applications directory installed into your web server's document root directory (i.e., c:\inetpub\wwwroot\flashcom). If you prefer to install this directory elsewhere, then follow the prompts in the installer dialogs to choose the installation location.
The FlashCom server requires file system read/write permissions to access all application files (FLV files, stream index files, shared object files, etc.).

Regarding servers running more than one virtual host:

    As a security feature, only full server administrators can start a stopped vhost. However, an administrator may restart a vhost for which he/she is an administrator (if the vhost is already running). Note that the default vhost (_defaultVHost_) cannot be put in a stopped state. It may, however, be restarted (which is functionally equivalent to stopping and starting).
    Note also that the administrative user tree view shows only users listed in the Server.xml file. If a vhost has no administrative user, it will not be shown in the list. If you add vhosts and wish to use the admin console to create administrators for the vhost, you can manually edit the scope field on the Admin Users panel and specify the new vhost.
    Vhost administrators are not permitted to add or remove other vhost administrator accounts nor can they change the passwords of other vhost administrators.
For the best experience with FlashCom Help, we recommend that you use a browser with Java VM support, such as Internet Explorer 6.0 or later. FlashCom Help also supports Netscape Navigator 6.1 or later on Windows and Macintosh. Running Macromedia Flash MX and FlashCom Help simultaneously on a Macintosh may require up to 32 MB of memory, depending on your browser’s memory needs.
Persistent shared object names including the path information are limited to 260 characters maximum.
The server may take up to two minutes to shut down, depending upon operations performed during the shutdown process. When net stop is used from the command line, the command may time out before the services are fully stopped. Use the Services control panel to start and stop FlashCom services.
Before removing Flash Communication Server MX, it is recommended that you stop both FlashCom and FlashComAdmin services using the services control panel.

The Developing Applications with Flash Communication Server manual recommends using prototypes when creating objects, so that all object functions and properties can be shared across all instances of the object. For performance reasons, the use of prototyping is not supported for two methods of the SharedObject object in server-side ActionScript--SharedObject.onSync and handlers associated with SharedObject.send. In server-side ActionScript, these methods must be associated with a specific instance of the object.

The FlashCom service may fail to start if the configuration files contain invalid XML. Make configuration changes using the administration API's or through the Administration Console. It is advisable to make backup copies of your configuration files before making any changes to them.

There is an error in line 84 of the chat.asc file installed in the server's scriptlib/components directory.

Incorrect :
this.history.unshift();

Correct:
this.history.shift();"

Reporting a bug to the Macromedia Flash Communication Server MX team
Found a bug? Please send the detailed bug information via the online Macromedia Software Feature Request and Bug Report form.

Note: Due to the high volume of e-mail we receive, we are unable to respond to every request.

Thank you for using Macromedia Flash Communication Server MX, and for taking the time to send us your feedback!