In Adobe’s knowledgebase I read, that described phenomen is correct. The reason is the following:

Mac OS X Snow Leopard (v10.6)’s enhanced security features prevent Adobe’s PDF Printer from functioning as it did in previous versions. As a result Adobe Acrobat Pro 9.1 removes the Adobe PDF Printer and adds a new Save as Adobe PDF function. Customers using earlier versions of Adobe Acrobat will find that the Adobe PDF Printer is unusable when running on Snow Leopard.

But how do I create PDF files with Adobe Acrobat? Here’s the solution:

Instead of using a PDF printer in the printer dialog, you just have to use the PDF option in the printer dialog:

Some of its features are:

• Importing and exporting sound files to several format (WAV, MP3, FLAC, etc.)
• Recording and playing sounds
• Multitrack mixing
• Noise removal
• Filtering etc.

We got the task to create a podcast (or simpified a remix). This production should take 30 to 120 seconds. We could remix existing audio files or record a new commercial. We desided to mix the vocals with the instrumentals of two different songs. This is quite easy and can be done as follows:

Import both songs in Audacity. Then you should have two tracks:

Audacity with 2 stereo tracks

Then the time consuming part begins – cutting, copying and deleting with the selection and time-shift tool…

Audacity Toolbar

For some parts I had to change the tempo of the voice track. It can be realized with the effect “Change Tempo…” or “Change Speed…”. They do the same but have differences in pitch handling. The “Change Tempo…” effect doesn’t change the pitch so your song doesn’t sound like Mikey Mouse.

At last you can export the mix through the export function and save the file in the desired format (mp3, wav, etc.)

And here’s the result – feel free to click on the play arrow:

So I started to search through the internet and I found something in the forum of Juniper itself:
Snow Leopard Network Connect Fix:

It Seems that Snow Leopard has changed some of the internal structure of Network Connect and removed the frameworks directory as well as messing up the permissions where changed.

After reading the workaround carefully, I searched for a Juniper Network Connect Installer and found one via Google. I installed the application and as expected the vpn tunnel didn’t work yet. As written in the workaround thread I have to do 2 things manually:

• Change the file permissions of the following folder (version number stands for the installed NC version – in my case it is 6.4:
  sudo chmod 755 /usr/local/juniper/nc/[version number]/

• Create the folder ‘Frameworks’ in the Network Connect application folder:
  sudo mkdir '/Applications/Network Connect.app/Contents/Frameworks'

After these two tweaks I started another attempt – and it works!

On several websites I read about connection timeouts and disconnections. A guy wrote that NC isn’t able to clean up the routing table on establishing of a connection. One trick which should work is to disable all unused network interfaces. I can’t commit this problems, and I hope this resists as long as Juniper releases their update.

After some research and try-and-error I found an easy way to change the handler without getting in contact with the support unit – thanks to my studies colleague Thomas Galliker and to Google.

There are two possibilities to bypass this “problem”:

1. Change the ending of all php files to .php52.
2. Add the following lines to the corresponding .htaccess File to use the PHP 5.2 handler for all php files:

Action php /cgi-php52/php
AddHandler php52 .php

After changing the handler via .htaccess file I didn’t have any problems with my installed and activated plugins.