Creating folders for apps

• If you’re in rearrange mode – by tapping and holding on an app on the home screen until the app icons start to shake – creating folders is easy and intuitive: You only need to drag an app icon over an other app icon and the iOS instantly creates a folder and automatically names it.
• The folder opens up and shows the included apps.
• You can change the automatic generated folder name by clicking into the rounded white name field.

Rename an existing folder for apps

• Changing existing titles of folders for apps is only working in the app rearrange mode.
• So, you have to tap and hold one of the app icons on the home screen until the icons start to shake.
• Then you tap on the folder you want to rename. The folder opens up so you can see the apps and the title in edit mode.
• You only have to click on the title. Now the keyboard appears and you can rename the folder.
• Just press the home button once you are finished to exit the rearrange mode.

Hope this saves some time.

Forbidden
You don’t have permission to access /MAMP/ on this server.
Apache/2.0.63 (Unix) PHP/5.2.11 DAV/2 Server at localhost Port XXXX

That’s a big issue, as the start page links to the local phpMyAdmin page for MySQL-database configuration. So you cannot admin the database anymore.
I traced down the problem to a wrong placed file: When I configured the WordPress installation via the web-interface, an .htaccess file was placed in the root directory of my harddrive. Quite scary … but a problem which can be fixed easily

As always: no guarantee and on your own risk … especially the Terminal is a wonderful tool … but if you do the wrong thing, you may be in serious trouble!

You normally do not recognize the .htaccess file within the Finder: all filenames starting with a dot are hidden files in a UNIX system … and the Finder does not show those hidden files. But if you use the Terminal, you can look at all the hidden files easily.
So fire up the Terminal app and go to the root directory of your hard drive:

cd /

then looks at all the files in your root directory:

ls -la

If you find a .htaccess there … you probably found your problem. But look inside the file before your rename or delete it:

cat .htaccess

The easiest way to proceed is to rename the htaccess file:

mv .htaccess htaccess-backup

This way the file is shown in the Finder again and does not confuse your MAMP installation. If you know what to do you can delete the renamed file now within the Finder and drag it to the trash

Problem: After updating from Mac OS X 10.5 Leopard to OSX 10.6 Snow Leopard the installed printer driver for the Kyocera-postscript driver does not work anymore. Here it’s an Kyocera Mita FS-2000D … but it should also work with other models. The printer diver was installed under Leopard and worked quite well. After finishing the update to 10.6 you are able to send a print job to the printer, but an error message shows up in the print queue.

Diagnosis:There are incorrect file permissions under Snow Leopard fort he Kyocera printer driver … and this causes some trouble. BTW a warm thank you to @kappuchino for his diagnosis and solution!

Solution:There is nothing like fixing the bug yourself You can easily fix the problem by one command in the Terminal:

1. Log into your Mac as an administrator.
2. Open the program “Terminal” – you’ll find it under “Programs/Utilities”.
3. Input the following command into the appearing command-line window and finish it with pressing the return-key:

   sudo chown root:wheel /usr/libexec/cups/filter/kyofilter

4. Now, you’ll be prompted for your password … so put in your password of the admin account and finish the input by pressing the return key again
5. That’s it. Just Close the Terminal program. Now printing on the Kyocera printer should be work like a charm.

Using Snow Leopard feels great and you immediately recognize the speed. Looks like all of the Apple engineers work “under the hood” was worth it! You should not expect fundamental changes within the user interface or other totally new features – the core of Snow Leopard are speed, detail improvements and technology upgrades.

But what’s about the compatibility to non-Apple-hardware products? Sadly, printing on my OKI laser printer does not work with the Leopard-compatible driver for the Oki MFP C5540. By using the preinstalled generic PS-printer-driver from Apple you are able to print on the OKI printer – you even an control the duplex unit. But you are not able to control all the specific printer settings like print quality, grayscale instead of color printing or specifying the installed memory on the printer. But, who knows how long Oki will need to update their printer drivers for Snow Leopard? That’s why I started debugging myself. So, here is the solution for all the fellow sufferers who also own an OKI printer … and as always: no guarantee and on your own risk:

Problem: After updating from Mac OS X 10.5 Leopard to OSX 10.6 Snow Leopard the installed printer driver for the OKI-postscript driver does not work anymore. Here it’s an OKI MFP C5540 … but it should also work with other models, like the OKI C5450 or C8800. The printer diver was installed under Leopard and worked quite well. After finishing the update to 10.6 you are able to send a print job to the printer, but an error message shows up in the print queue.

