![]() |
||
|
||
|
|||||||
| Questions or problems Have a question or problem about something you can't find in the Help/Users Guide? Ask it here! |
![]() |
|
|
Thread Tools | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Hi, jss, Reinhold:
I'm trying to think back and recall similar instances and I think I recall seeing the exclamation point warning when Composer had been terminated abnormally and was still running in the background. The cure was to use the Task Manager to get rid of the stalled instance of Composer. So, jss may have had such an instance a couple of times. David |
|
#2
|
|||
|
|||
|
Hi All,
I think you have id'd the problem David. Thanks. I remember now - NC took a long time to start up (due to machine load on other software, sound libs etc). I think I may have clicked again (in error) to start it again thinking I had not started it already. Maybe worth asking whether >1 copy running has any purpose and if not, arrange for it to check for such a situation? regards -jss |
|
#3
|
||||
|
||||
|
Hi guys,
Composer 3 does check for multiple instances and "kills" any lingering instances from a previous opening before opening up a new instance. That said, there may be "special" circumstances that trip up that safeguard. If you're able to re-create the situation, please do let us know. ttfn, Sherry
__________________
Music is to the soul like water is to green growing things. |
![]() |
| Bookmarks |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Midi keyboard and NC 3 - latency? | AB1022 | Questions or problems | 1 | 06-26-2015 06:45 PM |
| NC 2.6 aborts if Exit after loading a Template file | jss | Questions or problems | 18 | 12-13-2010 12:16 AM |
| Lost NC Icons | kombrig | Questions or problems | 2 | 07-30-2009 12:13 AM |