Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Installing Snow Leopard (and Rosetta) into Parallels on modern Intel Macs
- Thread starter MichaelLAX
- Start date
- Sort by reaction score
Thanks for the suggestions. Unfortunately, Graphics Converter isn't even remotely in the same league as Canvas (for starters it's bitmap only). Also, regarding Word, you're right - I probably did do these things in Classic. I'll definitely check out SheepShaver.
While I have not yet upgraded to Parallels 8, others here have successfully and reported it now supports the "cut and paste" across the virtual environment issue in Mac OS X that was not supported in earlier versions.
Yes (sort of). I did everything on a Lion machine and Parallels 7, and then transferred it to a Mountain Lion machine running Parallels 8 and that worked. Obviously you'll have to reinstall Parallels Tools.
Canvas left the Mac platform many years ago, leaving many stranded users with pretty much nothing equivalent to move to, other than a Windows machine. Here is a link to the latest Windows version:
http://www.acdsee.com/en/products/canvas-14
It has genuinely been a source of frustration for me that I still can't find a good substitute. Sigh.
Since you already have Parallels, why not install Windows and run Canvass there? Are the data files cross platform?
PS: I forget which Mac you have, but you can boot into Snow Leopard, then you can install Windows XP into Bootcamp and then access it from Parallels. Even on a newer Mac Parallels can install and run XP, just not from Bootcamp. XP is available on eBay very inexpensively.
Other frustrated Mac Canvas users...
PS: I forget which Mac you have, but you can boot into Snow Leopard, then you can install Windows XP into Bootcamp and then access it from Parallels. Even on a newer Mac Parallels can install and run XP, just not from Bootcamp. XP is available on eBay very inexpensively.
Other frustrated Mac Canvas users...
Last edited:
So now that everything is up and running it would seem I have lots of questions 
.
For the life of me, I can't figure out how to set files *.cvx files (for Canvas) in my Mountain Lion world to automatically open with the Canvas program in my SL virtual machine. I can certainly do such things for my Windows VM because Parallels created a ~/Applications Parallels/VM_name Applications directory that I could navigate to in the Open With section of a Get Info box.
Any ideas here?
. For the life of me, I can't figure out how to set files *.cvx files (for Canvas) in my Mountain Lion world to automatically open with the Canvas program in my SL virtual machine. I can certainly do such things for my Windows VM because Parallels created a ~/Applications Parallels/VM_name Applications directory that I could navigate to in the Open With section of a Get Info box.
Any ideas here?
Did you install Parallels Tools?
However, I do not think that cross-linking of files to applications across environments is supported in Mac OS X in Parallels.
All this means is that you must manually open your Snow Leopard environment and if you double click your Canvas data files there, they should open in Canvas.
As noted in my Cautionary Notes: be sure to keep ALL of your data files outside of the virtualized environment and just access, modify and save them from within Snow Leopard.
However, I do not think that cross-linking of files to applications across environments is supported in Mac OS X in Parallels.
All this means is that you must manually open your Snow Leopard environment and if you double click your Canvas data files there, they should open in Canvas.
As noted in my Cautionary Notes: be sure to keep ALL of your data files outside of the virtualized environment and just access, modify and save them from within Snow Leopard.
Snow Leopard on Mountain Lion
Hi Michael, I followed links here from Apple Support Communities/Why can't I use Word with Mountain Lion?
I think Parallel will help me. I just need to access my MSWord2004 and CS2 and a couple of other small programs. Your instructions look very concise. Thanks for putting them together. I'm not very techie. As far as systems and installations, I struggle through what I need to get done by trial and error. Hopefully not too many errors.
Before I purchase Parallel I want to be sure it will work on my set up. My MacBook Pro is from 2007 and I think Mountain Lion might be the last OS up grade it will be able to take. I like ML a lot, other than not supporting PPC programs. I guess a lot of people got caught up in that.
Would PD7 work or should I get PD8? I think you said in this thread that you haven't tired PD8 yet? I wasn't able to read all the discussion, I can't understand it all anyway. I didn't even know about Rosetta and PPC programs until after I updated to Mountain Lion.
I have a DVD of Snow Leopard 10.6.3 which I installed on my computer two yeas ago, I have another DVD of the same thing (which I bought to install on my mom's MacBook but she doesn't have a DVD drive). I upgraded to 10.6.11 last year but I think I did that online. I up graded to 10.8.1 last week on line.
I'm going to go through the thread, too.
Thanks
Hi Michael, I followed links here from Apple Support Communities/Why can't I use Word with Mountain Lion?
I think Parallel will help me. I just need to access my MSWord2004 and CS2 and a couple of other small programs. Your instructions look very concise. Thanks for putting them together. I'm not very techie. As far as systems and installations, I struggle through what I need to get done by trial and error. Hopefully not too many errors.
Before I purchase Parallel I want to be sure it will work on my set up. My MacBook Pro is from 2007 and I think Mountain Lion might be the last OS up grade it will be able to take. I like ML a lot, other than not supporting PPC programs. I guess a lot of people got caught up in that.
Would PD7 work or should I get PD8? I think you said in this thread that you haven't tired PD8 yet? I wasn't able to read all the discussion, I can't understand it all anyway. I didn't even know about Rosetta and PPC programs until after I updated to Mountain Lion.
I have a DVD of Snow Leopard 10.6.3 which I installed on my computer two yeas ago, I have another DVD of the same thing (which I bought to install on my mom's MacBook but she doesn't have a DVD drive). I upgraded to 10.6.11 last year but I think I did that online. I up graded to 10.8.1 last week on line.
I'm going to go through the thread, too.
Thanks
Chris:
Happy to help:
Here is the link to download the 14 day trial version of Parallels 8. Do not activate the trial version until you are ready to use Parallels, so you will get the full 14 days use.
Although I have not yet upgraded to 8 myself, I am confident from posters here that it will work the same as 7 and actually be better in that it can now support cut & paste from Mountain Lion to Snow Leopard and back.
If you find that these instructions are too daunting for you, you can send me your Snow Leopard Install DVD and a 16 Gig Flash Drive and I will do the installation and send it back to you.
Or, I can help you along in the process.
NOTE: There is a problem with STEP ONE and you need access to a Mac with Snow Leopard or Lion to complete this step and then move the modified Snow Leopard Install file over to your Mountain Lion Mac to complete the remainder of the steps.
This thread is very long and all you really need to know is in posts #1 and #3: Cautionary Notes.
Also, you may want to invest in some more RAM: what do you have now?
Let me know how I can proceed to help you out!
Happy to help:
Here is the link to download the 14 day trial version of Parallels 8. Do not activate the trial version until you are ready to use Parallels, so you will get the full 14 days use.
Although I have not yet upgraded to 8 myself, I am confident from posters here that it will work the same as 7 and actually be better in that it can now support cut & paste from Mountain Lion to Snow Leopard and back.
If you find that these instructions are too daunting for you, you can send me your Snow Leopard Install DVD and a 16 Gig Flash Drive and I will do the installation and send it back to you.
Or, I can help you along in the process.
NOTE: There is a problem with STEP ONE and you need access to a Mac with Snow Leopard or Lion to complete this step and then move the modified Snow Leopard Install file over to your Mountain Lion Mac to complete the remainder of the steps.
This thread is very long and all you really need to know is in posts #1 and #3: Cautionary Notes.
Also, you may want to invest in some more RAM: what do you have now?
Let me know how I can proceed to help you out!
Last edited:
Also, you may want to invest in some more RAM: what do you have now?
Michael, About this Mac says: Memory 4 GB 667 MHz DDR2 SDRAM
I have a friend who said this: I believe we can partition your hard drive into two drives and make one Lion and the other Snow Leopard. However, you will have to back up your stuff often because you will essentially halve the drive space and double the operating system space on your laptop.
I didn't want to partition my HD, I think Parallels is a better fit for my needs. Her HD is partitioned and she has Lion on it. I will ask her if she can help with the installation, otherwise I'll take your offer.
Thanks
Michael, About this Mac says: Memory 4 GB 667 MHz DDR2 SDRAM
I have a friend who said this: I believe we can partition your hard drive into two drives and make one Lion and the other Snow Leopard. However, you will have to back up your stuff often because you will essentially halve the drive space and double the operating system space on your laptop.
I didn't want to partition my HD, I think Parallels is a better fit for my needs. Her HD is partitioned and she has Lion on it. I will ask her if she can help with the installation, otherwise I'll take your offer.
Thanks
My Parallels running on my 2011 Mac Mini with 8GB RAM (with 2G allocated to Parallels) runs much faster than my 2009 MacBookPro with 4GB RAM with 1G allocated to Parallels, so if you can, I suggest you upgrade your RAM AFTER you have installed Parallels and are happy with the way it works otherwise.
The HD Partition "dual-boot" method is another workaround (for those older Macs that will boot Snow Leopard). I personally like the idea of being able to concurrently have both environments available to me at the same time, so I went with Parallels. The same is true of having access to Windows XP through Parallels instead of having to reboot into Bootcamp, in the few instances that I need it.
Always available to help: let me know!
The HD Partition "dual-boot" method is another workaround (for those older Macs that will boot Snow Leopard). I personally like the idea of being able to concurrently have both environments available to me at the same time, so I went with Parallels. The same is true of having access to Windows XP through Parallels instead of having to reboot into Bootcamp, in the few instances that I need it.
Always available to help: let me know!
I'm a little confused. While I was downloading the dmg for the trial version of PD8 my friend emailed me saying that Parallels partitions your HD. She's used it on a Mac with Windows. I'm still deciding what to do.
If I was to get a Mac Mini, could I reinstall Snow Leopard back on my MacBook Pro? Or can you not go back.
If I was to get a Mac Mini, could I reinstall Snow Leopard back on my MacBook Pro? Or can you not go back.
Last edited:
Your friend is confused.
She probably used the Apple supplied Bootcamp to partition her HD and install Windows into it. This allows any Intel Mac to "dual-boot" into Windows, but not run Windows concurrently with Mac OS X.
However, installing and using Parallels not only allows it to access your Bootcamp partition for its Windows files (and hence not duplicating them and wasting valuable hard disk space), but runs Windows and Mac OS X concurrently.
The same is true for using Parallels to run Mac OS X Snow Leopard; except there is no need for Bootcamp. Bootcamp is ONLY for Windows.
Hence, you can use the 14 day trial version of Parallels without any fear that it will partition your hard disk.
If you continue on with these Snow Leopard installation instructions, the final result will be the creation of a file in your Documents folder in your User Folder which will be named Mac OS X Snow Leopard.pvm. It will be approximately 15Gigs large and will contain all of the Snow Leopard files (and Parallels files) that Parallels needs to run Snow Leopard in virtualization.
As to your last question, you can go back: do you have a Time Machine backup from before you upgraded to Mountain Lion? If not, you may have to wipe and start from scratch! Be careful, I am not the expert in "going back!"
If you are still online and want to iChat, I am MichaelLAX
She probably used the Apple supplied Bootcamp to partition her HD and install Windows into it. This allows any Intel Mac to "dual-boot" into Windows, but not run Windows concurrently with Mac OS X.
However, installing and using Parallels not only allows it to access your Bootcamp partition for its Windows files (and hence not duplicating them and wasting valuable hard disk space), but runs Windows and Mac OS X concurrently.
The same is true for using Parallels to run Mac OS X Snow Leopard; except there is no need for Bootcamp. Bootcamp is ONLY for Windows.
Hence, you can use the 14 day trial version of Parallels without any fear that it will partition your hard disk.
If you continue on with these Snow Leopard installation instructions, the final result will be the creation of a file in your Documents folder in your User Folder which will be named Mac OS X Snow Leopard.pvm. It will be approximately 15Gigs large and will contain all of the Snow Leopard files (and Parallels files) that Parallels needs to run Snow Leopard in virtualization.
As to your last question, you can go back: do you have a Time Machine backup from before you upgraded to Mountain Lion? If not, you may have to wipe and start from scratch! Be careful, I am not the expert in "going back!"
If you are still online and want to iChat, I am MichaelLAX
Last edited:
Keeping data outside the Virtual Macnine is Good Advice.
The suggestion by MichaelLAX to keep your data outside of the virtual machine was recently proven very appropriate. I left my vSL (virtual Snow Leopard) running but had not used it for a day or two. My Mac froze during login from the screen saver and I had to use the power button to restart. Following this, every attempt to start vSL ended with a message from Parallels indicating the OS was not authorized under Parallels and Paralles quit. I had to restore the vSL from a two week old backup. If I had kept data in the virtual machine, I would have lost hours of updates. As it was a restore, quick test and I was on my way.
Thanks again for the great advice.
The suggestion by MichaelLAX to keep your data outside of the virtual machine was recently proven very appropriate. I left my vSL (virtual Snow Leopard) running but had not used it for a day or two. My Mac froze during login from the screen saver and I had to use the power button to restart. Following this, every attempt to start vSL ended with a message from Parallels indicating the OS was not authorized under Parallels and Paralles quit. I had to restore the vSL from a two week old backup. If I had kept data in the virtual machine, I would have lost hours of updates. As it was a restore, quick test and I was on my way.
Thanks again for the great advice.
Hi Michael, I'm glad I don't have to fiddle with a partition. However, you said Parallels with SL would take about 15gig, so I checked my storage. I have 9.67gig free out of 159.18gig.
I do have Time Machine with back up over a year ago. It uses 57.41GB out of 249.72GB on my external HD. I also have access to another ex HD temporarily.
My mother's MacBook has OS 10.4.11, but no DVD drive. I guess I could use the other ex HD to work between the two Macs. Or what would you suggest?
When I get a few hours in a row I'll try it. It won't be this weekend as I'm going camping at Lake Tahoe! Shucks!
I do have Time Machine with back up over a year ago. It uses 57.41GB out of 249.72GB on my external HD. I also have access to another ex HD temporarily.
My mother's MacBook has OS 10.4.11, but no DVD drive. I guess I could use the other ex HD to work between the two Macs. Or what would you suggest?
When I get a few hours in a row I'll try it. It won't be this weekend as I'm going camping at Lake Tahoe! Shucks!
Chris: Actually the partition will grow from 15Gigs as you install your PowerPC applications into it, too.
My advice is that you install the Snow Leopard Parallels file on to an external hard drive. NOTE: in STEP TWO sub step 6, you must change the destination of the file to the attached external hard drive (from its default of ~/Documents/Parallels/).
DO NOT EVER detach the external hard drive while Parallels and Snow Leopard is running.
Are you going to upgrade your Mom's MacBook to Lion or Mountain Lion, too? Is this model capable of the upgrade?
Yes, once put on an external hard drive, you could move it from one Mac to the other, but I have no experience in such usage and it may cause unpredictable results. I recommend that you create two different Snow Leopard.pvm files for each of the Macs (or create one and duplicate it for the other).
Enjoy Tahoe: i'm jealous!
My advice is that you install the Snow Leopard Parallels file on to an external hard drive. NOTE: in STEP TWO sub step 6, you must change the destination of the file to the attached external hard drive (from its default of ~/Documents/Parallels/).
DO NOT EVER detach the external hard drive while Parallels and Snow Leopard is running.
Are you going to upgrade your Mom's MacBook to Lion or Mountain Lion, too? Is this model capable of the upgrade?
Yes, once put on an external hard drive, you could move it from one Mac to the other, but I have no experience in such usage and it may cause unpredictable results. I recommend that you create two different Snow Leopard.pvm files for each of the Macs (or create one and duplicate it for the other).
Enjoy Tahoe: i'm jealous!
I'm having this exact same problem with a retail Leopard DVD on a Mountain Lion MacBook. But then I also went to a Leopard workstation, created a new file and the same problem exists.
I'm not a dunce, though not terribly swift with macs, so any help would be greatly appreciated - doubt that either of my Mac users (they aren't terribly sophisticated themselves) will be willing to move off of Eudora for their email, so I have to at least try and come up with a solution that works.
Last edited:
I have no experience with attempting to install Leopard using this method, although some anecdotal evidence supports that ability.
Will Eudora work on Snow Leopard? There is a thread on this forum that suggests it will work in Snow Leopard
So for less than $30 you can purchase a Snow Leopard Install DVD from Apple (see the telephone numbers listed in STEP ONE of the Installation instructions) and use this method to install Snow Leopard.
NOW: since you are attempting this installation on a Mountain Lion Mac, there is an additional problem. There are two workarounds:
1. Complete STEP ONE on a Snow Leopard or Lion Mac (it may actually work on a Leopard Mac, too), and then move the modified Snow Leopard Install file over to the Mountain Lion Mac and complete the remaining STEPS; or
2. Extract Disk Utility from the Snow Leopard Install DVD and see if that will work in Mountain Lion and use that Utility as needed in STEP ONE.
Let me know how this works out for you and your clients!
Will Eudora work on Snow Leopard? There is a thread on this forum that suggests it will work in Snow Leopard
So for less than $30 you can purchase a Snow Leopard Install DVD from Apple (see the telephone numbers listed in STEP ONE of the Installation instructions) and use this method to install Snow Leopard.
NOW: since you are attempting this installation on a Mountain Lion Mac, there is an additional problem. There are two workarounds:
1. Complete STEP ONE on a Snow Leopard or Lion Mac (it may actually work on a Leopard Mac, too), and then move the modified Snow Leopard Install file over to the Mountain Lion Mac and complete the remaining STEPS; or
2. Extract Disk Utility from the Snow Leopard Install DVD and see if that will work in Mountain Lion and use that Utility as needed in STEP ONE.
Let me know how this works out for you and your clients!
Last edited:
OK, got a SL DVD on the way. Hope that does the trick, but still would kinda like to know why I can't get that done with the Leopard DVD already owned. But if buying SL puts you in a better position to help me out, then I'm all for it.
Incidentally, the price of the SL DVD has gone down - it's now $19.95 plus tax, with free standard shipping. But I chose to pay $6 for two business day shipping. Even then it was only $28 all-in. Next day service was available for $12, but I'm not in that big of a hurry.
I had heard that the price lowered, which is why I said < $30, just to be safe!
Leopard, yeah, well... There are solutions, but I have not focused on them as for my purposes Snow Leopard has always been the better solution!
I am assuming your clients are either older or set in their ways about Eudora. There are some threads about migrating all of the data into the OS X Mail program, but...
If it works, don't fix it! Hahahaha
Anyway, Eudora will apparently work in Snow Leopard, so let me know when you need help again!
Leopard, yeah, well... There are solutions, but I have not focused on them as for my purposes Snow Leopard has always been the better solution!
I am assuming your clients are either older or set in their ways about Eudora. There are some threads about migrating all of the data into the OS X Mail program, but...
If it works, don't fix it! Hahahaha
Anyway, Eudora will apparently work in Snow Leopard, so let me know when you need help again!
Eudora 6.2.4 works with Snow Leopard in Parallels 7
I can report that Eudora 6.2.4 works with virtual Snow Leopard (vSL) in Parallels 7. Not only that, but you need not copy either the Eudora application or the folder ~/Documents/Eudora Folder from its original location. I dragged my Eudora settings file into the vSL dock and everything worked perfectly.
But I can also report that I have migrated all my email files to the latest Mountain Lion Mail app and I'm very pleased with the way it works. It is actually better than Eudora 6.2.4.
You may need Eudora Mailbox Cleaner to help (see http://www.macupdate.com/app/mac/7050/eudora-mailbox-cleaner)
I can report that Eudora 6.2.4 works with virtual Snow Leopard (vSL) in Parallels 7. Not only that, but you need not copy either the Eudora application or the folder ~/Documents/Eudora Folder from its original location. I dragged my Eudora settings file into the vSL dock and everything worked perfectly.
But I can also report that I have migrated all my email files to the latest Mountain Lion Mail app and I'm very pleased with the way it works. It is actually better than Eudora 6.2.4.
You may need Eudora Mailbox Cleaner to help (see http://www.macupdate.com/app/mac/7050/eudora-mailbox-cleaner)
Incorrect virtual start-up disc
I have encountered an issue with the recovery procedure described by MichaelLAX in post #68 on Page 3 of this discussion:
My main virtual Snow Leopard (vSL) machine crashed as can happen and led to the invalid Mac OS version message as described above. I had a recovery system in place, built exactly in accordance with Michael's instructions. But it too failed to boot up and gave the same error. At the time I blamed myself for being careless and not having closed down either virtual machine properly, but for other reasons (trouble with migration to ML from older installations) I had to rebuild my entire Mountain Lion system from a clean disc, and I thought I might as well do the Parallels and vSL install right over again.
This time I gave the virtual machines (VMs) different names ("OS X virtual Snow Leopard" and "OS X vSL recovery"), and I also renamed their hard discs ("v Snow Leopard HD" and "vSL recovery HD") from the default "Macintosh HD".
What I found was this. When the "OS X vSL recovery" VM is set up to mount the two virtual discs, on booting up the "OS X vSL recovery" VM, the boot disc used was always "v Snow Leopard HD". I know this because it is displayed on the boot up screen. This was true whatever I did (e.g. check Parallels Boot Order under the configuration options, select startup disc under System Preferences, etc). However if I removed Hard disc 2 (pointing at "v Snow Leopard HD", the one you might want to fix), then the boot disc is "vSL recovery HD" as expected.
If the two discs had the same name you would never notice what was going on.
This prevents the recovery procedure from working, since you cannot 'hot mount' another virtual disc (as far as I know). You have to use Configure and reboot, and that process fails as soon as the disc that needs fixing is included in the list to connect, as I have described.
I found a way round. I retrieved the old recovery VM from my backup disc, so this was not a clone of "OS X virtual Snow Leopard" (it was made before I reinstalled ML). This now booted up successfully, despite an error message saying that Hard Disc 2 could not be found. This was as expected since I had not copied in the original main VM. When I reconfigured this old VM to make Hard Disc 2 connect to "v Snow Leopard HD", saved and rebooted, Parallels used the correct boot file.
Michael may already have a theory about this - maybe I have missed some obvious setting. If I haven't missed anything vital, then this suggests that the recovery instructions in #68 need modifying. It looks as if cloning causes the trouble, so the solution would be to repeat the process of creating a vSL machine from the beginning of Step 2 in Michael's original post, whilst ensuring that the names used for the VM and the virtual HD are different.
I have encountered an issue with the recovery procedure described by MichaelLAX in post #68 on Page 3 of this discussion:
My main virtual Snow Leopard (vSL) machine crashed as can happen and led to the invalid Mac OS version message as described above. I had a recovery system in place, built exactly in accordance with Michael's instructions. But it too failed to boot up and gave the same error. At the time I blamed myself for being careless and not having closed down either virtual machine properly, but for other reasons (trouble with migration to ML from older installations) I had to rebuild my entire Mountain Lion system from a clean disc, and I thought I might as well do the Parallels and vSL install right over again.
This time I gave the virtual machines (VMs) different names ("OS X virtual Snow Leopard" and "OS X vSL recovery"), and I also renamed their hard discs ("v Snow Leopard HD" and "vSL recovery HD") from the default "Macintosh HD".
What I found was this. When the "OS X vSL recovery" VM is set up to mount the two virtual discs, on booting up the "OS X vSL recovery" VM, the boot disc used was always "v Snow Leopard HD". I know this because it is displayed on the boot up screen. This was true whatever I did (e.g. check Parallels Boot Order under the configuration options, select startup disc under System Preferences, etc). However if I removed Hard disc 2 (pointing at "v Snow Leopard HD", the one you might want to fix), then the boot disc is "vSL recovery HD" as expected.
If the two discs had the same name you would never notice what was going on.
This prevents the recovery procedure from working, since you cannot 'hot mount' another virtual disc (as far as I know). You have to use Configure and reboot, and that process fails as soon as the disc that needs fixing is included in the list to connect, as I have described.
I found a way round. I retrieved the old recovery VM from my backup disc, so this was not a clone of "OS X virtual Snow Leopard" (it was made before I reinstalled ML). This now booted up successfully, despite an error message saying that Hard Disc 2 could not be found. This was as expected since I had not copied in the original main VM. When I reconfigured this old VM to make Hard Disc 2 connect to "v Snow Leopard HD", saved and rebooted, Parallels used the correct boot file.
Michael may already have a theory about this - maybe I have missed some obvious setting. If I haven't missed anything vital, then this suggests that the recovery instructions in #68 need modifying. It looks as if cloning causes the trouble, so the solution would be to repeat the process of creating a vSL machine from the beginning of Step 2 in Michael's original post, whilst ensuring that the names used for the VM and the virtual HD are different.
Much to chew on in this last post and I am not sure if I completely understand it.
Most importantly, did you solve YOUR problem?
And if so, could you point out any specific additions/modifications that I can make to Post #68 based upon your experiences?
And, do you think that Post #68 suggestions have changed in light of Mountain Lion? I still have not upgraded.
Thanks!
Most importantly, did you solve YOUR problem?
And if so, could you point out any specific additions/modifications that I can make to Post #68 based upon your experiences?
And, do you think that Post #68 suggestions have changed in light of Mountain Lion? I still have not upgraded.
Thanks!