UPDATE: You’ll find an updated diagnosis & solution in the NEW BLOGPOST!

Diagnosis: There is a bug in the printer driver … the bug had no effect under Leopard (maybe because of the Apple partition scheme). When OKI coded the printer driver, they disregarded case sensitivity in their path names … former systems did not care about case sensitivity – but Snow Leopard does!
Solution: The fast work around is to use the generic PostScript-printer driver – but there you don’t have the possibility to set the OKI-specific printer settings. That doesn’t make me happy To get back the whole functionality of the Leopard OKI-printer driver there is only one way: Hands on coding and debug Fortunately fixing the bug is no rocket science – you only need a text editor like TextEdit or TextMate and you don’t be scared program code:

1. Search for your Oki-printer driver PPD-file in the Finder … you should find it under

   Macintosh HD/Library/Printers/PPDs/Contents/Resources/

   mine is called “Oki C5540.ppd”.

2. Before you go on make a backup of this file … this way you always can come back to the original state.
3. Open the PPD-file with the text editor and search for the following line:

   *cupsFilter: "application/vnd.cups-postscript 0 /Library/Printers/OKIDATA/Filters/OKfilterA"

4. Then search for the file “OKfilterA” … I found mine under the following:

   Macintosh HD/Library/Printers/Okidata/filters/

5. Now, adjust the path in the PPD-file … the line in my corrected PPD-file looks like this:

   *cupsFilter: "application/vnd.cups-postscript 0 /Library/Printers/Okidata/filters/OKfilterA"

6. Now, you only have to save the file and restart your Mac … now it should work

Some warnings before you start: Back up your system! The following steps are only recommended for those, who know what they do with their command line terminal. And everything you do – you do it on your own risk!

• Problem 1: I use apt-get instead of aptitude … but you should not use both systems at the same time!
• Solution: You can just use apt-get instead of aptitude. So the commands are:
  
$ sudo apt-get update
$ sudo apt-get upgrade
$ sudo apt-get install update-manager-core
$ sudo do-release-upgrade

  Be sure NOT to restart at the end of the upgrade … see problem 3 why!
• Problem 2: The do-release-upgrade script starts but aborts by telling me that I don’t have enough diskspace on my boot-partition:
  
The upgrade aborts now. The upgrade needs a total of 52.4M free space on disk '/boot'. Please free at least an additional 18.1M of disk space on '/boot'. Empty your trash and remove temporary packages of former installations using 'sudo apt-get clean'.

• Solution: Start to clean up your packages by using the suggested command:
  
$ sudo apt-get clean

  … but this was not enough on my server. So I figured out that I have a bunch of old kernel versions on the boot partition – which also can be removed. Check which kernel versions are installed by using the following command:
  
$ dpkg -l | grep linux-image

  In my case, I was able to delete the old linux-image-2.6.15-29 and the linux-image-2.6.17-12. Be sure to keep at least the Gutsy Gibbon version!
  
$ sudo apt-get remove --purge linux-image-2.6.15*
$ sudo apt-get remove --purge linux-image-2.6.17*

  Then you need to update your menu.lst:
  
$ sudo update-grub

  After doing this I check the kernel list file by looking into the file with the vi-editor:
  
$ sudo vi /boot/grub/menu.lst

  If everything looks right within the automatic kernel list at the end of the file I go on.
• Problem 3: The Ubuntu-geeks solved thisone themselves, but when I upgraded from Feisty Fawn to Gutsy Gibbon, I ran into big trouble: The do-release-upgrade functioned well, but when I restarted the server it did not boot properly anymore! The kernel list was not setup properly by the do-release -upgrade script!
• Solution: Therefor I always finish the do-release-upgrade script without restarting the server;
  then I re-update the menu.lst by
  
$ sudo update-grub

  after doing this I check the kernel list file by looking into the file with the vi-editor:
  
$ sudo vi /boot/grub/menu.lst

  If everything looks right within the automatic kernel list at the end of the file.
  
$ sudo restart


When you are finished with the upgrade and restarted your server … you should be able to access the server again via ssh. Then you can check the version of the installed linux version by typing:

$ lsb_release -a

The result should look like this :

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 8.04
Release: 8.04
Codename: hardy

I hope this howto / problem solving saves some time for you