Glasgow...

Apple introduced a defect in its FW packet delivery with Leopard. It's been acknowledged by Apple and is logged as a bug to be fixed. If you need proof, run Tiger, the bug isn't there. The defect affects software that uses large packet bursts like Avid to deliver large data streams.

Avid did consider writing a workaround within its software but any patch they conceived would be broken again when Apple fixes their code and Avid would be right back at square one with a broken application on Apple's OS. The decision was made to wait until Apple fixed their bug.

We're all upset about the fact that some of Avid's hardware will not work on Leopard but it has always been thus fro those of us who prefer the MAc platform. Unfortuately the history with Apple has been on of indiference to anyone who is writing software outside of cupertino. From what I hear though this may be in the process of changing. So far, I'm not seeing it.

glasgoweditor:

Todd Sanderson:

You're not listening.  It's not Avid's bug... it's Apple's.  Given that 'FACT'... what do you propose Avid does about it? 

The Mojo is made by Avid, Avid should find a workaround... I'm not listening.

Todd Sanderson:

Also... refrain from name calling, however minor... it's not the point of this forum.

Huh? Explain?

If you can't be bothered to listen, then why should I bother to reply.  You clearly want to vent, and this is not the place for that.  It's a "support" forum.  Call Avid to vent... Marianna is the person to contact.

BLKDOG:

 Glasgow...

Apple introduced a defect in its FW packet delivery with Leopard. It's been acknowledged by Apple and is logged as a bug to be fixed. If you need proof, run Tiger, the bug isn't there. The defect affects software that uses large packet bursts like Avid to deliver large data streams.

Avid did consider writing a workaround within its software but any patch they conceived would be broken again when Apple fixes their code and Avid would be right back at square one with a broken application on Apple's OS. The decision was made to wait until Apple fixed their bug.

We're all upset about the fact that some of Avid's hardware will not work on Leopard but it has always been thus fro those of us who prefer the MAc platform. Unfortuately the history with Apple has been on of indiference to anyone who is writing software outside of cupertino. From what I hear though this may be in the process of changing. So far, I'm not seeing it.

raspago:

Is there anything I should know about setting Avid to run on the Mac Pro any tips or trick? anything to improve performace, etc... ? anything to watch out for ?

.- You can't use any DNA hardware if you use Leopard. Since you are buying a new Macpro, you will be using leopard.

I have now a brand new Macpro-Leopard at work and probably is just me, but I'm having a lot of lock ups and freezes.

For example, the only way I can close Avid is using "force quit".

It quits unexpectly like five times a day (without saving)

I have a new Macpro with 6 GB Ram, Nvidia 8800GT, fresh Leopard install and MC 3.0.

.- I'm having the same problems when I disconnect the DNA.

What would it be?

I just took a SATA drive from another Mac of mine with Tiger installed on it and installed it into my new Mac Pro.  It gave me both a 10.5 and 10.4 bootable drive.

The only precaution I took was running Disk Warrior on the drive before I transfered and it was from a working G5 that already had Avid installed.

The target drive method works well too if you have a laptop or another computer to hook your Mac Pro to.  This method has worked well for a couple of other friends of mine. 

It is worth the trouble because the new Mac Pros are wicked fast on either OS.

Sorry I'm so late replying, I've been out of town at the funeral of a relative...  Here's the procedure.

HOW TO MODIFY A MAC OS X 10.4 INSTALL DISK TO DOWNGRADE THE OPERATING SYSTEM ON A SYSTEM SHIPPED WITH 10.5

1. Use Disk Utility to create a read/write disk image of the OS X 10.4 Tiger Install DVD

2. Mount the disk image and locate the OSInstall.dist file. Open the following folders: System/Installation/Packages. Inside the Packages folder, control-click on the OSInstall.mpkg file and choose “Show Contents.” A new folder will open with several files. Control-click on the file OSInstall.dist and choose “Open With Other… and navigate to Applications/Text Edit.

3. Once you have the OSInstall.dist open in the text editor, replace all instances of ‘return false’ with ‘return true’ Choose “Save As” to save a copy of the newly modified file to the desktop. Be sure to add the extension .dist to the file and do not add .txt A dialog box will pop up asking you to confirm the .dist extension.

4. Drag the new file into the same folder that it came from – you can not save the file directly to the folder. (System/Installation/Packages/OSInstall.mpkg/OSInstall.dist)

5. Use “Disk Utility” to burn the image back to a DVD. The file size (5.7 GB) requires that you must use a Dual-Layer DVD to burn the new disk image.

6. Boot the computer with the new installation disk in the DVD drive while holding down the “C” key and BINGO, you can now install an older OS on a new Mac Pro computer!

glasgoweditor:

So the mojo is not compatiable with the new revision of the software ? The Mojo is made by Avid, Avid should find a workaround... I'm not listening - you haven't explained the problem apart from saying its at Apples door ? What exactly is the problem then ? Many, Many, Many companies re-write and issue patches when Microsoft re-write XP, Avid included ! How many times were we told what securtiy patches to use and not use.

Microsoft release a SP each 12 to 24 month. Mostly they are accomulated hotfixed but with some new features. There take some time to fix for the software developers.

During the last four years we have use Avid, I can only remember one hotfix/patch which break Avid on windows. If You read Avids documentations, You can confirm there is few problems with Microsoft updates.

This is not surprising, as the market leader, Microsoft can not afford the luxury to break to much backward compability because to many businesses and business processes are depending on this backward compability (Everything from automatic cash machines and pulp processing mills to broadcast stations depends on working Windows systems.) This is also the reason You still can buy a new computer with Windows XP, two years after the release of Windows Vista. A new computer must work with non-Vista software.

You know, in real business, the lifetime of software and the update cycle is much longer than the 12 to 24 month the software industry want. Lots of systems in production is not upgrade during the last five to ten years. It is not important for software companies who works against business to support the latest and brigthest hardware. Most business prefere stability and reability with existing hardware. This is also true in this business, surprisingly. There are still lots of Meriden systems outthere working full time.