📄 ndsformms1.1releasenotes.htm
字号:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>
Release Notes for Nokia Developer's Suite for MMS v1.1
</title>
<meta http-equiv="content-type" content="text/html; charset=us-ascii">
</head>
<body>
<hr/>
<h1>
Nokia Developer's Suite for MMS v1.1
</h1>
<h3>
Release Notes
</h3>
<p>
Copyright (c) 2003 Nokia Corporation<br/>
Release Date: 31 July 2003
<hr/> </p>
<p>
For product support and the latest
release notes, contact Nokia at <a href="http://forum.nokia.com">www.forum.nokia.com</a>.</p>
<h3><u>Product Description</u></h3>
The Nokia Developer's Suite for MMS v1.1 ('NDSforMMS') enables the creation
of MMS messages from SMIL files and related media files. The resulting MMS
messages can be deployed to various MMS-capable device SDKs.
NDSforMMS also works as a plug-in to Adobe GoLive 6.0 and Adobe GoLive CS..
<p>
Note: Adobe GoLive should be installed first, in order for NDSforMMS to
function as a plug-in to Adobe GoLive. <hr/>
</p>
<h3><u>Minimum System Requirements</u></h3>
<p>
<b>Platforms:</b><br/>
Windows 2000 Professional (SP2) and Windows XP Professional (SP1) <br/>Java Run Time Environment 1.4.1_02<br/>
<br/>
<b>Hardware:</b><br/> 400 Mhz Pentium PC<br/>
96 MB RAM<br/>
20 MB Hard Disk Space<br/>
64 K colors
<hr/>
</p>
<h3><u>New Features</u></h3>
<ul>
<li>
Version 1.1 of NDSforMMS now also works as a plug-in to Adobe
GoLive CS. <br/></li>
<li>The default SDK supporting SMIL presentation that is installed as part of the NDSforMMS package
is Series 60 Content Authoring SDK
v1.2, Nokia Edition. <br/></li>
<li>Various MMS-capable Content Authoring SDKs that work
with NDSforMMS like Nokia 7210, 3510i, 5100, etc. are available from <a href="http://forum.nokia.com">www.forum.nokia.com</a>.</li>
</ul>
<h3><u>Defects Fixed Since v1.0</u></h3>
<table border="1">
<tr>
<td width="120" valign="top">
<p>
<b>Defect ID</b>
</p>
</td>
<td width="512">
<p>
<b>Defect Description</b>
</p>
</td>
</tr>
<tr>
<td width="120" valign="top">
<p>
<font color="#000000">JCHI-5KQW32</font>
</p>
</td>
<td width="512">
<b>Fixed:</b> Uninstall any JRE versions 1.3.0 or older from your system before
installing the NDSforMMS v1.0 package. Otherwise the Update Manager
component of this package will not run properly.<br/>
</td>
</tr>
</table>
<hr/>
<h3>
<u>Known Issues in v1.1</u>
</h3>
<table border="1">
<tr>
<td width="120" valign="top">
<p>
<b>Defect ID</b>
</p>
</td>
<td width="512">
<p>
<b>Defect Description</b>
</p>
</td>
</tr>
<tr>
<td width="120" valign="top">
<font color="#000000">JCHI-5JMMNN</font>
</td>
<td width="512">
If NDSforMMS is installed to the C:\ (root) directory, and it is
started from any directory (see example below) other than C:\ (root),
then NDSforMMS fails to connect to the installed Phone SDKs.
<p>Example: C:\sample-files> ..\ndsmms.exe</p>
<p><b>Workaround:</b> Start ndsmms.exe exactly from the directory it
is installed in.
</td>
</tr>
<tr>
<td width="120" valign="top">
<font color="#000000">TYU-5JMKRG</font>
</td>
<td width="512">
When NDSforMMS is started from Adobe GoLive, sometimes it does not display
the selected SMIL file name.
<p><b>Workaround:</b> MMS message can still be generated in NDSforMMS
for that SMIL file once the From/To information is provided.
</td>
</tr>
<tr>
<td width="120" valign="top">
<font color="#000000">-5N8F6R</font>
</td>
<td width="512">
<font color="#000000">If you open an MMS message that uses a different
encoding in the MMS Subject header, then NDSforMMS gives "Invalid
MMS Message: no media files" error.</font>
<p><b>Workaround:</b> No workaround. NDSforMMS does not support
encoded Subject headers in MMS messages.
</td>
</tr>
<tr>
<td width="120" valign="top">
TYU-5MF23N
</td>
<td width="512">
NDSforMMS does not support SMIL files which have links to parts using
the following
schema:
<img src = "cid:abc123"/><p><b>Workaround:</b> Use a filename referring to the part, instead
of the cid schema. Also note that when creating MMS messages, the media files referenced
in the SMIL file are expected to be in the same directory as the SMIL
file.
</td>
</tr>
<tr>
<td width="120" valign="top">
<p>
<font color="#000000">EHEN-5PHSTN</font>
</p>
</td>
<td width="512">
<p>Closing an SDK (particularly Series 60 CA SDK v1.0.6) from the SDK
window may not remove the corresponding instance line in the Message
Recipients panel of NDSforMMS. This will disable the user from
starting another instance of the SDK.
</p>
<p>
<b>Workaround:</b> Click the Close button on the instance line on
the Message Recipients panel of NDSforMMS before attempting to start
another instance of the SDK.
</p>
</td>
</tr>
<tr>
<td width="120" valign="top">
<p>
<font color="#000000">EHEN-5PNQ4U</font>
</p>
</td>
<td width="512">
<p>When an MMS message is sent to Series 60 Content Authoring SDK 1.2,
sometimes it shows an error "Program Closed: MMS Inbox".
</p>
<p>
<b>Workaround:</b> Click the Send button in NDSforMMS again so that
the MMS message is sent to the SDK again.
</p>
</td>
</tr>
<tr>
<td width="120" valign="top">
EHEN-5PGRP4
</td>
<td width="512">
When you close an instance of 3510i SDK, sometimes it may also close a
running instance of the 5100 SDK and vice-versa. This occurs if the
two SDKs are started immediately right after each other.
<p><b>Workaround:</b> Wait for one instance of one SDK to start
completely before clicking the Start button on the other SDK.
</td>
</tr>
<tr>
<td width="120" valign="top">
<font color="#000000">JCHI-5J3TLC</font>
</td>
<td width="512">
Uninstallation of NDSforMMS, while running NDSforMMS, does not warn
the User to exit NDSforMMS first. Many files related to product are
left behind on such uninstallation.
<p><b>Workaround:</b> Stop any running instances of NDSforMMS before
attempting to uninstall the product.
</td>
</tr>
<tr>
<td width="120" valign="top">
</td>
<td width="512">
If you are using the MMSC EAIF emulator and if the path for any
version of S60 CA SDK
is not correctly configured in the <font face="Courier">eaifem.properties</font> file
of the MMSC EAIF emulator, then the
MMSC EAIF emulator may not function correctly.
<p><b>Workaround:</b> Configure the path of S60 CA SDK correctly in the <font face="Courier">eaifem.properties</font>
file of the MMSC EAIF emulator.</p>
</td>
</tr>
</table>
<hr/>
<p ><small>Document published 31 July 2003</small></p>
</body>
</html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -