DVDSP run under Leopard?

Hi!
I've been combing eBay for a copy of FCS or FCS2 and been researching how DVDSP 3 or 4 runs under Leopard before I purchase.  Unfortunately I see a lot of folks that have had issues running DVDSP 3 or 4 (FCS or FCS 2) under Leopard.
Essentially, I am currently running 10.5.8 on a G5 1.8 DP and I am looking for a version of DVDSP that will run under this so I don't have to use a dual boot system just to burn DVDs.  Is there a version of DVDSP that will run under this configuration, or do I have to buy an Intel Mac?
Additionally, if I do buy an Intel Mac, can I get  away with a MacBook to run DVDSP and FCP and save the heavy lifting of Motion and/or Color for a desktop?
Thanks!

I don't have any significant experience with Leopard other than on a Mac Pro, but I've had full FCS2 installs running on 2.5GHz G5 dualies (Tiger) since it was released and have both FCS2 and FCS3 running on Snow Leopard flawlessly.
Apple says you need an Intel processor to run FCS3, but the Get Info for FCP7 says the code is universal and therefore it may run on a G5. Irrespective of that, DVDSP4 should run fine on your G5.
As for what you can "get away with" on a MacBook, you may find that the lack of firewire on recent MacBooks a problem. Additionally, I'm not sure about the video support. The MacBook Pro is a better choice, but more expensive. You may want to look into a used Mac Pro as an alternative.

