This was suggested by MM--but only after it had been 5 weeks, and I
was concerned about how long it was taking, so the case was sent to
researching.
A few weeks later they suggested it, along with the reinstall..
As soon as I found it was the Ivory, I emailed MM, and Synthogy---
Thank you David--
Bob Morabito
On Feb 8, 2008, at 5:02 AM, dhbailey wrote:
Congratulations on resolving your issue, and thank you for sharing
it with us. That's not a component that the Windows version
appears to have, which might explain why that situation appears to
have been only a
Just curious, while reading this thread I get the impression that OSX
doesn't have a feature for manually disabling drivers. Is that really true?
Best regards,
Jari Williamsson
___
Finale mailing list
Finale@shsu.edu
Bob Morabito wrote:
just a followup--
Before removing and reinstalling Finale, I removed each item one by one
from he Components folder-
the problem was with the Ivory component--
Synthogy (BTW--EXCELLENT tech support!) advised me to download the
update-- IvoryAU-Update-1_64_00-b3.dmg--I
Jari Williamsson / 08.2.8 / 4:13 AM wrote:
Just curious, while reading this thread I get the impression that OSX
doesn't have a feature for manually disabling drivers. Is that really true?
Correct. Hardware driver is a kernel extension. You need to unload it
at the kernel level. Now you
just a followup--
Before removing and reinstalling Finale, I removed each item one by
one from he Components folder-
the problem was with the Ivory component--
Synthogy (BTW--EXCELLENT tech support!) advised me to download the
update-- IvoryAU-Update-1_64_00-b3.dmg--I had version-v1.63.12
Bob Morabito / 08.2.7 / 7:25 PM wrote:
the problem was with the Ivory component--
Then your problem wasn't the same as the infamous HAL crash :-)
Many of MOTU PCI-424 and M-Audio FW I/O users have been experience
Finale 2008+ crash on splash, which log shows the crash at hardware
abstract layer
Hi Hiro--
i dont see it--i did post a small part of the log when I originally
posted it here--
I forwarded the entire crash log to you--
Peace, Bob Morabito
On Feb 7, 2008, at 11:04 PM, A-NO-NE Music wrote:
Bob Morabito / 08.2.7 / 7:25 PM wrote:
the problem was with the Ivory
I started this thread and the only way I was able to get finale 2008
back was to open the extensions folder in the system folder and
remove the MOTU audio driver. of course I now have to re-install the
driver. (you can't just drag it back into the folder like we did back
in the day).
jk
Bob Morabito / 08.2.7 / 11:52 PM wrote:
I forwarded the entire crash log to you--
Got it. This is a different crash from the infamous one. It is
crashing within Finale threads, and it doesn't suggest AU related to my
limited eyes. You did a good job going after AU to remedy your problem :-)
On 31 Jan 2008 at 14:11, Eric Dannewitz wrote:
On 1/31/08, A-NO-NE Music [EMAIL PROTECTED] wrote:
Are you sure companies recommending repair permission isn't pre-Tiger?
Nope. Not pre-Tiger at all.
Lots of vendors give stupid advice. On the Windows side of thing, the
usual (stupid) advice is
Thanks for thesoap box? What exactly does this contribute?
I said that the advice I got from M-Audio worked. How is that stupid?
On 2/3/08, David W. Fenton [EMAIL PROTECTED] wrote:
On 31 Jan 2008 at 14:11, Eric Dannewitz wrote:
On 1/31/08, A-NO-NE Music [EMAIL PROTECTED] wrote:
Are
does anyone have any ideas about this. I'm on a G5 w/10.4.11 and have
been using 2008 for months. nothing has been installed or changed.
the program quits as the splash screen is done initializing midi and
long enough to re-establish preferences. by the way I have removed
preferences and
Hmm. Check disk permissions? Have any sudden computer shutdowns (like power
outage)? You might want to boot into the OS X shell (boot while holding down
the Apple and the S key) and run the thing it suggests in the startup
screen.
On 1/31/08, jerry kalaf [EMAIL PROTECTED] wrote:
does anyone
Eric Dannewitz / 08.1.31 / 3:55 PM wrote:
Hmm. Check disk permissions?
Y'know, OSX permission issue is kinda things in the past now. Tiger
remedied a log of that issue, and the only chance you screw up
permission badly is when you install legacy software.
--
- Hiro
Hiroaki Honshuku,
Funny, cause a lot of companies recommend doing this. In fact, M-Audio
had be do this with some driver issues I had in 10.4.11, and it
cleared up the problem.
On 1/31/08, A-NO-NE Music [EMAIL PROTECTED] wrote:
Eric Dannewitz / 08.1.31 / 3:55 PM wrote:
Hmm. Check disk permissions?
Y'know, OSX
Nope. Not pre-Tiger at all.
They also recommended, if the Disk Utility did not clear up the
problem, downloading the 10.4.11 combo update and to reinstall that.
Regardless, DiskUtility does find little things wrong, and it's not a
bad idea to run it if you start having issues. It is also a good
Eric Dannewitz / 08.1.31 / 4:41 PM wrote:
Funny, cause a lot of companies recommend doing this. In fact, M-Audio
had be do this with some driver issues I had in 10.4.11, and it
cleared up the problem.
Well, this is how it goes.
If the vender used Apple installer, it will leave a Receipt package,
On Jan 31, 2008, at 12:18 PM, jerry kalaf wrote:
does anyone have any ideas about this. I'm on a G5 w/10.4.11 and
have been using 2008 for months. nothing has been installed or
changed. the program quits as the splash screen is done
initializing midi and long enough to re-establish
I cant get F2008a either to work..the case has been with support now
for a little over 6 weeks-Ive sent crash logs, screen shots, etc
(tho on a very few days it DID work, using the same files..never
could figure out why..)
they said it has to do with MOTU midi interfaces, and drivers..I
Eric Dannewitz / 08.1.31 / 5:11 PM wrote:
They also recommended, if the Disk Utility did not clear up the
problem, downloading the 10.4.11 combo update and to reinstall that.
That's a two different issues. You don't want to apply OS update with
Software Update because it isn't complete. You
On Jan 31, 2008, at 4:04 PM, Bob Morabito wrote:
This morning they advised me to totally uninstall it, and reinstall..
MM tech support told me that Finale did not have an uninstaller.
Did they give you any information about how to do the uninstall?
Dick H
This is what they sent me--
Crash on Midi Import [Case: 071213-000372]
Discussion Thread
Response (Scott H.)
01/30/2008 07:49 AM
Dear Robert,
I have not been able to reproduce the issue right now. I am still
trying many things to see what might be happening. Have you tried
removing
23 matches
Mail list logo
