PowerMac G4 and Leopard?

I heard Leopard needs at least 867 Mhz to run with a G4 processor but will a PowerMac G4 with 2 PowerPC G4 processors work? One processor is 450 Mhz and the other is 450 Mhz so total that 900 Mhz so will it work?

Yes, but slowly.
The installer will actually install on something less than 867MHz if it is a dual? For example, I have a dual 800 which falls slightly below the 867 mark but not according to you if it is a dual. I'm not rushing out to buy Leopard but Apple doesn't mention dual processor machines on the Leopard spec. page and it might be handy to have a triple booting computer (OS9 native/Tiger/Leopard).
I know that people have been bypassing the formal install procedure as a challenge to get it to run on old machines but that's another matter.
Message was edited by: Limnos

Similar Messages

How do I find the hardware specs? (iMAC, PowerMac G3 and PowerPC)

For starters I have never used a mac before
We have some iMACs, PowerMac G3s and PowerPCs in stock which have had their HDDs erased (zero'd) so there is no OS installed.
I need to find the CPU type/speed & RAM size
Is there a boot cd I can load to determine this?
I assume there is no BIOS feature like in PCs where the hardware is listed?
Many thanks
Paul

A "boot CD" for a Mac is the Mac OS X installation disc that comes with it. You obviously don't have that... Mac's should always be sold with its original discs, but that's a pipe dream, I suppose.
The next best thing is a retail Mac OS X installation disc. These are the discs Apple sells "in a box" to owners of existing Macs in order to upgrade to the latest OS release. If you get one for Panther (10.3) or Tiger (10.4), startup from it by holding down the C key. When you get to the first Installer screen, go to the Apple menu and select +About This Mac+. That will tell you processor type, processor speed, and amount of RAM installed.
Make sure it's a retail disc. They are black with a silver X. Mac OS X installation discs that came with a particular Mac model (usually gray color) will usually not work on other models.
The current OS release, Leopard (10.5), would not be a good choice for this purpose because many G4 and below Macs cannot run it.
Tiger will work on all PowerPC Macs that originally had a G4 and have at least 256mb of RAM. It will also work on slot-loader G3 iMac (not tray-loaders), Blue and White Power Mac G3 (not beige), PowerBook G3 (only the model with FireWire) - not earlier G3 models.
Panther will work on all PowerPC Macs that originally had a G4 and most G3's that have at least 128mb of RAM, so it may be the best choice for this purpose.
There are some G3 Macs that need to have a firmware upgrade before running Mac OS X (even the installer) for the first time. This is particularly harmful to slot-loading G3 iMacs.
http://support.apple.com/kb/HT1395
If most of the Macs have a FireWire port, and you have an external FireWire drive, you should install either Panther or Tiger on that drive. Then you can boot each Mac from that external FireWire drive and run System Profiler to get more detailed information about the system. Mac OS X installations are generalized, so as long as a PowerPC Mac ran the installation, it should work with supported PowerPC Macs. Some Macs do not have FireWire. USB external drives are not bootable on most PowerPC Macs.

SCSI Scanner on PowerMac G5 with Leopard

Hi all,
I have an old high-end SCSI scanner (AgfaScan XY-15) that I would like to use with my PowerMac G5 and OSX 10.5.8. In the past, I used a G4 MDD that could dual-boot OS 9 and OS X 10.3. The G4 had an Adapted card (29160 IIRC), the G5 an Atto (UL5D).
To have the scanner work with OS X 10.3, I had to replace IOSCSIArchitectureModelFamily.kext and IOSCSIParallelFamily.kext (in /System/Library/Extensions) by their OS X 10.2 versions (something Agfa recommended for their mid-range scanner, on a page that can now only be found in archives : http://web.archive.org/web/20050306100359/http://www.agfa.com/digicam_scanner_dr ivers/faq/#faq22a)
On Leopard, I can see the scanner in the ATTO configuration tool, but the scanner sofware always outputs a "scanner not found" error. This scanner cannot be used with VueScan, so the solution suggested on Using SCSI Scanner with 10.5 possible? is not applicable.
I have tried changing parameters (for instance disabling LUNs for ID 4 - the scanner - as shown below, which results in the scanner only appearing once in the list of devices), but I cannot seem to find the good combination of parameters.
Does someone with experience in SCSI scanners have some tips?
Thanks in advance for the help!

The last device on the chain must have termination turned on. If it is, then I don't know what to say other than to try some of the other scanner drivers on my subscription site*:
http://www.macmaps.com/macosxnative.html
* Links to some of my pages may give me compensation.

FCP 5 and Leopard Help

Hi I am currently running OS X 10.4.11 on a PowerMac G5 and I have been considering upgrading to Leopard. I notice on some website that to be able to use FCP 5 in Leopard I must be on version 5.1.4. Now I have been on 5.0.4 for ages now and it still says I am up to date. Is this a mistake or when I upgrade operating systems it will, if you will 'unlock' this update? any info I will greatly appreciate

5.1.x was only released as part of a paid upgrade of Final Cut Studio 1 to make it Universal Binary i.e. Intel compatible. Owners of FCS 1 could also return the original disks and upgrade for a nominal fee, for a short time. This offer has long since been discontinued.

IMac (Late 2006) Stalls with EFI 1.2 and Leopard

A few days ago, I installed both the iMac 1.2 EFI Firmware update and Leopard on my late 2006 20" iMac. Since then, I've seen random momentary stalls throughout the system.
It sometimes happens while scrolling a web page, displaying a sheet, opening a stack, browsing CoverFlow, and so on. I don't know how to intentionally recreate it, it just seems to happen. It often (always?) seems to coincide with some disk activity.
I don't remember this behavior on the same hardware in the past, so either it's something with the firmware update or Leopard. Has anyone seen anything else like this?
Thanks in advance.

Some people reported various bugs after installing the firmware update. Shutting it off and turning it back was all that was needed to fix the bugs.

Endnote X1 and Leopard

Has anyone tried using Endnote X1 and Leopard? I can't open any files ("the document blabla couldn't be opened"), nor can I create a new library ("Failed to create library").
Anyone any ideas if this is fixable?

Fixed the problem. Originally I had no problems keeping the Endnote files wherever I liked, however it now only works with the Endnote files in Users/Library. A bit weird, but I can live with it.

Can I run Tiger and Leopard on the same computer

Hi folks.
I've been meaning to install Leopard for ages but have never got round to it (I bought the retail box when it first came out). I have upgraded my RAM to 2GB and my hard drive to 320GB with no problems.
My upgraded hard drive has been partitioned into 2 equal parts of 160GB. These appear on desktop as Mackintosh HD1 and HD2. HD1 is the disk with all my files, music, OS etc and HD2 is empty
I have 2 bootable clones of my present system - one is on a 160GB external and the other is the original 80GB HD that I replaced.
My question is this - can I install Leopard on to my 160GB external HD, then clone it on to the empty HD2. If I do this would I be able to run both Tiger and Leopard on the same Macbook?
Is there any problems with this plan? Would I be able to transfer between the 2 OS and how do I install Leopard on the external drive. Is it just a case of inserting the Leopard DVD and choose the external drive as the target?
As usual thanks in advance
Del

# Original Tiger in the internal HD, New Leopard in the external HD.
# New Leopard in the internal, Legacy cloned Tiger in the external.
# Split internal, one partition with Tiger, another with Leopard.
Leopard is backwardly compatible with older Macs, just make sure yours fulfills the minimum system requirements, both use the same filesystem format, so each can see the other. You can't run both at the same time, unless you purchase the server version of Leopard and run it virtualized. 99.9% of Firewire external HD's are bootable, some USB's are bootable but have to test first. You can choose which system to boot from by pressing the Option key at boot time, before the chime. Just make sure the external HDD is plugged in and turned on if that's where you want to boot from.
When I migrated my PBG4 from Panther to Tiger, got an external FW HDD, cloned Panther onto it, upgraded using Archive and Install, cleaned up, customized and tested it. When I was satisfied all was ok, cloned the original Panther onto another partition of the external HDD, wiped and tested for failure the internal HDD, then cloned the known good and tested Tiger into it. Only thing that died along the way was my old and ancient Photoshop v2.x, that refused to run on Tiger.

1st generation MacBook, battery and Leopard issues; looking for help please

I have a 1st generation MacBook that started having battery problems immediately after installing Leopard. it was the same issue many others have complained about; battery life shortened and shutting down while on battery power with no warning. I have never had that problem while using Tiger. I experienced this with both 10.5.0 and the stand alone upgrade of 10.5.1 using an erase and install method.
(BTW, as a side note: I'm religious about calibrating my battery every month and use a program called "CoconutBattery" to document the results. Prior to Leopard, the battery measured 97-99% capacity. Three days after Leopard was installed it was time for another check, the result was 74% capacity.)
I had a clone backup of Tiger and immediately restored my MacBook, but the problem followed Tiger. I have Applecare and called support. Both myself and the tech found it rather hard to believe that the battery just suddenly failed coincidentally after the Leopard install. We went through the regular things; SMC reset, firmware checks, diagnostics, repair permissions, etc.
We believe it has to do with the Battery Updater package. I had gone between both versions of 1.2 and 1.3, but the problem remained with both Tiger and Leopard. The tech decided to send me a new battery (it's on the way) and I wish to try installing Leopard again. As long as I have my cloned Tiger image, all I have to lose is my time, but hopefully, not another battery! I would honestly like to get Leopard running on this machine.
But... here's my question. In reading through these discussions in both the Leopard and MacBook forum, there doesn't seem to be any consensus of which BatteryUpdater package to use. The Apple tech honestly told me he didn't know. Also, if the BU package "writes" to the battery (which it states it does), can it be downgraded once v1.3 has been installed? I mean, should I leave the battery out, install Leopard, then manually update BU to v1.2 before installing the battery (if possible)? I do plan on testing the new battery with my Tiger install, just to verify it is working as it was before.
There are a lot of people here claiming to be knowledgeable about Leopard, never had any problems with a variety of machines, etc, etc, so I would appreciate your input. Please don't speculate, but if you're using a version of BU that works with Leopard and your 1st Gen MacBook, I would appreciate you telling me about it. I have tried to document and methodically relate everything I've done so far, but if you need additional information, just let me know.
I noticed Leopard had installed BU v1.3 when I checked it, so it must use that as default, since I noticed Tiger had v1.2.
OR, am I way off base on this? Can anyone think of another reason I may have had this problem? Am I barking up the wrong tree by concentrating on the BatteryUpdater package? Is it possible all these batteries are failing under a Leopard install maybe due to some unknown reason?
Any knowledgeable advice or suggestions are welcome, thanks!

Well, Ding Dang y'all... it appears the battery was the culprit. I received my replacement battery from Apple and followed the same steps and everything seems to be working fine.
It sure was strange that the battery started this problem immediately after Leopard was installed... I don't know what to say about that, unless BatteryUpdater v1.3 started the chain of events.
In case it helps someone else, here's exactly what I did (rebooted through each step):
- Backed up data; unauthorized computer from iTunes
- Erase and install from the Leopard disc, while keeping the old battery in
- Installed Leopard, did software updates except for delta 10.5.1 update
- Applied combo update of 10.5.1 from separately downloaded file
- Found BatteryUpdater Bundle (BU) of v1.3, moved to trash, rebooted
- Ran software updates, BU v1.2 was found and installed
- Then, swapped out battery to new battery
- Tested unit, seems to be okay now, no shutdown issues, battery runtime seems normal
Thanks to all that had advice and suggestions. It was enough to get me to try it again. Now, I have two more machines to upgrade, since these are production machines, I'll probably wait awhile. But, having this is a real treat.
Have a great holiday everyone!

G4 and Leopard

Now, according to Apple, 10.5 with be totally 64-bit, which, I suspect will be a problem with G4 users as this PPC processor is a 32-bit processor (and not 64-bit).
I was wondering what Apple will be doing about this ? With G4 users just have to 'make do' with just a 32-bit version or with 64-bit be emulated in some way ?
Or am I wrong in assuming the G4 isn't a 64-bit processor ?

As I understand it the Unix under-pinnings of OS X were 64-bit in Tiger. 64-bit applications could be used, but only from the command line/terminal application/Unix shell. With Leopard 64-bit support has simply been extended upwards to include certain development frameworks such as Cocoa, allowing 64-bit applications to be used from the Mac GUI with the usual Mac OS look and feel.
As a G4 user I don't think anything will change between Tiger and Leopard. 64-bit support will now be included from top to bottom, but not at the expense of 32-bit support. In a sense we have to 'make do' anyway due to the hardware limitations. For example, one of the advantages of a 64-bit processor and OS is that more memory can be addressed. However, the G4s have a maximum of 4 DIMM slots with 512MB per DIMM, so we're limited to 2GB of memory at the hardware level anyway even if the OS does support more. IMHO, unless you're using specialised applications or need to be able to address huge amounts of memory (for example if you're working with huge image files), 32-bit is fine. If this isn't the case, you should probably be using a G5 or Mac Pro anyway.

Droplet Script used to work fine in Tiger and Leopard, now doesn't

Hey everyone,
I'd like to apologize in advance, I'm not really good with AppleScript and was only able to create my droplet in the first place by changing little bits of a Droplet example script I found on the internet (I forgot where I found it, but it might even have been here at Apple).
The script worked perfectly fine in Tiger and Leopard but throws an error in Snow Leopard. The error says "Can't make alias "...filepath... "into type file."
The problem is that I can't find the problem in my script. I don't get any indication which line it may be and I hope someone here will be able to help me.
I also tried Script Debugger, but the script works there! So that doesn't help either...
I'd appreciate any help, here is the script:
-- QuickTime supported image formats
property type_list : {"JPEG", "TIFF", "PNGf", "8BPS", "BMPf", "GIFf", "PDF ", "PICT"}
property extension_list : {"jpg", "jpeg", "tif", "tiff", "png", "psd", "bmp", "gif", "jp2", "pdf", "pict", "pct", "sgi", "tga"}
property typeIDs_list : {"public.jpeg", "public.tiff", "public.png", "com.adobe.photoshop-image", "com.microsoft.bmp", "com.compuserve.gif", "public.jpeg-2000", "com.adobe.pdf", "com.apple.pict", "com.sgi.sgi-image", "com.truevision.tga-image"}
-- This droplet processes files dropped onto the applet
on open these_items
repeat with i from 1 to the count of these_items
set this_item to item i of these_items
set the item_info to info for this_item
try
set this_extension to the name extension of item_info
on error
set this_extension to ""
end try
try
set this_filetype to the file type of item_info
on error
set this_filetype to ""
end try
try
set this_typeID to the type identifier of item_info
on error
set this_typeID to ""
end try
if (folder of the item_info is false) and (alias of the item_info is false) and ((this_filetype is in the type_list) or (this_extension is in the extension_list) or (this_typeID is in typeIDs_list)) then
processitem(thisitem)
end if
end repeat
end open
-- this sub-routine processes files
on processitem(thisfile)
-- NOTE that the variable this_item is a file reference in alias format
-- FILE PROCESSING STATEMENTS GOES HERE
tell application "Image Events"
launch
-- get the parent folder of the image file
set the parent_folder to the container of this_file
-- derive new name for the new image file
set the new_name to my addextension(thisfile, "png")
-- look for an existing file
if (exists file new_name of the parent_folder) then
error "A file named \"" & new_name & "\" already exists."
end if
-- open the image file
set this_image to open this_file
-- save in new file. The result is a file ref to the new file
set the new_image to save this_image as PNG in file new_name of the parent_folder with icon
-- purge the open image data
close this_image
end tell
end process_item
on addextension(thisfile, new_extension)
set this_info to the info for this_file
set this_name to the name of this_info
set this_extension to the name extension of this_info
if this_extension is missing value then
set the default_name to this_name
else
set the default_name to text 1 thru -((length of this_extension) + 2) of this_name
end if
return (the default_name & "." & the new_extension)
end add_extension

Here's the faulty line:
--open the image file
*set this_image to open this_file*
The command open doesn't return anything that could be assigned to the variable this_image.
I also wonder if it wouldn't be better to add “as alias” at the end of each of the following two lines:
*set this_info to the info for this_file*
*set the item_info to info for this_item*
I hope this help.

MacMini and Leopard

Well!
I recently bought a MacMini because the motherboard on my eMac allegedly croaked. The replacement cost wasn't much more than a new mini so I figured, "what the heck." Then, I upgraded to Mac OS 10.5 the day after it became available.
Since installing Mac's new Leopard, I am no longer able to use my Canon 8400F Scanner or CanoScan scanning software, Photoshop Elements, Alsoft Diskwarrior, Lacie SilverKeeper and IMSI TurboCad. The menu bar and title bars in Safari display vertical lines that make text illegible and, worse yet, Apple Mail randomly stops downloading some of my mail from Road Runner. Yep, it stumped Road Runner, too.
You know, I wish they had a method for more thorough testing at the store level, because I am not convinced there was anything wrong with that eMac motherboard. With all the software I'm going to have to repurchase, I'm thinking about taking the eMac off the junk shelf and setting it up on my desk, again. I'm almost certain, at this rate, that there won't be much difference in productivity.
Now, let's see: I'm on Social Security. I don't make a lot of bread, but I feel certain that I can set aside a small amount each month to upgrade my software before the Social Security System goes belly up . . . . maybe.
For the present, however, can someone out there please tell me how to uninstall Mac OS 10.5 and downgrade to Max OS 10.4 without making a bigger mess than I am in right now.
Thank you.

Well, Da Brew,
Unfortunately, now that a higher version of Mac OS X is installed, the only way to downgrade is to *Erase & Install*.
You'll have to back up all your data, but this is not a problem as you already do that anyway.
_Running both Tiger and Leopard on your Mini:_
Since you're erasing everything, why not split your internal HD into two partitions,
install Tiger on Volume 1 and Leopard on Volume 2?
Use the Tiger DVD to partition HD (menu Utilities > Disk Utility),
then install Tiger,
then install Leopard later on Volume 2.
Good luck!
Axel

Pro Tools and Leopard

Just wanted to know if anyone had heard any information about Digidesign patching up Pro Tools to work with Leopard.
I really hope they do it soon...

I just got this info from Digidesign on LE and Leopard.
Hello Everyone,
I'm Dave Lebolt, general manager of Digidesign. I wanted to take a moment to talk to you about what is happening with Mac OS X Leopard and support in Pro Tools. Some of you have commented that getting Leopard qualified far earlier than now would seem like a "no-brainer," or that Digidesign is often far too late in coming on line in support of newer OS versions. Some have hypothesized that we will charge for an upgrade just to offer you Leopard support. Some people have even said that it's possible that Apple may be causing problems for Pro Tools on purpose. And some folks have said all of these things at once!
The first thing I want to say to all of you is: I'm sorry. I'm sorry that getting here is taking so long and that we have not been able to communicate more about it, and also because we really do care about your experience as customers... People working here are passionate about Pro Tools, a lot of us here want to use our product with Leopard too, and most of all we care because we genuinely want to do anything we can to help you be creative and successful in what you do. So I'm sorry if we're letting you down by not getting things released sooner.
Lack of Leopard support across our product line affects many of you (and affects our business), so I wanted to give you some insight into what's been happening and where we are in the process. Some quick answers to the above statements:
* We have an excellent working relationship with Apple. I have regular communications with senior folks there, as do many others in our organization with their peers (especially engineering and test). The people I talk to at Apple want Pro Tools to be compatible as much as we do; they know that a lot of you are our mutual customers. Ultimately, Apple considers Digidesign to be an important developer on the platform.
* Rest assured, we will not charge Pro Tools 7.4 owners for an update to support OS X Leopard. In fact, it is not our policy (nor has it ever been) to charge for a "dot release" where the only change is support for a new OS version.
* We'd love to have the new Leopard compatible version out to all of you, and it's very painful not to have it for everyone right now. We start work on the qualification (and development process as required) early in the cycle. We begin work on the "seed" versions of the operating system as soon as they are available and sometimes things are changing even as the initial OS release goes to market. If anything changes after that (i.e., a dot release), we sometimes have to start over in addressing any problems that may be newly introduced and go through entirely new rounds of testing to ensure quality.
What's The Current Status?
We have been working hard on supporting OS X Leopard since its introduction to developers at WWDC in 2006 for many months (including some period of time prior to Leopard's release). As is often the case with entirely new major OS versions, there were some quick "dot" releases after introduction. Many of the problems that Apple addressed in these dot releases were critical to improve OS X Leopard operations (you can read about some of them on the support section of Apple's website). These improvements and fixes were very valuable to a broad base of Mac users. Unfortunately, the currently shipping OS X Leopard release, 10.5.2, contains some changes that actually caused problems with Pro Tools (and some other apps as well). In our case, the problems included audio interfaces not being recognized by the computer, track counts dropping to near zero, and errors coming up during normal operation. Some of you who may have experimented with Pro Tools and OS X Leopard 10.5.2 may have encountered some of these problems.
We have worked closely with Apple's engineering group, who have been working very hard in cooperation with us to get the problems ironed out. The good news is that we're getting close to the home stretch, but we have to do a lot of testing of the fixes that have been implemented in order to be sure that we're in good shape. We need to make sure that our product works well and you're not just getting something that's marginal, and it takes time to exercise all of the newly changed code.
What Works on Leopard? Anything At All?
Currently, only Pro Tools|HD systems running Pro Tools 7.4.1 software are officially qualified with OS X Leopard 10.5.1 running on the new generation Mac Pro 8 core desktop machines (with "Harpertown" processors). This means no support yet for Pro Tools LE and M-Powered, and it means that users of the new Mac Pros need to stick with OS X 10.5.1 for the time being.
Why this Message?
We have posted this information along the way (just a couple of weeks ago our head of customer service posted information to the DUC), but the amount of time that is passing combined with our concern within the company prompted me to want to reach out to all of you. We work cooperatively with Apple, and want to respect the process that we have in place for fixing problems; but I wanted to give you a bit more information about what's been happening and why we're not there yet...
When Will It Ship?
We hope to have the new release within between 1 and 2 months from now; some of that timetable is contingent on Apple. We'll keep you posted as we get closer. Normally, we don't want to give specific dates because that can cause problems in expectation and it's better not to have negative surprises, but I'd like to share this info with you in the spirit of keeping closer to you as our customers.
I hope that my note gives you a better idea of what's been going on — thanks for listening.
- Dave L.

"Moving" Tiger and Leopard OS's from G4 (32b) to G5 (64b)

I plan to image Tiger (10.4) and Leopard (10.5) from my Power Mac G4 (Quicksilver 2002) to a recently acquired a Power Mac G5 (Early 2005). My questions are:
1. Tiger and Leopard were installed on a G4, a 32 bit processor, but the G5 is a 64 bit processor. Do I need to do anything after I’ve “installed” the G4 Tiger and Leopard on the G5 to have them function as 64 bit Operating Systems (a.they can detect which processor they are installed on automagically and don’t need my intervention OR b.I have to toggle something OR c.I have to reinstall one/both of the Operating Systems on the G5 for them to function as 64 bit Operating Systems)?
2. How can I tell if the OS is running as a 32 bit or 64 bit process?
TIA.

Hi Barubin,
I'm no expert on OS X's internals, but I believe Tiger and Leopard's kernel still is 32-Bit, but allows 32-64-bit bridging. In Leopard's Activity Monitor I can only find two apps running in 64-Bit mode:
usbmuxd
IIDCAssistant
The best way of getting 64-Bit is to upgrade to Snow Leopard on Intel, I'm afraid.
Your target-disk method or BDAqua's suggestions should work just fine, but I usually find hdiutil to be generally more reliable, plus I can keep around a system image for safety's sake. When I say reliable, I mean that you can always interrupt the image creation by using CTRL-C or check whether it is actually throwing any errors. The GUI has hung on me on occasions. I also love UNIX, which helps!
I've never done a speed comparison between Disk Utility and its CLI counterparts, but I like the verbosity/flexibility provided by the CLI. It's a matter of taste, really. If you're not comfortable using the CLI, stick to the other options.
The purpose of asr -imagescan (asr stands for Apple Software Restore), is to rebuild the target image and replace it with a checksummed and reordered (optimised) version, so it can then be verified against the contents of your target volume after you're restored the data. Also, scanning the image allows you to do a block restore, which is effectively a blazingly fast blind copy. In a matter of minutes you can easily restore 15 GB of data into your chosen volume, as opposed to not scanning it with asr or Disk Utility and the restore operation defaulting to a normal image mount --> data copy operation, which is slow and inefficient. It's a tradeoff really. You can wait for ages restoring, or creating the image
I rather wait for image creation since it's the safest and cleanest option data-wise.
Check out:
$ man asr
$ man hdiutil
I'm confident it will all work just fine with your heart transplant!
Cheers

Info regarding Diswarrior 4 and Leopard compatibility

I emailed Alsoft regarding Diskwarrior 4 and Leopard compatibility. Here is the response I got.
+DiskWarrior 4.0 will successfully rebuild a disk that has Mac OS X 10.5+
+Leopard installed or a disk that has been attached to a computer running+
Leopard.
+However, some operating system functionality has changed within Leopard+
+itself. As such, there are some compatibility issues when running an+
+installed copy of DiskWarrior 4.0 while started up from Mac OS X 10.5+
+Leopard. Alsoft currently recommends that you do not run DiskWarrior 4.0+
+while the computer is started from Mac OS X 10.5 Leopard.+
+Instead, to run DiskWarrior, you should start up the computer from either:+
+1) A DiskWarrior 4.0 CD.+
+2) Any disk that starts up in 10.4.x and then run DiskWarrior 4.0.+
+An updated version of DiskWarrior that has complete Leopard+
+compatibility will be released soon as a free download for existing+
+owners of DiskWarrior 4.0.+
+-- What you can expect when running DiskWarrior 4.0 under Mac OS X+
+10.4.x and rebuilding a Leopard disk.+
+All features work as expected with one exception: FileVaults created+
+while started from Leopard are not visible to DiskWarrior 4.0 and cannot+
+be rebuilt (repaired).+
+-- What you can expect when running DiskWarrior 4.0 under Mac OS X 10.5+
+and rebuilding a Leopard disk.+
+While not recommended (and discouraged), if you do run DiskWarrior 4.0+
+while started from Mac OS X 10.5 you might encounter some problems such as:+
+1) There is a lengthy delay whenever DiskWarrior is determining which+
+drives are currently attached. This delay is dependent upon the number+
+of attached drives and may last up to 2 or 3 minutes. You will+
+experience this delay when first starting DiskWarrior, whenever a disk+
+is attached or detached while DiskWarrior is running but idle, and+
+whenever a rebuild is completed or canceled.+
+2) You cannot rebuild FileVaults or disk images.+
+3) In step 9 (comparing directories) of a rebuild, the progress bar+
+might get to 100% even though the comparison step is not finished.+
+4) When performing Check All Files and Folders the progress bar might+
+get to 100% even though the check is not finished.+
+5) After rebuilding a disk, DiskWarrior may report that some files or+
+folders have had their permissions changed. This is inaccurate and the+
+permissions have not been changed.+
+To repeat, an updated version of DiskWarrior that has complete Leopard+
+compatibility will be released soon as a free download for existing+
+owners of DiskWarrior 4.0.+
+-- What about DiskWarrior 3?+
+DiskWarrior 3 and earlier versions are not compatible with Mac OS X 10.5+
+(Leopard). Alsoft does not recommend running DiskWarrior 3 or earlier on+
+a disk that has Mac OS X 10.5 Leopard installed or a disk that has been+
+attached to a computer running Leopard.+
+-- Marc+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Marc Moorash, Alsoft Technical Support+
+Email: [email protected]+
So, it seems it will work but you need to run it from the disk or if you have it installed on a external drive running Tiger, it will work.
Thom

If you open your Tiger Address Book, select all cards, drag them to the desktop, it will make one big "mega-VCF" card with a name like "Alan Adams and 543 others.vcf" Dump that to a flash drive or email it to yourself, then doubleclick on it on the Leopard machine. They will all import just fine into your Leopard Address Book.
Try doing something similar with your iCal data, Open the application, choose your calendars one at a time, and select File > Export. That should make a big "mega-ics" calendar card with a name like "work.ics" or "home.ics, i.e., "originalcalendarname.ics" with all the events of that calendar. Then same drill: dump that to a flash drive or email it to yourself, then doubleclick on it on the Leopard machine.
Both generation methods create text files, which should import just fine into the Leopard applications.

I purchased a powermac pro and it came with logic Pro 9 (but with out the additional suite of programs that comes with). How can I reregister or reinstall Logic Pro 9 to get those features?

I could really use some insight into this please also how many gigs of RAM should my power mac have it only has two right now and logic tends to glitch up majorly.

My original question :
I purchased a powermac pro and it came with logic Pro 9 (but with out the additional suite of programs that comes with). How can I reregister or reinstall Logic Pro 9 to get those features?

PowerMac G4 and Leopard?

Similar Messages

Maybe you are looking for