damians personal blog

Arabe	Deutsch	Français
Hummus	Zerstossene Kichererbsen mit Sesamöl	Poids chiches cassés au l'huile de sésame
Moutabal	Gegrillte und pürierte Auberginen	Aubergines grillés et purées
Taboulé	Petersiliensalat	Salade au pérsil
Fattoush	Salat (Lattich, Tomaten, Zwiebeln, geröstetes libanesisches Fladenbrot)	Salade (laitue, tomates, ognions, pain libanes rôti)
Labné	Entwässerter Joghurt	Yaourt déhydraté
Zaitun	Oliven	Olives
Sahtar	Spezielle Gewürzmischung mit Sesam	Mélange d'épices et sésam
Haléoué	Süsse Spezialität aus Sesamöl und Zucker	Spécialité douce à la base de l'huile de sésame et sucre
Marhaba	Guten Tag (offizieller Libanesischer Dialekt)	Bonjour (dialecte libanes officiel)
Kefik / Kefak	Wie gehts	Ça va?
Kesik / Kesak	Zum Wohl (die Dame / der Herr)	Santé (la dame / le messieur)
Kascun	Zum Wohl (alle zusammen)	Santé (à tous)
Sahten	Guten Appetit	Bonne Appétit
Saha	Die Gesundheit	la Santé
ala albak	gleichfalls	pareillement
Haram!	(Du) Armer!	Le pauvre (toi)!
Mabrouk	Gratuliere	Félicitations
Ashta!	(Erste) Sahne!	Crème (de la crème)!
Habibi	Schatz	Chérie
Elbe	Mein Leben	Ma vie
Hayété	Mein Herz	Mon coeur

Nachtrag: fast hätte ich das schönste vergessen - die Kosenamen!

        31.Mär.2006, 17:27 :: people and cultures :: Permalink :: Comments (0)

Well, i admit the title was a little exagerated. I will explain how You can install the software on an Apple OS X install DVD that ships with a Mac on any other Mac.

Careful: It will not describe how to install the OS that comes with a Mac on another Mac but only the software bundled with it. I encountered this problem when I wanted to install some additional software from my MacBook Pro DVD on my older iBook.

First, where to find the Packages:
/Volumes/Mac OS X Install Disc 1/System/Installation/Packages/.packages/ on the first install disc:

• Booth.pkg
  
• CPU_ComicLife.pkg
  
• CPU_QuickBooks.pkg
  
• CPU_OfficeTDD_disc.pkg
  
• CPU_OmniOutliner.pkg
  
• Nanosaur
  
• Marbleblast
  
• and so on …
  


/Volumes/Mac OS X Install Disc 2/Packages/ on the second install disc (sometimes also /Volumes/Mac OS X Install Disc 2/Packages/.packages):

• GarageBand.mpkg
  
• iDVD.mpkg
  
• iMovieHD.mpkg
  
• iPhoto.mpkg
  
• iWeb.mpkg
  
• iWork Trial.mpkg

How to get there:

• Open the Finder
  
• press [CMD]-[SHIFT]-G
  
• copy and paste the path given above into the dialog box
  
• Finder opens directly a Folder with all the software packages

Some packages will be easy, some a little more difficult. If a package has the ending .pkg, such as Booth.pkg, You can double-click, and it will install.
But if a package has the ending .mpkg it is likely that You get an error when trying to install saying "The Software cannot be installed on this computer". Then You have to use the following workaround to trick the verification:

• Open the Finder
  
• right-click on the correspondig package
  
• select "Show package contents"
  
• open the "Contents" folder
  
• open the "Resources" folder
  
• double-click the all the packages You find and install them one by one; this way there will be no verification whether You are allowed to install the software or not

The software installed will work fine if the OS and CPU is compatible. For instance iLife '06 works great on my iBook.

        29.Mär.2006, 22:32 :: mac os x :: Permalink :: Comments (0)

Ich habe heute in einer freien Minute mich gefragt, ob man denn das Pfeifen (englisch hiss) des MacBook Pro nicht mit dem internen Mikrofon aufnehmen kann. Und siehe da, es funktioniert tatsächlich: mbp_pfeifen.mov (296KB).

