Dick Hauser / 07.9.22 / 0:32 PM wrote:
Yes. I've loaded a midi file into quicktime and it plays just fine.
Exported that to the desktop as midi and then dragged to DP5 which
played without a problem (after changing output for midi to my Emu
and DMP.
Seems you can isolate the problem to
Dick Hauser / 07.9.21 / 0:48 PM wrote:
I offered up the crash log but the tech didn't want it. My initial
post included the first bit of it but it's so long, I didn't include
it all. I'll send it to you off list.
I received it. I am not a programmer but here is my guesses.
Your HAL
Forgot to ask. Have you tried removing Finale pref file?
--
- Hiro
Hiroaki Honshuku, A-NO-NE Music, Boston, MA
http://a-no-ne.com http://anonemusic.com
___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale
A-NO-NE Music wrote:
[snip] If app is crashing and tech support doesn't want crash log is simply
wrong to me.
But having to decipher a crash log would get in the way of their sending
out the practically automatic We can't reproduce that here. replies.
And it might actually involve doing
A-NO-NE Music wrote:
Dick Hauser / 07.9.21 / 0:48 PM wrote:
I offered up the crash log but the tech didn't want it. My initial
post included the first bit of it but it's so long, I didn't include
it all. I'll send it to you off list.
I received it. I am not a programmer but here is my
On Sep 21, 2007, at 11:01 PM, A-NO-NE Music wrote:
Dick Hauser / 07.9.21 / 0:48 PM wrote:
I offered up the crash log but the tech didn't want it. My initial
post included the first bit of it but it's so long, I didn't include
it all. I'll send it to you off list.
I received it. I am not
Dick Hauser / 07.9.20 / 1:17 AM wrote:
We looked at the startup screen and noted that the crash occured when
the message initializing midi came up (after the initializing Core
Midi) and so started to look at possibilities that something there
was amiss. We moved the Plug-in components out
On Sep 21, 2007, at 8:32 AM, A-NO-NE Music wrote:
They didn't ask you for the crash log?
Why do you not post the crashed thread here as I suggested.
I missed that request, Hiro.
I offered up the crash log but the tech didn't want it. My initial
post included the first bit of it but it's
Dick Hauser / 07.9.19 / 9:55 PM wrote:
Of course, it follows with 25 or 30 threads of similar looking stuff,
all of which means nothing to me.
But that's where the clue is. The address error doesn't mean nothing in
crash log. Scroll down, and find where it sez:
Thread n Crashed:
Copy
On Sep 20, 2007, at 1:13 AM, Dick Hauser wrote:
On Sep 19, 2007, at 7:52 PM, Christopher Smith wrote:
The only time I ever had a bad address error is when I had a bad
RAM chip.
MemTest is a shareware app that does a great job of detecting bad
RAM. I highly recommend it.
Barring that,
On Sep 20, 2007, at 8:49 PM, Christopher Smith wrote:
On Sep 20, 2007, at 1:13 AM, Dick Hauser wrote:
On Sep 19, 2007, at 7:52 PM, Christopher Smith wrote:
The only time I ever had a bad address error is when I had a bad
RAM chip.
MemTest is a shareware app that does a great job of
This is a surprise, since it was working yesterday. Well, not
entirely true, I guess, since I did get this message once in a while
but a restart of the application always worked.
I'm on FMac2008.r2
OSX 10.4.10
Dual 2 GHz Power PC G5
4GB Ram
The first part of the error report looks like
The only time I ever had a bad address error is when I had a bad RAM
chip.
MemTest is a shareware app that does a great job of detecting bad
RAM. I highly recommend it.
Barring that, am I right in thinking that you have 2 X 2 GB chips?
Try removing one and see if it crashes. Then try the
On Sep 19, 2007, at 7:52 PM, Christopher Smith wrote:
The only time I ever had a bad address error is when I had a bad
RAM chip.
MemTest is a shareware app that does a great job of detecting bad
RAM. I highly recommend it.
Barring that, am I right in thinking that you have 2 X 2 GB
14 matches
Mail list logo
