Como vacio el cache en mi mac pro

hola necesito saber como se vacia el cache en mi mac

Con Safari abierto, presione las teclas Comando + Opción + E en su teclado después salga y reinicie Safari.

Similar Messages

Is a hard drive of 32 Mo/Mb Cache compatible for a Mac pro ( before 2008)

Bonjour,
I have bought a hard drive Samsung/750 GB Sata (3,5 séries). 7200 tr.minutes. 32 mo Cache. My mac pro is a old one
(before 2008). Is the 32 Mo/Mb cache compatible for my mac ? In this one i have still a Samsung hard drive of 500Gb but its cache is a 16 Mo/Mb one;
Tank's véry much.

Doesn't have any effect on compatibility.
http://eshop.macsales.com/shop/hard-drives/sata/mac-pro
A couple favorites of mine:
http://eshop.macsales.com/item/Western%20Digital/WD6400AAKS/
http://eshop.macsales.com/item/Western%20Digital/WD3000HLFS/
http://eshop.macsales.com/item/Western%20Digital/WD1001FALS/
http://www.tomshardware.com/reviews/hitachi-western-digital-terabyte,2017-13.htm l
http://www.barefeats.com/harper14.html
http://www.barefeats.com/harper13.html
They work just fine, including in pre-Mac Pro era PowerMac G5s.

New Mac Pro internal PCIe flash disk Ae cache - partition?

I have ordered a new Mac Pro, 8-core, D700s, 64 GB RAM, and the 1TB PCIe internal flash boot drive. I would like information directly from Adobe on how to best utilize the internal flash drive as my cache drive for Ae, Pr, Au and Ps.. With 1TB, I figure I can allocate half towards being my dedicated cache for Adobe apps. My question is, is it best to just create a folder on the boot drive to use as my cache, or is it better to partition the drive into two halves-one half for the boot and documents, and the second partition as the dedicated cache drive? I'm thinking it might be a good idea to partition so that the boot half of the drive is protected from wear from the heavy writes incurred by the caches? Any other advice specific to optimizing Adobe apps for the nmp would be appreciated too. Thanks.

Wear leveling is done at the drive level, not the partition level, so partitioning won't help with that issue.
Partitioning has the advantage of making it so that if your cache fills up it won't run your boot disk out of space, which Mac OS still doesn't handle very gracefully.
What I opted to do was to get an external SSD drive for cache. Why? Because caching puts a lot of stress on the drive and it's a lot cheaper to replace a standard SATA SSD drive than it is to replace the built-in Apple-specific SSD.
That was my thinking anyway. We'll all know more after the new MacPros have been out for a year or two.
Bob Currier
Synthetic Aperture

Does the cache matter when choosing hard drive for mac pro?

Hi,
I have been looking at all the specs to see about adding another hard drive to my mac pro. It is the 1st generation 2006 duel. I am getting a bit confused about the specs required! I don't understand cache? I think that mine is 8 cache, but a lot of the drives I am looking at are 16 or more. Is this important, have I got to stick to 8? Also does it matter about which Sata? i.e. 1, 11 or 111? and what does 'low profile' mean? Fitting it seems really easy, but buying the wrong drive seems easy as well!
Thanks for any help,
Adrian.

Desktop drives are nominal 3.5" form factors, about one inch tall. They use a 12 Volt motor to spin the heavy platters around fairly fast.
Notebook rotating drives are mostly 2.5" form factor, now mostly around 9.5mm tall, possibly less. They have only 5 Volts available to spin the motor.
SATA 1, 2, 3 -- 1.5, 3.0 and 6.0 is all specsmanship -- rotating drives cannot source data off the spinning platters faster than a burst of about 150 Mbytes/sec (1.2 Mbits/sec). So that part does not matter except that the 1.5 drives will be older models. Do note pay extra for better SATA speeds.
Rotation speed is very important, because that determines how fast the bits can fly past the read head. 5400 RPM is slower than 7200 RPM. A few 10,000 RPM drives are available, but they are too pricey for most users. I use 10,000 RPM drives in my Server. For Desktop computers, DO pay extra for 7200 over 5400. For notebook computers, a few 7200 RPM drives are available, but they sometimes run HOT.
Green drives, on the other hand, take great liberties with spin rates and sleeping, and are not suitable for production (great for Backups, but then they are not candidates for spares for your main drives). For these reasons, I do not own any Green Drives.
Large-enough cache size means the drive can read an entire track in one revolution, so that if you next ask for blocks near the original block you will not wait the average 4.166 milliseconds for the platter to spin halfway around to pick up new data (it is waiting, pre-fetched in the cache). So do not pay extra above about 8Mbytes, but use larger cache size as a tie breaker between equivalent models.

Would my Mac Pro accept an internal HD with SATA 6Gb/s with 64MB Cache?

I am looking to expand the storage on my Mac Pro and wanted to know if it would accept internal HD with SATA 6.0Gb/s, 7200RPM, 64MB Cache. Also, do they accept 3 T Drives?

I would point out that Apple never updates hardware specs on hard drives.
That was the size available at the time.
Doubt any real testing went into it.
Almost no one buys hard drives from Apple unless:
They are using Apple RAID controller and want to be sure; they use SAS; don't realize that for normal customers even workstations, SATA II/III are fine and there is nothing special, there are not Apple firmware models that you need other than Apple controller support.
When the Mac Pro 2006 came out I think 750GB was the largest, and while other web pages get updated and tech notes reflect new information, that has not happenend to product spec pages. - And there are pages where the specs and hardware/software requirements are even off base, making matters even worse.
Any drive that can fit as is or with an adapter (such as Icy Dock for SSDs) that has SATA interface.
Guess that is too complicated??

Seagate ST8000AS0002 8TB 5900RPM 128MB Cache SATA3 - for Backup Data Only. Are there any compatibility issues with an older 3,1 Apple Mac Pro 8-Core 2.8GHz (4-Core x 2) ?

Finally mass storage drives are being released. The Seagate ST8000AS0002 8.0 TB 5900RPM has just been released in Australia and I was advised to check on any compatibility issues, being that my 3,1 Mac Pro is an old, but working fine machine.
I have read there are possible issues with using HDs greater than 2TB with the MP 3,1 . But checking with OWC, they say the Seagate 4.0 TB Solid State Hybrid Drive is compatible for use with the MP 3,1.
So can the hardware and operating system handle an 8.0 TB of this sort ?