Similar Messages

  • Will my programs run under Leopard?

    I have a G5 iMac currently running Tiger and I am thinking of upgrading to Leopard. I am wondering if I will need to upgrade some of my programs as well. They are Quicken 2004, Adobe Acrobat 7.0 Professional, Adobe elements 2, Fetch 4.0.3, Microsoft Office 2004, Superduper 2.5.
    Thanks
    Jerry

    Your SuperDuper and Office are good, I run Quicken '05 however.
    Joe

  • Entourage (running under leopard) in microsoft exchange

    Is it possible that entourage in leopard works properly or I need to update to snow leopard. It tooks me one week but I´m not able to do it right.
    thanks again.

    Please post Entourage related questions on MIcrosoft's own forums for their Mac products:
    http://www.officeformac.com/productforums

  • Some images created in Tiger unusable under Leopard - can crash Aperture

    I have tried both updates and clean installs of Leopard on my MBP and external firewire disks. In both cases I find that a large number of images in my libraries (built under Tiger), give Aperture fits. For example, whilst I can see thumbnails, I can't export versions - messages come up to say the images can't be decoded. Similarly, if I try to edit or view some images full screen, I get a message saying "unsupported format". At times, trying to work with these images crashes Aperture.
    In a couple of cases, I still have the offending images on cards and I was then able to import them anew into Aperture (running under Leopard) - these work OK.
    Boinx Fotomagico under Leopard stopped running and quit without warning trying to run previously created slideshows that incorporate some of the above-mentioned images.
    I conclude that there is a problem with Leopard's treatment of images rather than Aperture specifically. However, I have no clue how to address the problem. At present Leopard is just unusable for me.

    Hello
    a - my way of life is the Winston Churchil's one : "absolutely no sport"
    b - as during more than 30 years I ruled a pottery workshop using a process which is unique worldwide, I know what confidentiality means.
    c - Whe I exchange with Apple, they don't ask me to sign a Non Disclosure Agreement.
    They perfectly know that when I beta tested I NEVER violate the signed ones.
    I'm aware of anomalies when using Numbers under Leopard.
    Maybe you met one which I ignored.
    Knowing such of these problems, I decided to use Tiger as my main operating system.
    Here, as I play safety, Leopard is always in test, not in real use.
    Yvan KOENIG (from FRANCE samedi 19 janvier 2008 17:20:41)

  • Spontaneous Intel iMac Reboot under Leopard

    I have three upgraded machines running under Leopard, two MacBooks and one Intel iMac. On only the Intel iMac I am experienced what can best be described as spontaneous reboots. Suddenly while working (web browsing with Safari) the screen will blank, no sound and reboot to the login screen.
    Has happened twice in the last two days ... anyone else seeing this problem? Solution?

    Same sort of problem here. We use the machine primarily for viewing TV in the kitchen with eyeTV. There is no clear pattern to the reboots. This log shows the timestamps of recent reboots.
    Nov 25 21:47:21 iLife bootlog[46]: BOOT_TIME: 1196045228 0
    Nov 26 04:23:47 iLife bootlog[46]: BOOT_TIME: 1196069015 0
    Nov 26 22:34:50 iLife bootlog[47]: BOOT_TIME: 1196134479 0
    Nov 27 08:22:04 iLife bootlog[46]: BOOT_TIME: 1196169712 0
    Nov 27 21:21:25 iLife bootlog[47]: BOOT_TIME: 1196216471 0
    Nov 28 16:17:25 iLife bootlog[46]: BOOT_TIME: 1196284634 0
    Nov 28 17:10:21 iLife bootlog[46]: BOOT_TIME: 1196287809 0
    Nov 29 08:15:32 localhost bootlog[47]: BOOT_TIME: 1196342115 (user initiated reboot)
    Dec 1 12:08:04 iLife bootlog[46]: BOOT_TIME: 1196528873 0
    Dec 2 20:37:39 localhost bootlog[47]: BOOT_TIME: 1196645847 0 (user initiated reboot)
    Dec 3 17:23:53 iLife bootlog[46]: BOOT_TIME: 1196720623 0
    Since 11/29 all other apps but eyeTV have been turned and kept off. Two reboots since. We have eyeTV running on two other machines (iMac G5 and MacPro) with no problems so we do not believe the issue is that software. Will happily provide syslogs to Apple if they are interested.

  • My app will no longer run under Snow Leopard, runs fine under Lion.

    My app will no longer run under Snow Leopard, even though it was originally written for Snow Leopard.  It runs fine on my Dev machine under Lion. But when I test it on my Snow Leopard Mac Mini the app starts but the window does not appear. Going to file, new window does nothing. My depolyment target is set to 10.6. Is there something I did to make my app lose Snow Leopard compatiblty?

    Does your application use features only available in Lion?  Are you getting any console logs?

  • I'm running snow leopard. The try to open any .mov file in Quicktime, and I get an error message that says, "The document xyz.mov could not be opened. The movie is not in a format that Quicktime player understands. I'm a recent upgrade to Snow Leopard.

    I'm running snow leopard. The try to open any .mov file in Quicktime, and I get an error message that says, "The document xyz.mov could not be opened. The movie is not in a format that Quicktime player understands. I'm a recent upgrade to Snow Leopard.
    Help!
    Thanks, Mark

    Unfortunately, the error message gives no details about what codec might be missing or what it needs.
    If the file can't be opened in QT, it only means you cannot use the QT "Inspector" window to check what compression formats were used to create the file. It does not mean you can't use the Finder "Information" window to check on the compression formats or use a third party media information window (e.g., like VLC which will open many compression formats not supported natively by QT) to determine what kind of data is included in the MOV wrapper. If the file cannot be opened in any app, it is usually a good sign that the file itself is corrupted.
    It's a stupid error message. Apple should do better than that.
    Error trapping is quite extensive but there are still many areas which require human oversight. The message is telling you that either the container has a problem (e.g., not properly terminated, non-standard, or corrupted) or that one or more of the compression formats used is not supported by your current codec component configuration or that the data was encoded using non-standard settings or preferences not supported by QT or that the fourCC code does not match the data contained in the file or that there are timecode inconsistencies, etc., etc., etc. In short there are a near infinite number of possible problems for which it would be very difficult/nearly impossible to program error trapping depending on your sourcing of content and how you process it before it reaches the player app. Think of it like trying to play a BD disc in an DVD player.
    I'll call Apple support when I get a chance.
    Chances are good that they will end up sending you back here. In any case, it is often a good idea to post a sample file for examination by other QT users. At the very least, they should be able to tell you if the sample file will play on other systems which would indicate whether or not the file itself is bad and under the best of circumstances whould allow them to examing the file in detail for various common problems.

  • HT1338 Purchased a used macbook pro with Mountain Lion. My old Mac runs Snow Leopard is backed up to Time machine. How do I register the operating system to me and how do I use Time Machine to move my files to the new used computer?

    Purchased a used macbook pro with Mountain Lion. My old Mac runs Snow Leopard is backed up to Time machine. How do I register the operating system to me and how do I use Time Machine to move my files to the new used computer?

    If you look at the User Tips tab, you will find a write up on just this subject:
    https://discussions.apple.com/docs/DOC-4053
    The subject of buying/selling a Mac is quite complicated.  Here is a guide to the steps involved. It is from the Seller's point of view, but easily read the other way too:
    SELLING A MAC A
    Internet Recovery, and Transferability of OS & iLife Apps
    Selling an Old Mac:
    • When selling an old Mac, the only OS that is legally transferable is the one that came preinstalled when the Mac was new. Selling a Mac with an upgraded OS isn't doing the new owner any favors. Attempting to do so will only result in headaches since the upgraded OS can't be registered by the new owner. If a clean install becomes necessary, they won't be able to do so and will be forced to install the original OS via Internet Recovery. Best to simply erase the drive and revert back to the original OS prior to selling any Mac.
    • Additionally, upgrading the OS on a Mac you intend to sell means that you are leaving personally identifiable information on the Mac since the only way to upgrade the OS involves using your own AppleID to download the upgrade from the App Store. So there will be traces of your info and user account left behind. Again, best to erase the drive and revert to the original OS via Internet Recovery.
    Internet Recovery:
    • In the event that the OS has been upgraded to a newer version (i.e. Lion to Mountain Lion), Internet Recovery will offer the version of the OS that originally came with the Mac. So while booting to the Recovery Disk will show Mountain Lion as available for reinstall since that is the current version running, Internet Recovery, on the other hand, will only show Lion available since that was the OS shipped with that particular Mac.
    • Though the Mac came with a particular version of Mac OS X, it appears that, when Internet Recovery is invoked, the most recent update of that version may be applied. (i.e. if the Mac originally came with 10.7.3, Internet Recovery may install a more recent update like 10.7.5)
    iLife Apps:
    • When the App Store is launched for the first time it will report that the iLife apps are available for the user to Accept under the Purchases section. The user will be required to enter their AppleID during the Acceptance process. From that point on the iLife apps will be tied to the AppleID used to Accept them. The user will be allowed to download the apps to other Macs they own if they wish using the same AppleID used to Accept them.
    • Once Accepted on the new Mac, the iLife apps can not be transferred to any future owner when the Mac is sold. Attempting to use an AppleID after the apps have already been accepted using a different AppleID will result in the App Store reporting "These apps were already assigned to another Apple ID".
    • It appears, however, that the iLife Apps do not automatically go to the first owner of the Mac. It's quite possible that the original owner, either by choice or neglect, never Accepted the iLife apps in the App Store. As a result, a future owner of the Mac may be able to successfully Accept the apps and retain them for themselves using their own AppleID. Bottom Line: Whoever Accepts the iLife apps first gets to keep them.
    SELLING A MAC B
    Follow these instructions step by step to prepare a Mac for sale:
    Step One - Back up your data:
    A. If you have any Virtual PCs shut them down. They cannot be in their "fast saved" state. They must be shut down from inside Windows.
    B. Clone to an external drive using using Carbon Copy Cloner.
    1. Open Carbon Copy Cloner.
    2. Select the Source volume from the Select a source drop down menu on the left side.
    3. Select the Destination volume from the Select a destination drop down menu on the right
    side.
    4. Click on the Clone button. If you are prompted about creating a clone of the Recovery HD be
    sure to opt for that.
    Destination means a freshly erased external backup drive. Source means the internal
    startup drive. 
    Step Two - Prepare the machine for the new buyer:
    1. De-authorize the computer in iTunes! De-authorize both iTunes and Audible accounts.
    2, Remove any Open Firmware passwords or Firmware passwords.
    3. Turn the brightness full up and volume nearly so.
    4. Turn off File Vault, if enabled.
    5. Disable iCloud, if enabled: See.What to do with iCloud before selling your computer
    Step Three - Install a fresh OS:
    A. Snow Leopard and earlier versions of OS X
    1. Insert the original OS X install CD/DVD that came with your computer.
    2. Restart the computer while holding down the C key to boot from the CD/DVD.
    3. Select Disk Utility from the Utilities menu; repartition and reformat the internal hard drive.
    Optionally, click on the Security button and set the Zero Data option to one-pass.
    4. Install OS X.
    5. Upon completion DO NOT restart the computer.
    6. Shutdown the computer.
    B. Lion and Mountain Lion (if pre-installed on the computer at purchase*)
    Note: You will need an active Internet connection. I suggest using Ethernet if possible because
    it is three times faster than wireless.
    1. Restart the computer while holding down the COMMAND and R keys until the Mac OS X
    Utilities window appears.
    2. Select Disk Utility from the Mac OS X Utilities window and click on the Continue button. 
    3. After DU loads select your startup volume (usually Macintosh HD) from the left side list. Click
    on the Erase tab in the DU main window.
    4. Set the format type to Mac OS Extended (Journaled.) Optionally, click on the Security button
    and set the Zero Data option to one-pass.
    5. Click on the Erase button and wait until the process has completed.
    6. Quit DU and return to the Mac OS X Utilities window.
    7. Select Reinstall Lion/Mountain Lion and click on the Install button.
    8. Upon completion shutdown the computer.
    *If your computer came with Lion or Mountain Lion pre-installed then you are entitled to transfer your license once. If you purchased Lion or Mountain Lion from the App Store then you cannot transfer your license to another party. In the case of the latter you should install the original version of OS X that came with your computer. You need to repartition the hard drive as well as reformat it; this will assure that the Recovery HD partition is removed. See Step Three above. You may verify these requirements by reviewing your OS X Software License.

  • Problems with ViaVoice under Leopard, especially key mapping problems

    ViaVoice's behavior has changed considerably under Leopard. First I will discuss the key mapping problem, since I'm eagerly looking for an answer to this problem. At the end of this post, I will voice some of the other problems I've experienced for those who may be interested. The key mapping problem may be specific to the fact that I use a foreign keyboard with a US version of ViaVoice.
    INTRO:
    I have used ViaVoice on my Mac for years, more or less without problems (ViaVoice's bugginess is notorious).
    Those who know ViaVoice will know that one has two general options for dictation. One can dictate into ViaVoice's so-called SpeakPad, which allows special formatting, editing and dictation error correction within the dictated text, or one can dictate into "external" software such as Microsoft Word, in which case ViaVoice just sends a string of characters to that software. SpeakPad appears to make strong use of the operating system's built-in functionality for character formatting, document formatting, etc.
    *MY PROBLEM*
    I have a German keyboard on my PowerBook, yet dictate in US English. When I dictated into SpeakPad under Tiger, all characters appeared correctly. However, when I dictated into Microsoft Word using Tiger, I had to switch the keyboard mapping from German to US to get all characters (that means including the characters that are located at different positions on a German keyboard than they are on a US keyboard such as y, z, apostrophes and parentheses) to appear correctly.
    Under Leopard, things have changed. Now it doesn't matter whether I dictate into SpeakPad or Word; the results are the same and many characters do not appear correctly.
    If set to a German keyboard, y and z appear as expected. To name a few irregularities:
    "(" appears as ")"
    ")" appears as "="
    apostrophes appear as "#" and
    ";" appears as ","
    If set to a US keyboard, y and z are interchanged. "(" and ")" appear as expected. Apostrophes appear as "\" and ";" appears as ","
    By comparison, if typed (as opposed to dictated, as in the examples above) "correctly" (i.e. based on the letters printed on the keyboard) on a German keyboard set to imitate a US keyboard:
    y and z are interchanged
    apostrophes appear as "|"
    "(" appears as "*"
    ")" appears as "(" and
    ";" appears as the symbol for "less than"
    Since I don't have a US keyboard, I can't say how it would behave if set to imitate a German keyboard, i.e. if there's a correlation to the results I get when I dictate.
    Since I was previously able to dictate correctly into SpeakPad by setting the keyboard to "German" and into Word by setting the keyboard to "US," I presume that this is a problem in Leopard, not ViaVoice.
    *OTHER PROBLEMS WITH VIAVOICE UNDER LEOPARD*
    In addition to the aforementioned key mapping problems (that may be specific to those of us with foreign keyboards), ViaVoice appears to have lost considerable functionality in Leopard. I cannot access SpeakPad's Preferences and the correction window. Moreover, the traffic-light like window buttons have disappeared from the VoiceCenter (although they work if you click where they should be). SetupAssistent appears to function.
    I've written to Nuance about these problems, but have little hope that they will invest the time in producing a patch since they haven't released any updates since 2003.

    Thrums1,
    I've never had to "register" ViaVoice after updating the system. I thus suspect you haven't fully followed my above, three-step advice (particularly step 3).
    1) Reinstall ViaVoice from CD.
    2) Update to the latest version (using the patch downloadable from Nuance's website).
    3) Replace the “temp” and “users” folders (in the "ViaVoice" folder at the upper level of your home directory) by a previous copy thereof. When I say previous copy, I mean a copy from when ViaVoice was still working properly, e.g. a copy from when it was running under Tiger.
    As I said, I've gotten ViaVoice to survive several system updates by following the above steps. To my knowledge, the last step is critical since it saves you from having to reconfigure ViaVoice under the new operating system (in this case Leopard). I suspect that ViaVoice is crashing on your system because it's trying to start some module of the SetUpAssistant that is incompatible with Leopard (as many are). If you instead use old copies of the "temp" and "users" folders (from the previous system), then ViaVoice doesn't have to go through the initial "registration" process; ViaVoice doesn't need the SetUpAssistant; and all is (more or less) fine.
    Good luck!
    BTW, to my knowledge, Dictate only runs on Intel Macs. It thus won't run on a G4 iBook, just as it won't run on my PowerBook G4.

  • Workaround to import video in FCP 6.0.5 under Leopard

    On behalf of a FCP user under Leopard with FCP 6.0.5 I would like to ask you how to import video from a Panasonic camcorder using some strange format. The workaround now is to import it on another machine under Snow Leopard with iMovie, export it as one .mov 'for computer use' and import it in FCP 6.0.5 on the Leopard machine. The video from the camcorder does not play under Leopard, probably because of the QT version 7.6.6.
    The Panasonic camcorder has an SD card with video which is recognised as a Camera Archive. It has folders with a name like PRG001 containing files like MOV001.MOD and MOV001.MOI and PRG001.PGI.
    Possibly there is some plugin, extention or other workaround?
    It is currently too expensive to upgrade FCP 6.0.5 to the latest version, although the 2006 MacBook Pro with Intel might be able to run it. I was advised not to upgrade to Snow Leopard without upgrading FCP, because it will cause all kinds of trouble.

    Although I would still need to buy the "QuickTime MPEG-2 Playback Component for Mac OS X" to work with it, right? At least that is what MPEG Streamclip suggests when I try to open the MOVxxx.MOD files with it.

  • CUPS printing to remote server doesn't work under Leopard

    So i have an ubuntu system running cups 1.2.8 as a print server. i have an epson stylus colour 760 plugged in and configured and working.
    i also had a macmini running tiger printing to it fine via ipp. now it didn't occur to me that something as simple (and important) as printing would be severely broken under Leopard. basically, after the upgrade, i can't print at all to the remote cups server.
    the symptoms are that the job queue will pause; even after clicking on 'resume', it will start the progress bar, and then after 100%, it will just pause again.
    i have on the cups server (qbic)
    EpsonPrinter
    Description: Epson Stylus 760 Colour
    Location: Small Bedroom
    Make and Model: Epson Stylus Color 760 - CUPS+Gutenprint v5.0.0.99.1
    Printer State: idle, accepting jobs, published.
    Device URI: usb://EPSON/Stylus%20COLOR%20760
    And on the macmini:
    qbic
    Description: qbic
    Location:
    Printer Driver: Epson Stylus Color 760 - Gutenprint v5.1.3
    Printer State: stopped, accepting jobs, not published.
    Device URI: ipp://192.168.1.244/ipp/EpsonPrinter
    None of the following work
    - used lpd://192.168.1.244/EpsonPrinter
    - tried ipp://192.168.1.244/ipp/EpsonPrinter
    - tried ipp://192.168.1.244/EpsonPrinter
    The error messages from the macmini are:
    I [01/Jan/2008:23:19:52 +0000] Printer "qbic" started by "ytl".
    I [01/Jan/2008:23:19:52 +0000] [Job 25] Started filter /usr/libexec/cups/filter/cgpdftoraster (PID 791)
    I [01/Jan/2008:23:19:52 +0000] [Job 25] Started filter /usr/libexec/cups/filter/rastertogutenprint.5.1 (PID 792)
    I [01/Jan/2008:23:19:52 +0000] [Job 25] Started backend /usr/libexec/cups/backend/ipp (PID 794)
    E [01/Jan/2008:23:20:02 +0000] [Job 25] Destination printer does not exist!
    E [01/Jan/2008:23:20:02 +0000] PID 794 (/usr/libexec/cups/backend/ipp) stopped with status 4!
    I [01/Jan/2008:23:20:02 +0000] Hint: Try setting the LogLevel to "debug" to find out more.
    I [01/Jan/2008:23:20:02 +0000] [Job 25] Backend returned status 4 (stop printer)
    I [01/Jan/2008:23:20:02 +0000] Saving printers.conf...
    The job never appears on the cups server jobs list; however a tcpdump does show that there is communication:
    x@qbic:~$ sudo tcpdump -i eth0 port 631
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
    23:27:55.397616 IP 192.168.1.204.49599 > qbic.ipp: S 3571921204:3571921204(0) win 65535 <mss 1460,nop,wscale 3,nop,nop,timestamp 660419916 0,sackOK,eol>
    23:28:05.490215 IP qbic.ipp > 192.168.1.204.49599: S 3610561258:3610561258(0) ack 3571921205 win 5792 <mss 1460,sackOK,timestamp 2498972 660419916,nop,wscale 2>
    23:28:05.490269 IP 192.168.1.204.49599 > qbic.ipp: . ack 1 win 65535 <nop,nop,timestamp 660419916 2498972>
    23:28:05.490285 IP 192.168.1.204.49599 > qbic.ipp: P 1:155(154) ack 1 win 65535 <nop,nop,timestamp 660419916 2498972>
    23:28:05.490301 IP qbic.ipp > 192.168.1.204.49599: . ack 155 win 1716 <nop,nop,timestamp 2498972 660419916>
    23:28:05.490315 IP 192.168.1.204.49599 > qbic.ipp: P 155:457(302) ack 1 win 65535 <nop,nop,timestamp 660419916 2498972>
    23:28:05.490331 IP qbic.ipp > 192.168.1.204.49599: . ack 457 win 1984 <nop,nop,timestamp 2498972 660419916>
    23:27:55.453575 IP qbic.ipp > 192.168.1.204.49599: P 1:26(25) ack 457 win 1984 <nop,nop,timestamp 2498978 660419916>
    23:27:55.453705 IP 192.168.1.204.49599 > qbic.ipp: . ack 26 win 65535 <nop,nop,timestamp 660419917 2498978>
    23:27:55.453804 IP qbic.ipp > 192.168.1.204.49599: P 26:225(199) ack 457 win 1984 <nop,nop,timestamp 2498978 660419917>
    23:27:55.453861 IP qbic.ipp > 192.168.1.204.49599: P 225:354(129) ack 457 win 1984 <nop,nop,timestamp 2498978 660419917>
    23:27:55.453919 IP 192.168.1.204.49599 > qbic.ipp: . ack 225 win 65535 <nop,nop,timestamp 660419917 2498978>
    23:27:55.453959 IP 192.168.1.204.49599 > qbic.ipp: . ack 354 win 65535 <nop,nop,timestamp 660419917 2498978>
    23:27:55.456571 IP 192.168.1.204.49599 > qbic.ipp: F 457:457(0) ack 354 win 65535 <nop,nop,timestamp 660419917 2498978>
    23:27:55.456636 IP qbic.ipp > 192.168.1.204.49599: F 354:354(0) ack 458 win 1984 <nop,nop,timestamp 2498978 660419917>
    23:27:55.669906 IP qbic.ipp > 192.168.1.204.49599: F 354:354(0) ack 458 win 1984 <nop,nop,timestamp 2498999 660419917>
    23:27:55.670050 IP 192.168.1.204.49599 > qbic.ipp: . ack 355 win 65535 <nop,nop,timestamp 660419919 2498999>
    23:28:08.470574 IP qbic.ipp > 192.168.1.255.ipp: UDP, length 183
    Any help is appreciated!

    The default setting under Tiger was CUPS, under Leopard it is Bonjour.
    To access CUPS
    http://localhost:631/printers/

  • IPhoto 7.1.1 Under Leopard 10.5.1 Will not print photo under "save as PDF"

    iPhoto 7.1.1 Under Leopard 10.5.1.
    Select a photo, choose "print" icon at bottom of iPhoto window.
    Choose "print".
    Choose "Save as PDF".
    Result: Unknown error message appears with white space (no text) in message box, but with "OK" button.
    Hit "OK button".
    RESULT: iPhoto prints a screen shot of the iPhoto window and renders it to a PDF file.
    In other words, *the print function under iPhoto does not work*. It yields an error every time that does not have a message, then *instead of printing the selected photo, takes a PDF screen shot of the iPhoto window*.
    This is an example of poor programming. And of course, there is no way to fix it, or to get help.
    Is anyone else having this problem?

    This is an example of poor programming.
    How do you come to this conclusion. It's working fine for me. You're the first to report such an issue.
    First repair disk permissions with Disk Utility and delete the iPhoto preference file, com.apple.iPhoto.plist, that resides in your User/Library/Preferences folder. A corrupted pref file can cause all sorts of unusual performance problems. If that doesn't help, log into another account and try from there. If it still doesn't work a reinstall of iPhoto seems warranted. To reinstall iPhoto you'll have to delete the current application and all files with "iPhoto" in the file name that reside in the HD/Library/Receipts folder.
    It iPhoto performs correctly in the other account then your primary account is the culprit and may be a preference file other than iPhoto's that's at fault. To determine if that's the case try the following;
    Trouble Shooting Preferences
    Go to HD/Users/Your_name/Library. Move the Preferences folder (in its entirety) to the Desktop and make a second copy of it so you have Copy A and B. Now try the the process again and determine if problem is fixed.
    If the problem IS fixed, then go to the new Prefs folder that the OS will have created and open it up.
    Open Copy B on the Desktop and select all of the items inside. Drag them into the open new library folder. When the Copy window comes up check the Apply to All check box and then click on the Don't Replace button as seen here. That will keep the new files created and bring back all of the others.
    If the problem is NOT fixed, trash the new Prefs folder and move the intact Copy A folder back to the Library folder .
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
    I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

  • I can't find the mac app store on my imac. i am running snow leopard, and i have run "update software" several times. what's up?

    I am trying to upgrade to Lion. I need to go through Mac App store to buy it. I need to get the Mac App store icon in my dock. I have run Update Software several times, trying to get the Mac App store onto my iMac, but with no luck. It doesn't show up in the dock, it doesn't show up in Finder under Applications, and it doesn't show up when I search in Searchlight for App Store, Store, Mac App Store, etc. What am I doing wrong?

    I am running snow leopard
    James....
    You arne't necessarily doing anything wrong.
    Install the Mac OS X 10.6.8 Update Combo
    That should reinstall the App Store for you.
    Restart your Mac after the combo is finished installing.
    You should see the App Store icon in the Dock and be able to access from your Apple menu also.
    Make sure your Mac meet's Lion's requirements

  • InDesign CS4 will not run under Lion

    I have InDesign CS4 and Design Suite CS3. All my other CS3 apps run under Lion. The Upgrade to Lion failed leaving my internal unbootable, so I installed and migrated to an external drive. But after the upgrade to Lion all of the other CS 3 aps run, IDCS4 will not run. I get the following message:
    Adobe InDesign is missing required system fonts or CMap files. Please reinstall InDesign.
    I used the uninstaller and reinstalled. No affect. I made the Library folder visible. No effect. I cant

    There is a very long list of incompatibilities with Lion:
    http://kb2.adobe.com/cps/905/cpsid_90508.html
    I'm sure there are many more that are unknown.
    FWIW, I highly recommend sticking with Snow Leopard for now and when you do upgrade, do so as a clean install.
    John will be along soon to tell you to ignore the man behind the curtain.
    Bob

  • Using Encore 3 Under Leopard 10.5.4

    I have recently purchased the Adobe Production Premium package and successfully prepared several Blu-ray and standard definition DVD's using Encore 3. However, whenever I attempt to output any of these DVD's to Flash Video by selecting Build>Output to Flash from within Encore 3, my menus transcode, but when Encore gets to my timeline video, the progress bar goes to about 20% almost instantly and remains there forever. I have tried several different types of video files including short Quicktime movies created in Final Cut Pro as well as other formats in the Encore 3 timeline. The result is always as given above. When this happens, I finally have to Force Quit Encore 3 because selecting cancel on the transcode give me an endlessly spinning beach ball.
    I am running Encore 3 (latest updates installed) on an 8-core Mac Pro (Early 2008 model) with 12 GB of RAM and under Leopard 10.5.4 (latest version with all updates installed). I have successfully transcoded these timelines that seem to freeze Encore 3 using MPEG SlipStream so I know the files are OK.
    Is anyone else having this problem? Is there any solution to the problem? Does output to Flash simply not work under Leopard?
    I have posted this problem on both the Adobe Encore User Forum and written to Adobe Tech Support. I have received no response from Adobe.
    Thank you in advance for responding.
    Tom

    Since no one replied, I can now confirm that the failure of Adobe Encore CS3 to successfully build a DVD to Flash Video is a known problem which has been confirmed by Adobe Technical Support. The feature works perfectly under Windows XP or Vista and it did work in Leopard on an earlier version of Quicktime, specifically Quicktime. specifically Quicktime 7.3.1. However, under the latest version of Quicktime (7.5), the Build to Flash Video feature in Encore CS3 has been broken. I have provided detailed feedback to Apple on this issue. One can only hope that in a future release of Quicktime, the problem will be corrected.
    Tom

Maybe you are looking for