Weils grad so spassig war, habe ich einen Mini-Film draus gemacht. Ich gebe zu, der Film ist absolut überflüssig, aber was solls – man hört das Pfeifen deutlich. Bloss die hohen Frequenzen kommen nicht so rüber, die hat das eingebaute Mikro unterschlagen, denn in echt ist das Pfeifen viel unangenehmer als in der Aufnahme.

        21.Mär.2006, 0:42 :: apple :: Permalink :: Comments (0)

I had some difficulties to get the emulator Q (based on QEMU) running on my Intelmac. Here is a little HowTo install Windows98 on OS X:

• Download the unstable Build from kberg.ch/q/ or get it from my mirror.
  
• If you already used a previous version, delete the preferences files
  ~/Library/Preferences/ch.kberg.q.plist
  ~/Library/Preferences/ch.kberg.qemu.plist
• Open Q.app, click on the plus to add a new pc.
  
• Disable the checkbox "Drivers: Show Disk with Q Windows Drivers".
  
• Go to tab "Hardware", select in the "Harddisk" drop-down "Create other Diskimage...", go with the suggested settings (1024mb qcow).
  
• Change "Boot from" to "CD-Rom" and finish your configuration with a click on "Create PC".
  
• Insert the Windows98 installation CD into your Mac and press the run button (Start PC).
  
• In the DOS prompt appearing follow the instructions to install windows:
  • Boot from CD ROM
    
  • Run Windows 98 Setup
    
  • Continue
    
  • Configure free space
    
  • Yes activate support
    
  • Confirm
    
  • Boot from CD ROM
    
  • Run Windows 98 Setup
• And then follow the normal steps to install good ol' Win98.

        19.Mär.2006, 19:39 :: mac os x :: Permalink :: Comments (0)

Usually when you have an unreactive application, you can terminate it with the cmd-alt-esc dialog "quit application immediately". But sometimes it is a process which won't show up in that list. Then I get the terminal at hand, type top -u to find the PID, quit top with q and type kill . For most of the processes, this will do it perfectly. But today I had a process which was using up 100% of one of my cores and will not terminate with the above method.

How I got it killed finally:

After the kill -stop, the process stopped using my CPU at 100%. Maybe it would have been enough with only -stop and then -kill directly, but I haven't yet had the opportunity to test it.

Update: Well, it happened again, and I could verify my theory.

Update 2: I just found out that sudo kill -kill is actually sufficient to end a process who won't react to a 'normal' kill.

        18.Mär.2006, 13:18 :: mac os x :: Permalink :: Comments (0)

When I think back to that keynote of Steve when he revealed Apples switch to Intel... I was one of the harshest critics of that decision. I shook my head in front of my iBook G4 and thought "where are You going Apple?" Other computer manufacturers were switching to the Cell chip, and Apple turns the back on the modern, slick and powerful PowerPC architecture.

And now I am one of the first people to own an Intel-based mac, the MacBook Pro. Why this? Because I wouldn't ever want to change away from Apples smoothly designed hardware. And even more important I have gotten used to the practical and intuitive operating system OS X.

(Just to make myself clear - I don't think the turn towards the x86 CPU architecture was inevitable. For economic reasons it may have been the best decision. But it gave away a bit of the "be different" mentality of Apple. And now I gotta live with what I can't change… )

My first impressions of the MacBook Pro I am writing on: this is truly the Rolls Royce of all the Notebooks. Features like the integrated iSight camera, the indeed very very bright screen or the backlight keyboard make You just love this baby.

The system is faster than ever, the universal (Intel&PowerPC) software pops right into life when you want it, and Rosetta does its best to serve You any software you want to use. Any? A small bunch of app's will not run in rosetta an haven't been adapted yet.

The most painfully missing app's I've encountered so far - You only know the true value of something when it's gone!

• CocoaGestures why won't that damn tab not close?
  
• PithHelmet where has all that useful information gone among these ads?
  
• AutoPairs there is a key for closing a bracket?

To the CocoaGesture and PithHelmet there is a fairly easy solution: activate the checkbox "Open using Rosetta" in the information window in the Finder of your favourite browser. The next time You open the application it will take a little longer to launch, but once the app is running, the speed loss is neglectable.

One thing I was very suprised to see working without any problems is the Cisco VPN. Just get the latest version (1.6 according to the official count, whereas it will report as 4.9.00 (0050) in the Finder), install it, and it works. And it works even better than before: I haven't had a problem with the kernelextension so far, wich was pretty frequent with the older version.

        6.Mär.2006, 23:13 :: apple :: Permalink :: Comments (0)