The problem is with formatting the large disk. The Mac can see and use them if formatted for a Mac
Format large disks
That bug appeared in 10.8.4, and has not yet been fixed.
using a Disk Utility from any older Mac OS X, including the 10.6 DVD (if your Mac can boot from it) or any saved Installer DVD or thumb drive will work.
Another work-around is to move that drive to an external enclosure and Erase it there (provided your enclosure is modern enough to deal with drives over 2.2TB.

Como recuperar un Mac Pro robado sin icloud

HOla hoy me robaron mi Mac Pro quisiera saber sí es posible rastrearlo sin necesidad del iCloud?

Ir a www.icloud.com y haga clic en Buscar mi Mac.

Is my mac pro's nVidia 8800gt dead. B&W lines across my screen only

Hi, I run a Mac Pro 2008 oct core system. The specs are as follows:
dual 2.8GHz quad core processors
Snow Leopard with all software updates
16GB RAM DDR2 (Pre-DDR3 mac) (apple certified RAM, so won't break my warranty)
Hard drives are set in two raid arrays, there are four 1.5 TB drives, each set to pairs of raid 0 for 3 TB drives. One raid array is set to time machine the other is my startup disc.
dual DVD RW drives
N-Videa 8800GT graphics card (Shipped with my mac)
using a DVI to HDMI adapter to connect to a 40" Samsung LCD TV as a monitor (has always worked flawlessly)
I have upgraded a lot of the parts myself and have a fair amount of knowledge of how to do my own upgrades. My system today crashed on me after waking from sleep mode and attempting to use the web. Now when I try rebooting it gives me a screen that is even lines of black and white, nothing else. I do get the Apple beep noise like normal so my assumption is it isn't going to be the memory. I have cleaned off, reseated, and tried different slots with my graphics card, and both DVI ports, same effect. I am pretty sure this is the graphics card demanding to be replaced, which I have considdered upgrading anyway in the past. Most of my computer activities involve watching HD quality movies and TV shows and playing games with high graphic requirements at maximum settings, so using a top of the line graphics card is to be expected.
What I am posting here for is just getting a confirmation that other people agree with me that this is the problem so I do not waste my money on a new graphics card. Please let me know opinions, I would like to have my computer running swimmingly in the near future. Thanks in advance, I appreciate any help I can get.
-Jacob

Most people often seem to think that after a system freeze they don't need to repair their boot drive.
Over the years, Disk Warrior stands out as indispensable.
ie, don't rely on the restart alone to repair and fix, and you probably don't want to trust and rely on just Apple First Aid.
Boot from another drive and run Apple First Aid followed by Disk Warrior; keep backups of your system you can boot from. Clone your system with SuperDuper. Clear out system caches.
You don't need to buy Apple RAM and its prices to have certified RAM, Crucial and others are fine. Sometimes even better.
I like a fsst, small, boot drive and keep it just to OS/Apps; everything else, media files, data, whatever, on other drives. Multiple backups and redundancy. TimeMachine doesn't benefit or perform any faster with RAID, I've tried just to see.
I would slice off some space for an emergency boot drive so you can OPTION boot to that and run First Aid and other maintenance.
Then worry about hardware, and maybe run some hardware tests.
And for a good "is it software or hardware" do a clearn install of Apple OS and updates (only) - needs less than 30GB.

Mac Pro has slowed to a crawl - Please Help Me!

Hello,
For some time now my Wireless or Wired Internet connection using my Mac Pro has slowed to almost nothing. For example, This page took 5 mins to load and now Internet use has become unusable.
I feel its my Mac Pro because all other Apple Computer run very fast wirelessly. I have (2) New iMac's (1) Apple TV and (1) Apple iPhone. All stream and surf the Internet blazingly fast.
My Mac Pro is constantly being redirected to other sites (mostly **** related) and a huge amount of Pop ups (even though pop ads are disabled in Safari). All Internet browsers perform the same on my Mac Pro or ANYTHING Internet related including WoW, Software updates or even iTunes Music Down loads.
I really feel that in some way (which is shocking) I am infected with "something" that is making my computer crawl on the Internet. Redirection of websites is just now very aggravating.
I am looking at the (2) Original Disks that came inside the Mac Pro Box. I'm seriously considering wiping my system clean and starting from scratch.
I currently hold NOTHING on my Factory 320GB HD other than programs.
I have installed (2) 1TB drives and created a RAID slice thus creating a single HD icon on my desktop that reads 1.8TB. Thats is where all my Music, Photos, and Movies reside.
My question is....
When I wipe my system will that RAID be broken? Will I lose everything on those 2 drives or will using the restore CD's leave all that information in tact?
Please let me know before I proceed.
Thank you for your time.
John

Your RAID won't be touched. But back it up today if you haven't yet!
I use Firefox for security with noscript and some other filters, but I also hardened the router firewall to manually block services, ports and add rules - both incoming and outgoing.
You might want to look at LittleSnitch or NetBarrier and do some logging.
I've seen/heard where older routers and modems were fine, but not with Mac Pro or with Intel Macs in general and needed to be replaced or firmware updated. Problems with the latest updates for Airport have been seen by some, and worth checking into - on forums, news sites or hit google.
And of course check what processes are getting loaded and run; manually delete caches, history, metadata, even the bookmarks cache.
~/Library/Caches/Metadata
There are issues with fake Flash updates; normal sites (like CNN) suffering from SQL-injection. Best to run with javascript off for now.
Might want to look into ClamXav and other malware protection. But I would switch and see how Firefox and Opera behave. And turn off java, script, and plug-ins while you consider your options and try to find out why.

Mac Pro turns itself on every day at the same time

My Mac Pro suddenly decided to start turning itself on every day at 6:00:12pm local time (12:00:12AM GMT). It turns on at exactly 12 seconds after 6:00pm every day.
I recently upgraded to OSX 10.5 and installed the point update. It did it before the point update and continues to after the point update.
I have had it since April and it has never done this before. It did NOT do this under 10.4.
I have the options in system settings to NOT wake on LAN event and NOT restart after power failure. It is NOT set to automatically turn on but it is set to automatically turn itself off at 1:00am.
These settings have not changed since 10.4 and I have verified them. No other software has recently been installed since the update to 10.5. I did update the Wacom driver to the new Leopard driver. That is all. I have the Wacom tablet unplugged from the computer.
Any ideas?
Here is the console log from yesterday. It pretty much looks the same every day.
Log file:
Nov 18 18:00:12 localhost com.apple.launchctl.System[2]: kern.maxproc: 532 -> 512
Nov 18 18:00:15 localhost com.apple.launchctl.System[2]: launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
Nov 18 18:00:15 localhost com.apple.launchd[1] (org.cups.cupsd): Unknown key: SHAuthorizationRight
Nov 18 18:00:15 localhost com.apple.launchd[1] (org.ntp.ntpd): Unknown key: SHAuthorizationRight
Nov 18 18:00:16 localhost kernel[0]: npvhash=4095
Nov 18 18:00:16 localhost DirectoryService[12]: Launched version 5.0 (v514)
Nov 18 18:00:16 localhost kernel[0]: hi mem tramps at 0xffe00000
Nov 18 18:00:16 localhost kernel[0]: PAE enabled
Nov 18 18:00:16 localhost kextd[11]: 412 cached, 0 uncached personalities to catalog
Nov 18 18:00:16 localhost kernel[0]: 64 bit mode enabled
Nov 18 18:00:16 localhost kernel[0]: Darwin Kernel Version 9.1.0: Wed Oct 31 17:46:22 PDT 2007; root:xnu-1228.0.2~1/RELEASE_I386
Nov 18 18:00:16 localhost kernel[0]: standard timeslicing quantum is 10000 us
Nov 18 18:00:16 localhost kernel[0]: vmpagebootstrap: 973126 free pages and 75450 wired pages
Nov 18 18:00:16 localhost kernel[0]: migtable_maxdispl = 79
Nov 18 18:00:16 localhost kernel[0]: 88 prelinked modules
Nov 18 18:00:16 localhost kernel[0]: AppleACPICPU: ProcessorApicId=0 LocalApicId=0 Enabled
Nov 18 18:00:16 localhost kernel[0]: AppleACPICPU: ProcessorApicId=1 LocalApicId=1 Enabled
Nov 18 18:00:16 localhost kernel[0]: AppleACPICPU: ProcessorApicId=2 LocalApicId=2 Enabled
Nov 18 18:00:16 localhost kernel[0]: AppleACPICPU: ProcessorApicId=3 LocalApicId=3 Enabled
Nov 18 18:00:16 localhost kernel[0]: AppleACPICPU: ProcessorApicId=4 LocalApicId=5 Enabled
Nov 18 18:00:16 localhost kernel[0]: AppleACPICPU: ProcessorApicId=5 LocalApicId=6 Enabled
Nov 18 18:00:16 localhost kernel[0]: AppleACPICPU: ProcessorApicId=6 LocalApicId=7 Enabled
Nov 18 18:00:16 localhost kernel[0]: AppleACPICPU: ProcessorApicId=7 LocalApicId=4 Enabled
Nov 18 18:00:16 localhost kernel[0]: Loading security extension com.apple.security.TMSafetyNet
Nov 18 18:00:16 localhost kernel[0]: calling mpopolicyinit for TMSafetyNet
Nov 18 18:00:16 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)
Nov 18 18:00:16 localhost mDNSResponder mDNSResponder-164 (Nov 4 2007 13:23:04)[16]: starting
Nov 18 18:00:16 localhost kernel[0]: Loading security extension com.apple.nke.applicationfirewall
Nov 18 18:00:16 localhost kernel[0]: Loading security extension com.apple.security.seatbelt
Nov 18 18:00:16 localhost kernel[0]: calling mpopolicyinit for mb
Nov 18 18:00:17 localhost kernel[0]: Seatbelt MACF policy initialized
Nov 18 18:00:17 localhost kernel[0]: Security policy loaded: Seatbelt Policy (mb)
Nov 18 18:00:17 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Nov 18 18:00:17 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Nov 18 18:00:17 localhost kernel[0]: MAC Framework successfully initialized
Nov 18 18:00:17 localhost kernel[0]: using 16384 buffer headers and 4096 cluster IO buffer headers
Nov 18 18:00:17 localhost kernel[0]: devfsmakenode: not ready for devices!
Nov 18 18:00:17 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
Nov 18 18:00:17 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
Nov 18 18:00:17 localhost kernel[0]: mbinit: done
Nov 18 18:00:17 localhost kernel[0]: Security auditing service present
Nov 18 18:00:17 localhost kernel[0]: BSM auditing present
Nov 18 18:00:17 localhost kernel[0]: rooting via boot-uuid from /chosen: A3FDED86-37C7-3DF1-9FCC-6C589DDC1077
Nov 18 18:00:17 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Nov 18 18:00:17 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleAHCI/PRT0 @0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDri ver/ST3500630AS P Media/IOGUIDPartitionScheme/Customer@2
Nov 18 18:00:17 localhost kernel[0]: BSD root: disk0s2, major 14, minor 2
Nov 18 18:00:17 localhost kernel[0]: FireWire (OHCI) TI ID 8025 built-in now active, GUID 0019e3fffe8072a0; max speed s800.
Nov 18 18:00:17 localhost kernel[0]: Jettisoning kernel linker.
Nov 18 18:00:17 localhost kernel[0]: Resetting IOCatalogue.
Nov 18 18:00:17 localhost kernel[0]: Matching service count = 0
Nov 18 18:00:17 localhost kernel[0]: Matching service count = 18
Nov 18 18:00:17: --- last message repeated 4 times ---
Nov 18 18:00:17 localhost kernel[0]: AppleIntel8254XEthernet: Ethernet address 00:19:e3:66:97:7a
Nov 18 18:00:17 localhost kernel[0]: AppleIntel8254XEthernet: Ethernet address 00:19:e3:66:97:7b
Nov 18 18:00:17 localhost kernel[0]: Previous Shutdown Cause: 5
Nov 18 18:00:17 localhost mDNSResponder[16]: Adding registration domain tjasher.members.mac.com.
Nov 18 18:00:17 localhost mDNSResponder[16]: Setting up AutoTunnel address FD14:A58A:53D0:1166:0219:E3FF:FE66:977A
Nov 18 18:00:19 localhost fseventsd[42]: bumping event counter to: 0xfa0a6 (current 0x0) from log file '00000000000f52e0'
Nov 18 18:00:22 localhost kernel[0]: Intel8254x -- Link Down -- 00:19:e3:66:97:7a -- called by enableHardware() --
Nov 18 18:00:26 localhost kernel[0]: -- Auto-Negotiation Advertisement Register (04d) = 0xde1
Nov 18 18:00:25 localhost /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[37]: Login Window Application Started
Nov 18 18:00:26 localhost kernel[0]: -- Auto-Negotiation Link Partner Ability Register (05d) = 0x0
Nov 18 18:00:22 localhost bootlog[48]: BOOT_TIME: 1195430411 0
Nov 18 18:00:26 MacPro kernel[0]: -- Auto-Negotiation Gigabit Advertisement Register (09d) = 0xe00
Nov 18 18:00:26 MacPro kernel[0]: -- Auto-Negotiation Gigabit Link Partner Ability Register (10d) = 0x4000
Nov 18 18:00:26 MacPro kernel[0]: -- PHY Specific Status Register (17d) = 0x8040
Nov 18 18:00:26 MacPro xgridcontrollerd[28]: Error: controller missing password file "/etc/xgrid/controller/client-password"
Nov 18 18:00:26 MacPro com.apple.launchd[1] (com.apple.xgridcontrollerd[28]): Exited with exit code: 2
Nov 18 18:00:27 MacPro kernel[0]: Intel8254x -- Link Up -- 00:19:e3:66:97:7b -- called by interruptOccurred() --
Nov 18 18:00:26 MacPro rpc.statd[33]: statd.notify - no notifications needed
Nov 18 18:00:26 MacPro xgridcontrollerd[28]: Notice: controller failed
Nov 18 18:00:27 MacPro kernel[0]: -- Auto-Negotiation Advertisement Register (04d) = 0xde1
Nov 18 18:00:26 MacPro configd[15]: setting hostname to "MacPro.local"
Nov 18 18:00:27 MacPro kernel[0]: -- Auto-Negotiation Link Partner Ability Register (05d) = 0xcde1
Nov 18 18:00:26 MacPro /usr/sbin/ocspd[64]: starting
Nov 18 18:00:27 MacPro kernel[0]: -- Auto-Negotiation Gigabit Advertisement Register (09d) = 0xe00
Nov 18 18:00:27 MacPro kernel[0]: -- Auto-Negotiation Gigabit Link Partner Ability Register (10d) = 0x7c00
Nov 18 18:00:27 MacPro kernel[0]: -- PHY Specific Status Register (17d) = 0xaf08
Nov 18 18:00:27 MacPro kernel[0]: Intel8254X -- Negotiated Speed: 1 Gb/s, Duplex: Full, Flow Control: Receive Pause Enabled, Transmit Pause Enabled
Nov 18 18:00:27 MacPro kernel[0]: sandbox-exec 28 PARENTAGEEXEC_AND_DROPPROFILE SBF /usr/libexec/xgrid/xgridcontrollerd 13 (seatbelt)
Nov 18 18:00:28 MacPro kextd[11]: writing kernel link data to /var/run/mach.sym
Nov 18 18:00:30 MacPro com.wacom.wacomtablet[90]: TabletDriver[90]: Env RUNWITHLAUNCHD is set to 1
Nov 18 18:00:31 MacPro loginwindow[37]: Login Window Started Security Agent
Nov 18 18:00:31 MacPro Parallels[106]: Loading Hypervisor module...
Nov 18 18:00:32 MacPro com.apple.SystemStarter[31]: kextload: extension /System/Library/Extensions/hypervisor.kext is already loaded
Nov 18 18:00:32 MacPro kernel[0]: [Parallels] Parallels Hypervisor started.
Nov 18 18:00:32 MacPro Parallels[112]: Loading Monitor module...
Nov 18 18:00:32 MacPro com.apple.SystemStarter[31]: kextload: extension /System/Library/Extensions/vmmain.kext is already loaded
Nov 18 18:00:32 MacPro kernel[0]: [Parallels] Parallels VM observer thread started
Nov 18 18:00:32 MacPro Parallels[114]: Loading ConnectUSB module...
Nov 18 18:00:32 MacPro com.apple.SystemStarter[31]: kextload: extension /System/Library/Extensions/ConnectUSB.kext is already loaded
Nov 18 18:00:32 MacPro Parallels[116]: Loading Network module...
Nov 18 18:00:32 MacPro com.apple.SystemStarter[31]: kextload: extension /System/Library/Extensions/Pvsnet.kext is already loaded
Nov 18 18:00:32 MacPro Parallels[118]: Loading Virtual Ethernet module...
Nov 18 18:00:32 MacPro com.apple.SystemStarter[31]: kextload: /Library/StartupItems/Parallels/Pvsvnic.kext loaded successfully
Nov 18 18:00:33 MacPro kernel[0]: comparallels_kextPvsvnic1: Ethernet address 00:1c:42:00:00:01
Nov 18 18:00:33 MacPro kernel[0]: comparallels_kextPvsvnic0: Ethernet address 00:1c:42:00:00:00
Nov 18 18:00:33 MacPro ntpd[25]: bind() fd 28, family 30, port 123, scope 7, addr fe80::21c:42ff:fe00:1, in6is_addrmulticast=0 flags=17 fails: Can't assign requested address
Nov 18 18:00:33 MacPro ntpd[25]: bind() fd 28, family 30, port 123, scope 8, addr fe80::21c:42ff:fe00:0, in6is_addrmulticast=0 flags=17 fails: Can't assign requested address
Nov 18 18:00:33 MacPro Parallels[121]: Staring DHCP/NAT daemon...
Nov 18 18:00:33 MacPro pvsnatd[123]: en3: DHCP/NAT for 10.211.55.2-10.211.55.254 netmask 255.255.255.0
Nov 18 18:00:33 MacPro pvsnatd[123]: en2: DHCP for 10.37.129.2-10.37.129.254 netmask 255.255.255.0
Nov 18 18:00:34 MacPro Parallels[125]: Restarting InternetSharing...
Nov 18 18:00:34 MacPro Parallels[127]: Restaring CiscoVPN...
Nov 18 18:00:34 MacPro com.apple.SystemStarter[31]: /Library/StartupItems/Parallels/Parallels: line 62: /System/Library/StartupItems/CiscoVPN/CiscoVPN: No such file or directory
Nov 18 18:00:34 MacPro Parallels[129]: Initialization complete.

Updates installed by Software Update are "delta" updates - they go from 10.x.y to 10.x.y+1, and are customized for a particular Mac model. It appears that in this case they also patch some files instead of replacing them fully. The "combo" update will update 10.x.anything to the latest 10.x.y, it'll update any Mac model, and in this case it appears they contain full files instead of patches. The delta updater for 10.5.1 is about 39 MB; the combo updater is about 110 MB. You can download the combo updater from the Support site. Sites such as www.macfixit.com often recommend installing the combo updater instead of, or after, the delta updater, as it often solves mysterious problems. One specific example is the numerous "SUID" messages when doing a "repair permissions" - the combo update gets rid of all but one, and that one is specifically stated by Apple to be okay. Of course, no guarantees, but the combo updater is a reasonable thing to try.
Doug

How many hard drives can i install in my mac pro

How do I know what size hard drives I can install? I currently have 4 x 2TB drives installed and am looking to go bigger. 4 x 4TB would be ideal and if you have suggestions on which drives might give me best performance for HD video editing that would be nice too.
Also can I install more RAM?
ere is some information to help.
Mac Pro
Early 2008
Processor 2 x 2.8 GHz Quad-Core Intel Xeon
Memory 16 GB 800 MHz DDR2 FB-DIMM
Graphics 2 x NVIDIA GeForce GT 120 512 MB
Software Mac OS X Lion 10.7.3 (11D50b)
Model Name:          Mac Pro
Model Identifier:          MacPro3,1
Processor Name:          Quad-Core Intel Xeon
Processor Speed:          2.8 GHz
Number of Processors:          2
Total Number of Cores:          8
L2 Cache (per Processor):          12 MB
Memory:          16 GB
Bus Speed:          1.6 GHz
Boot ROM Version:          MP31.006C.B05
SMC Version (system):          1.25f4
Serial Number (system):          G************
Hardware UUID:          47DF4954-C493-50B8-85F3-FC381FA75AD6

PCIe SSD controller
www.macperformanceguide.com
That would be $1600 for your 16TB
There are kits to put 2.5" drives (4) in lower optical drive bay. Some WD 10K VR 500GB and 1TB ($200 and $300, 200MB/sec)
32GB 8 x 4GB FBDIMM 800MHz
GTX 570 w/ 10.7.3 from MacVidCards

10.5.7 Fundamental Incompatibility with Mac Pro - Screen/System Lock ups

Hi all.
It looks like 10.5.7 is causing a lot of problems, but I think I found a problem that is very fundamental.
First, my system. It's one of the original Mac Pros with Quad Xeons at 2.66GHz. It has 24GB of RAM and several drives in there. I have 3 30" displays plugged into 3 NVIDIA GeForce 7300GT cards. I originally ran a 10.5.7 combo update on my 10.5.6 system, and experienced these problems (detailed below). As I was also running a beta of iTunes and the iPhone SDK (the 3rd release), and beta 2 of Safari 4, I thought this may have caused some trouble. So, I tried an experiment.
I bought a new Corsair 256GB SSD for my startup drive. Loaded my family pack of 10.5.6 onto it as a fresh install, and just applied the 10.5.7 combo update. I get the exact same behavior with no further software. So, this is a fundamental incompatibility of 10.5.7 with a machine having these specs.
Now the problems. They start with the primary (in my case center) screen locking while the other two screens keep working. Meaning, the primary display "works" but none of the windows move, the clock freezes...yet, if you move the mouse there and luckily grab a window, you could move it out onto the other 2 displays and it would allow you to continue to use the application. If you hit the CONTROLkey and scroll up and down (zooming the display in and out) it can sometimes "unlock" the primary display, but then there are many artifacts. For example, the shadows cast by windows appear as plain grey "dashboard esque" blocks and have black stripes at the edges. Also, at random times, the machine just seems to hang completely, and unlock a minute or 2 later. Eventually it locks for good.
Unfortunately this has lead me into a deadlock situation. My iTunes has been updated to the 3rd beta in the iPhone 3.0 SDK release. The library has been modified and only works with that version now. That version requires 10.5.7. So if I revert back to 10.5.6, I lose my iTunes Library or have to wait till the offical version of iTunes is realeased (although that may still require 10.5.7).
I see lots of people are having Firewire (800 in particular) problems, and I have several drives I need on Firewire. It's not a solution to yank them. It all works fine under 10.5.6, of course.
So the question is...is help on it's way? What to do!?
Thanks for any insights.
More info on the system below:
Hardware Overview:
Model Name: Mac Pro
Model Identifier: MacPro1,1
Processor Name: Dual-Core Intel Xeon
Processor Speed: 2.66 GHz
Number Of Processors: 2
Total Number Of Cores: 4
L2 Cache (per processor): 4 MB
Memory: 24 GB
Bus Speed: 1.33 GHz
Boot ROM Version: MP11.005C.B08
SMC Version (system): 1.7f10
NVIDIA GeForce 7300 GT:
Chipset Model: NVIDIA GeForce 7300 GT
Type: Display
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x8
VRAM (Total): 256 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0393
Revision ID: 0x00a1
ROM Revision: 3008
Displays:
Cinema HD:
Resolution: 2560 x 1600
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
Display Connector:
Status: No Display Connected
NVIDIA GeForce 7300 GT:
Chipset Model: NVIDIA GeForce 7300 GT
Type: Display
Bus: PCIe
Slot: Slot-2
PCIe Lane Width: x8
VRAM (Total): 256 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0393
Revision ID: 0x00a1
ROM Revision: 3008
Displays:
Cinema HD:
Resolution: 2560 x 1600
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
Display Connector:
Status: No Display Connected
NVIDIA GeForce 7300 GT:
Chipset Model: NVIDIA GeForce 7300 GT
Type: Display
Bus: PCIe
Slot: Slot-3
PCIe Lane Width: x4
VRAM (Total): 256 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0393
Revision ID: 0x00a1
ROM Revision: 3008
Displays:
Cinema HD:
Resolution: 2560 x 1600
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
Display Connector:
Status: No Display Connected
ATA Bus:
SONY DVD RW DW-D150A:
Model: SONY DVD RW DW-D150A
Revision: 1.MD
Serial Number:
Detachable Drive: No
Protocol: ATAPI
Unit Number: 0
Socket Type: Internal
Low Power Polling: No
Power Off: No
TSSTcorpCD/DVDW SH-S162L:
Model: TSSTcorpCD/DVDW SH-S162L
Revision: LC02
Serial Number:
Detachable Drive: No
Protocol: ATAPI
Unit Number: 1
Socket Type: Internal
Low Power Polling: No
Power Off: No
FireWire Bus:
Maximum Speed: Up to 800 Mb/sec
Built-in Hub:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Unknown
FreeAgent Go FW:
Manufacturer: Seagate
Model: 0x2200
GUID: 0x20370200105F82
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Up to 200 Mb/sec
Sub-units:
FreeAgent Go FW Unit:
Unit Software Version: 0x10483
Unit Spec ID: 0x609E
Firmware Revision: 0x110
Product Revision Level: 410G
Sub-units:
FreeAgent Go FW SBP-LUN:
Capacity: 149.05 GB
Removable Media: Yes
BSD Name: disk5
Mac OS 9 Drivers: No
Partition Map Type: GPT (GUID Partition Table)
S.M.A.R.T. status: Not Supported
Volumes:
Seagate149GBTote:
Capacity: 148.73 GB
Available: 132.95 GB
Writable: Yes
File System: Case-sensitive Journaled HFS+
BSD Name: disk5s2
Mount Point: /Volumes/Seagate149GBTote
Unknown Device:
Manufacturer: Unknown
Model: Unknown
GUID: 0x0
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Unknown
OEM ATA Device 00:
Manufacturer: OEM
Model: 0x0
GUID: 0x30E102E0454B7D
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Up to 200 Mb/sec
Sub-units:
OEM ATA Device 00 Unit:
Unit Software Version: 0x10483
Unit Spec ID: 0x609E
Firmware Revision: 0x110
Product Revision Level:
Sub-units:
OEM ATA Device 00 SBP-LUN:
Capacity: 931.51 GB
Removable Media: Yes
BSD Name: disk4
Mac OS 9 Drivers: No
Partition Map Type: GPT (GUID Partition Table)
S.M.A.R.T. status: Not Supported
Volumes:
TimeMachine:
Capacity: 931.19 GB
Available: 606.63 GB
Writable: Yes
File System: Case-sensitive Journaled HFS+
BSD Name: disk4s2
Mount Point: /Volumes/TimeMachine
Unknown Device:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Unknown
Unknown Device:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Unknown
Unknown Device:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Unknown
Unknown Device:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Unknown
Unknown Device:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Unknown
Memory Slots:
ECC: Enabled
DIMM Riser A/DIMM 1:
Size: 4 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x8551
Part Number: 0x373254353132393230454641335343322020
Serial Number: 0x02007D11
DIMM Riser A/DIMM 2:
Size: 4 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x8551
Part Number: 0x373254353132393230454641335343322020
Serial Number: 0x02006013
DIMM Riser B/DIMM 1:
Size: 4 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x8551
Part Number: 0x373254353132393230454641335343322020
Serial Number: 0x0200711F
DIMM Riser B/DIMM 2:
Size: 4 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x8551
Part Number: 0x373254353132393230454641335343322020
Serial Number: 0x02007012
DIMM Riser A/DIMM 3:
Size: 2 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x830B
Part Number: 0x4E54324754373255344E4231424E2D334320
Serial Number: 0xA4730244
DIMM Riser A/DIMM 4:
Size: 2 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x830B
Part Number: 0x4E54324754373255344E4231424E2D334320
Serial Number: 0x70780241
DIMM Riser B/DIMM 3:
Size: 2 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x830B
Part Number: 0x4E54324754373255344E4231424E2D334320
Serial Number: 0xE4760245
DIMM Riser B/DIMM 4:
Size: 2 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x830B
Part Number: 0x4E54324754373255344E4231424E2D334320
Serial Number: 0xF0770241

I can only tell you that I've run 10.5.7 on my Mac Pro, same model as yours, without any problems. As a beta tester my Mac Pro was the main hardware on which 10.5.7 was tested. I currently have it installed on a first generation iMac, MacBook, and MacBook Pro as well as a second generation MacBook Pro. So far not a single problem.
But, I don't have multiple video cards nor do I use any beta version of iTunes (didn't know there was one since each system upgrade includes the current release) but I do use the Safari 4 Beta - the most recent version just released when 10.5.7 was released.)
I can suggest you read the following about updates of system software:
Essential Steps Before Updating OS X!
Please do things right before updating OS X in order to avoid problems.
A. Repair Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger and Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior (4.0 for Tiger, and 4.1 for Leopard) and/or TechTool Pro (4.6.1 for Leopard) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
B. Clone Using Restore Option of Disk Utility
1. Open Disk Utility from the Utilities folder.
2. Select the destination volume from the left side list.
3. Click on the Erase tab in the DU main window. Set the format type to Mac OS Extended (journaled, if available) and click on the Erase button. This step can be skipped if the destination has already been freshly erased.
4. Click on the Restore tab in the DU main window.
5. Select the destination volume from the left side list and drag it to the Destination entry field.
6. Select the source volume from the left side list and drag it to the Source entry field.
7. Double-check you got it right, then click on the Restore button.
Destination means your backup drive (should be erased first.)
Source means your startup drive or volume.
C. Download the Standalone Combo Updater from Apple.
Be sure you quit all running applications and disconnect all peripherals (except original keyboard and mouse) before running the installer. When the installer is running do not use the computer in any way other than to respond to an installer dialog.
Install the update by double-clicking on the installer package icon. When the installation is completed Restart the computer. Your computer will boot twice - this is normal. Upon completion of the update use Disk Utility to repair permissions. Not all permissions will seem repaired. You will get spurious reports regarding permissions related to iTunes, Front Row. These can be ignored. They will appear every time you repair permissions.
Following these basic steps should prevent most if not all updating problems. Note that if you have unrepairable disk problems reported in Step A then DO NOT update your system until those problems are resolved.
If you find that you did not follow these suggestions, then you might consider reinstalling OS X and going about the process properly in the hope of a successful result:
How to Perform an Archive and Install
An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
Repairing the Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.

