From: Jordan Bigel <[EMAIL PROTECTED]>
Subject: Re: sdk+jmf
Hi again Kevin,
First, there have been some problems experienced whereby everything was
set up properly, but a "NoPlayerFoundException" was still generated. We have
not yet nailed down what is causing this, but it ONLY happens with JDK
1.2.x - if
you would just try a 1.1.x version of the JVM as a test, I would appreciate
hearing
the results.
>The client (RealPlayer) has "G2 JMF", but do I need to download
>the whole update or only "G2 JMF" component? Also in our environment
You only need the G2 JMF component. Basically this upgrade package includes
2 DLLs (native method implementations) used by JMF. They are not shipped with
the SDK because they are platform specific. The DLLs are called rjco3260 and
rjjn3260 - both belong in the \winnt\system32 or \windows\system dir (and
will be
placed there automatically by the upgrade installer). If the installer
detects
Netscape it will also copy the rjjn3260 library to \netscape\java\bin and
it will
make a copy of rjmf.jar and put it in \netscape\java\classes. You might check
to make sure these files are all in place (after you download the G2 JMF
component
from the Upgrade server).
We have not yet tried G2 JMF on top of the JMF 2.0 base classes. We are
assured
by Javasoft (and our review of the 2.0 spec) that this should not be a
problem. However,
you should try it with the JMF 1.x jar just to see if that is the problem.
Jordan.
PS. To report bugs in JMF or other Real products, go to
http://service.real.com.
At 02:34 PM 8/12/99 -0700, RealForum wrote:
>From: Kevin Liu <[EMAIL PROTECTED]>
>Subject: Re: sdk+jmf
>
>Hi Jordan,
>Thank you very much for your message.
>I tried all these but still have the same error message. I typed
> java com.real.util.RJMFConfig
>
>and it seems working by giving me this
> RMA JMF Config V1.0
> RMA JMF already configured!
>
>The client (RealPlayer) has "G2 JMF", but do I need to download
>the whole update or only "G2 JMF" component? Also in our environment
>we have JDK1.2.2 and JMF2.0. Do you think this might cause the
>problem.
>Thanks, -- Kevin
