Rhapsody three Font menu error

[Stuart]

I haven't used Rhapsody 3 for quite a while and I now have a need to use
it.

When I try to run it it comes up with an error "Font menu has active
tasks" and dies.

This is with RO4.39 on a Kinetic, from a clean start.

Help!!

[Jean-Michel]

Post by Stuart
I haven't used Rhapsody 3 for quite a while and I now have a need to use
it.
When I try to run it it comes up with an error "Font menu has active
tasks" and dies.
This is with RO4.39 on a Kinetic, from a clean start.
Help!!

Hope you haven't lost the PMS fonts...

[Stuart]

Post by Jean-Michel

Post by Stuart
I haven't used Rhapsody 3 for quite a while and I now have a need to use
it.
When I try to run it it comes up with an error "Font menu has active
tasks" and dies.
This is with RO4.39 on a Kinetic, from a clean start.
Help!!

Hope you haven't lost the PMS fonts...

Can look but it was all working when I last used it.

Just to be clear the problem is R3 on my old Kinetic.

R4 on my ARMX6 works fine thanks to you.

I've just got R3 running via Aemulor on the ARMX6 and I finally figured
out how to get sound out my ARMX6. It seems it was set to the audio jack
and my monitor was looking for audio on HDMI.

[Nick Roberts]

Post by Stuart
I haven't used Rhapsody 3 for quite a while and I now have a need to
use it.
When I try to run it it comes up with an error "Font menu has active
tasks" and dies.
This is with RO4.39 on a Kinetic, from a clean start.

At one stage, there was an issue with 2 quite different RMs both being
called FontMenu - one was the toolbox module, and the other was a third
party (Joris Roling). Rhapsody was one of the programs that was
affected, but I don't know which version of Rhapsody (if any) fixed it.

It's worthwhile checking to see if your version of Rhapsody is trying
to RMEnsure a local module called FontMenu rather than referencing the
location of the toolbox. If so, this may well be the issue. There's a
way round it, but the instructions are quite complex and there's no
point in posting it until it's been confirmed that this is the problem.

[Stuart]

Post by Nick Roberts

Post by Stuart
I haven't used Rhapsody 3 for quite a while and I now have a need to
use it.
When I try to run it it comes up with an error "Font menu has active
tasks" and dies.
This is with RO4.39 on a Kinetic, from a clean start.

At one stage, there was an issue with 2 quite different RMs both being
called FontMenu - one was the toolbox module, and the other was a third
party (Joris Roling). Rhapsody was one of the programs that was
affected, but I don't know which version of Rhapsody (if any) fixed it.
It's worthwhile checking to see if your version of Rhapsody is trying
to RMEnsure a local module called FontMenu rather than referencing the
location of the toolbox. If so, this may well be the issue. There's a
way round it, but the instructions are quite complex and there's no
point in posting it until it's been confirmed that this is the problem.

Thanks, I'll check tonight when I get back in from work but the puzzle is
that it used to work fine. I did what I needed to do on the ARMX6 with
Aemulor but I would still like to get it sorted

[Jean-Michel]

Post by Stuart

Post by Nick Roberts

Post by Stuart
I haven't used Rhapsody 3 for quite a while and I now have a need to
use it.
When I try to run it it comes up with an error "Font menu has active
tasks" and dies.
This is with RO4.39 on a Kinetic, from a clean start.

At one stage, there was an issue with 2 quite different RMs both being
called FontMenu - one was the toolbox module, and the other was a third
party (Joris Roling). Rhapsody was one of the programs that was
affected, but I don't know which version of Rhapsody (if any) fixed it.
It's worthwhile checking to see if your version of Rhapsody is trying
to RMEnsure a local module called FontMenu rather than referencing the
location of the toolbox. If so, this may well be the issue. There's a
way round it, but the instructions are quite complex and there's no
point in posting it until it's been confirmed that this is the problem.

Thanks, I'll check tonight when I get back in from work but the puzzle is
that it used to work fine. I did what I needed to do on the ARMX6 with
Aemulor but I would still like to get it sorted

For information, with !Rhapsody4 you can import Rhapsody3 and Rhapsody2
files using !R4convert in Support directory. I use it to convert Maestro
files.

Nice music.

[Stuart]

Post by Jean-Michel
For information, with !Rhapsody4 you can import Rhapsody3 and Rhapsody2
files using !R4convert in Support directory. I use it to convert Maestro
files.

Yes. When I got R4, I used to convert files from R3 to R4 format for
printing, though I still often found it necessary to import into Draw-plus
to tidy scores up to my satisfaction.

[Nick Roberts]

Post by Stuart

Post by Nick Roberts

Post by Stuart
I haven't used Rhapsody 3 for quite a while and I now have a need to
use it.
When I try to run it it comes up with an error "Font menu has active
tasks" and dies.
This is with RO4.39 on a Kinetic, from a clean start.

At one stage, there was an issue with 2 quite different RMs both
being called FontMenu - one was the toolbox module, and the other
was a third party (Joris Roling). Rhapsody was one of the programs
that was affected, but I don't know which version of Rhapsody (if
any) fixed it.
It's worthwhile checking to see if your version of Rhapsody is
trying to RMEnsure a local module called FontMenu rather than
referencing the location of the toolbox. If so, this may well be
the issue. There's a way round it, but the instructions are quite
complex and there's no point in posting it until it's been
confirmed that this is the problem.

Thanks, I'll check tonight when I get back in from work but the
puzzle is that it used to work fine. I did what I needed to do on the
ARMX6 with Aemulor but I would still like to get it sorted

Whether it will work or not is dependent on whether another app has
RMEnsure'd (the toolbox version of) FontMenu before Rhapsody 3 tries.

This could be as minor as a toolbox app being added to the "Look At"
path at boot time.