TS2002 my mac pro takes a long time to start up!

i had my mac pro for less than a year.
i updated it to lion.
now, my mac heats up very fast, the fans won't stop running, and my startup seems to get slower and slower

I assume that's 117°F ?
Could be many things, we should start with this...
"Try Disk Utility
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Select your Mac OS X volume.
5. Click Repair Disk, (not Repair Permissions). Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)
If perchance you can't find your install Disc, at least try it from the Safe Boot part onward.
If 10.7.0 or later...
Bootup holding CMD+r, or the Option/alt key to boot from the Restore partitirion & use Disk Utility from there.
Then I'd get Lion Cache Cleaner & clear the caches...
http://www.northernsoftworks.com/lioncachecleaner.html
So, have you opened Console yet & seen any messages going by?

Do I need a 64 bit processor on my Mac Pro to run CS6 and Lightroom 4?

I would like to install Adobe CS6 and Lightroom 4 on my 2008 Mac Pro but may not have the right processor to run it. I know I will have to upgrade my OS X 10.5.8 to at least OS X 10.6.8. The system requirements specify a Multicore Intel processor with 64-bit support. I have a Quad-Core Intel Xeon processor. Does this mean my Mac will not run this software at all or slowly at best? Will I only be able to use this software if I buy a new computer?
Here is what I have now:
Hardware Overview:
Model Name:          Mac Pro
Model Identifier:          MacPro3,1
Processor Name:          Quad-Core Intel Xeon
Processor Speed:          2.8 GHz
Number Of Processors:          2
Total Number Of Cores:          8
L2 Cache (per processor):          12 MB
Memory:          6 GB
Bus Speed:          1.6 GHz
Boot ROM Version:          MP31.006C.B05
SMC Version (system):          1.25f4
Serial Number (system):
Hardware UUID:          A120CDBF-0CB3-56FA-9AF2-16F2938C5F0D
System Software Overview:
System Version:          Mac OS X 10.5.8 (9L30)
Kernel Version:          Darwin 9.8.0
Boot Volume:          Macintosh HD 320
Boot Mode:          Normal

Please see the tech specs for LR 4 : http://www.adobe.com/products/photoshop-lightroom/tech-specs.html
LR 4 and CS 6 applications will not run on 10.5.8, you need atleast 10.6.8 to run these applications.

WORKAROUND! - Sluggish Motion V 4.0.1 on Mac Pro Nehalem 2.97 GHz 16 Vcore

Hi guys, like several people on this forum and others I been very frustrated with the performance of both Motion.app version 3 and now Motion.app V4 .0 .1 (latest update) on my 2009 Mac pro Nehalem 2.97 GHz 16 Vcore 12GB with the ATI Radeon 4870 graphics card.
I have two workarounds that may be of assistance in relieving this issue. They work for me however before I discuss what they I'd like to set the scene.
Like many of us, I have trawled this forum and many others including COW and so on mostly relying on those 10-12 (the dozen or so) excellent tips from people like Mark Spencer and others. This includes the usual things like turning off rendering options that make heavy use of CPU/GPU etc.
Caveat: I'd also like to note here that this performance sluggishness has absolutely nothing to do (and is completely unrelated to) I/O performance nor is it related to memory usage. The reason I say this is because during some testing and the normal practice I keep all a Motion.app cache files (autosave, cached files etc) out on a very fast PROAVIO EB8NS disk array with ATTO R380 HBA onto SAS paths where this box is capable of over 450 MB per second measured with Kona system test tool. Additionally I have 12 GB of memory on this Mac pro which I assigned 70% of it to be available to Motion.app V4. The sluggishness Motion.app V4 is not manifest itself through the usual items such as excessive virtual memory page in/out or swap in/out activity. In fact in this scenario I describe below in my system when nothing else is running the former is non-existent! Additionally I also want to know that Motion.app V4 in my scenario/situation/environment is definitely and certainly NOT impacted by insufficient I/O bandwidth..
However, like many people, who have the same or similar setup to myself, we experience severe delays the most basic Motion.app UI such as: selecting an item, scrubbing through the timeline, performing any kind of transform etc etc. Many of us trying to diagnose this problem (looking for any kind of diagnostics or messages etc) have noticed that with the exception of one single core, the remaining cores to do very little (idle or just barely moving) whilst the remaining single core is taking out at 100% constantly.
Many months ago whilst really bogged down with this problem trying to complete a project, I contacted Mark Spencer who politely explained that notion exploits the on-board graphics card (in my case the ATI Radeon HD 4870). After frustratingly trying to improve the performance of this and completely reinstalling Final Cut Suite in a different brand-new (at the time MacOS X 10.5.6), I found that there was little difference.
I am mentioning all this because, I know that a few colleagues have had a similar problem and have not found any satisfaction in looking at this despite many well-informed forum users who offer excellent advice.
At my wits end (currently), I took a few days to try and isolate what the problems may be caused by (what exacerbates this severely degraded performance). This user interface sludgy degradation is manifested through the UI also has the (spinning beach ball).
I isolated pieces in some of the Motion.app projects and started to ISOLATE (Control-I) what I thought were quite complex layers and individual objects but to no avail. I then resorted to completely deleting them with some improvement in performance (noticeably less sluggyness) however it still was not lightning fast as I expected considering it I was in draft mode, 720 p resolution, with lighting, shadows and reflections completely turned off in the view.
*Motion.app BEHAVIOURS*: after some hours and a great deal of trial and error (non-productive work time I might add) it occurred to me that some of the Motion.app behaviours in particular place in the layer with as few as five objects in the layer (behaviours such as "Motion.app path", "wriggle", "oscillate" and even good old trusted "throw" seem to be the culprits in this particular layer.
I will note well here at this point, but of course "camera layers" does seem to be affected at all with the basic movements such as Dolly, frame, sweep etc. I have some sets up to 4 or five cameras which seems not to bother Motion.app at all!
*OBJECT SELECTION (S):* yes this also seems to have some degrading impact on playout, scrubbing and so on. Interesting I thought.
Workarounds: here are a few things that I know that work to get around some problems of working where Motion.app is extremely SLUGGY in the user interface (UI). Perhaps someone has already noted these on a forum or posted on however I couldn't find them.
So my workflow/practice here is to do the following when I'm manipulating objects (placement, set up, applying filters, adjusting timeline, and so on):
+WORKAROUND #1+: *DISABLE the behaviours* in the layers where you are performing any object manipulation. In fact we have many objects in many layers where the topmost layer (a group of nested layers) contains any behaviours, I would suggest you disable those whilst you work on that particular layer.
It's a very simple stylus click to enable the BEHAVIOURS layers that you have been working on to see what the effect of those behaviours when you want to play them out in the player/canvas.
I have no idea why such trivial behaviours cause my very expensive Mac pro to nearly lock up whilst in Motion.app version 4 and also version 3. Anyway is definitely works on me.
+WORKAROUND #2+: *DESELECT ANY ITEM IN THE CANVAS* (in any view) when attempting to play out whilst in the canvas. Again I don't know why having one or more items (including the camera) insert would have such a drastic impact on the performance of Motion.app to play out what I think is a frivolous range, however this really works for me.
*How to measure the performance or how to monitor the performance/usage of the ATI Radeon HD 4870 graphics card from MacOS X?* I would like to know exactly what this is doing on my system when one of the CPU cores is pegged out in 100% servicing requests from Motion.app. I can't find utility (which am willing to pay for) that sees the ATI Radeon HD 4870 graphics card. One I thought would have is an application called atMonitor.app (http://www.atpurpose.com/atMonitor/) which seems to do a pretty good job on my uni body MacBook Pro and wife's Macbook Air.
It would seem that any of the utilities don't seem to see the ATI Radeon HD 4870 or if they do and they initiate commands to it that the ATI Radeon HD 4870 and doesn't respond or send any replies status information. (Beats me I'm not a technical person these days)
Summary: I would be very interested if other people who have a similar if not pretty near exact setup as myself have found these two suggestions useful. I have tried some of these Motion.app projects on my MacBook Pro uni-body and with some difference the MacBook Pro exhibits similar sluggyness to this Mac pro.
W
Hong Kong

Mark, I took your advice and reinstall Final Cut Suite Version 3 (including Motion.app version 4.0.1) onto a completely different and I'm used file system including a brand-new install of MacOS X snow leopard 10.6.1, which I believe is the most recent update.
To be clear, I have all the latest Pro Applications updates as well apply to this brand-new system.
So here is the *bad new*s.
*Using exactly the same hardware configuration as I described in this theme of woe, I launched Motion.app V4 .0 .1 and opened up several of the projects that I'm having trouble with that is issued.*
Simply, the symptoms and observation I described in this thread exists with a brand-new installation.
Anyway looks like I have a backup/another instance available Final Cut Pro in case my main production image has trouble.
Once again, as I described initially in this thread, I used the two workarounds to overcome the consistent and overwhelmingly an exaggerated 20 seconds lag on average interactions with Motion.app with the success that I'd described previously.
In another thread back in September 2009, a forum poster mentioned that he felt that the camera framing behaviours were the root of this problem. And to this end he advised converting these behaviours to keyframes using the command-K ("convert to keyframes") to overcome his misery.
This indeed does work very well. So this is the third workaround and I'm starting to use.
Further I have done some more hard comparisons with my 2009 MacBook pro uni-body 2.93 GHz with a standard arrangement of 4 MB of memory and the usual disk internally. *To my great surprise*, I found that the projects that I'm having a lot of trouble with were much more responsive not only with the camera framing behaviours (which I'm not particularly having any trouble with), but the layers that contains a simple transform behaviours such as "motion path", "wiggle", and so on did not seem to bother the Mac book pro.
I watched the CPU cores on the Mac book pro maybe go to 80% while the project was loading, and also whilst I gingerly navigated through the project although feeling a little sluggy was far less in orders of 10 to 20 seconds faster than this Mac pro Nehalem with all the bells and whistles on my earnings embedded within it.
Now I'm starting to wonder, as Andy pointed out, +maybe there is some trouble with the hardware in this system+. I really could not know how to determine if this is the case. However before I draw this conclusion finally, I noticed that there are a lot more people out there with the same consideration as I have that have this same problem. It's not narrowed down to those owners with the ATI Radeon HD 4870 graphics card, however these seem to be the bulk of the people who are trying to do things that are getting a fair amount of forum time (like me).
There certainly seems to be something of an issue as there are some symptom dumps for Motion.app but only one or 2 to over this period that seemed to be triggered by something on this machine. And like many on this forum I gave up reading dumps for a living back in the 1990s.
I would really like to know how I can diagnose this problem before I had to pack this Mac pro up and carted back to the local Apple care centre here in Hong Kong (which means I won't have it forever while, which means no income). Yes I can use my Mac book pro uni-body which is I might end up doing.
_Oh, and this little gem._ I find that if I invoke the "timeline pane/window" (command-7), that it can take up to 2 seconds to refresh the screen. It is amazingly slow and feel like there is definitely something wrong.
If I have a simple motion project by that I mean some simple plates some moving text and no real 3-D except for one little camera Motion.app V 4 seems to work quite okay.
The sets that I'm working in at about eight or nine cameras over the timeline and maybe three or four sets in the project. This is not the work I think especially when most of the moving here is a few objects wobbling around in 3-D space and quick camera moves using the camera framing behaviour.
In summary, having spent what seems to be 40 or 50 hours messing with this issue are not doing anything productive, I've come to the conclusion that there is definitely something wrong with this setup that I have. However having had no problem with that up until now (I know actually I had some problems back in May 2009 with it but it seemed that install a Final Cut Suite version 2 completely fixed it.
And I am totally surprised that my Mac book pro uni-body if pressed can do the job that I want.
Therefore Motion Forum users, I really don't know what else there is to do other than to poke around over time and eventually something will fix this because it is really very frustrating and like many of us on this forum I did endeavour to pay for/put capital funds into a system highly recommended by many that uses Apple production applications than I expected it would work.
By the way, I noticed when I use Nuke version 5 and Shake V 4.1 and even Maya PE, I don't have these issues but will concede that I doubt whether the use applications take advantage directly of the GPU arrangement in the graphics card like Motion.app does.
That's all I have.
Any other thoughts are most welcome.
W

Como vacio el cache en mi mac pro

Similar Messages

Maybe you are looking for