I recently bought an Xbox game for my kids, Lego batman 2. They LOVE it. Really LOVE it. Fine. It is just that the game has some serioud flaws. Flaws that are widly documented on the net. And that this hurts imho the brads Lego and WB Games. caus it is not like I am the only one suffering from this problem: as 2.5 M results show.

The maker knows about that the game freezes during many cut scenes, though says it happens "occascially".

See this message

Occasionally, a crash occurs while Batman and Robin are hopping into a car. The rain and ambient noises continue like the game is loading but the game freezes.
If this occurs, try the following:
· Pause the game and click Extras. In Extras there will be an option to enter a code. Enter the code ‘n0cut5’ and resume play. Doing so will allow you to skip the cutscene and continue progress.

It lists a number of other "solutions". Dont bother. Just use the "no cutscene. Despite it's name you still see the movies, but can skim them, do so in level in 9 and 12:-(

Naambellen. Kent u die uitdrukking nog? Ik moets daar aan denken toen ik laatst hoorde dat onze -volgens de GeenStijlGanzenGeneratie- “staatsomroep” NPO uit “uw belastingpoet” de postduiven voerde door NPO.nl te kopen.
Naambellen. Het eenvoudiger maken van een telefoon nummer door deze van “een naam” te voorzien. Op telefoons staond vroeger -in Amerika al sinds een halve eeuw. Op oude dial toestellen stonden per cijfer al 3 letters. In Nederland met de introductie van mobiele telefoons waarmee ge-sms-ed kan worden kortere tijd populair geweest. Zo is het landelijk oveheidsnummer 077 4656767 volgens phonespell het handig te onthouden 07-pi-OK-or-or.

Naambellen. Een vorige werkgever introduceerde een dienst waarbij je middels je computer -begin 2000- kon inbellen naar een speciaal nummer om een VPN te slaan naar een beveiligde infrastuctuur. Inbellen middels een modem LCDbuis vriendjes. Dat deden sommigen toen nog. Het nummer dat je op je computer moest intypen was netnummer (wellicht 0800 of zo) IKBELIN. Lekker handig, voelt u hem? Moest je dus op je nokia telefoon gaan kijken om te weten welk telefoon nummer je moest bellen op je PC. De zelfde mensen die hier voor kozen gingen ook -geen grap- met polonaise door de gangen toen bleek dat ze voor een grote telco klant een soort “portal” (het was 2000) mochten bouwen en het domain dat ze wouden gebruiken nog “vrij” was; whepp.nl. Ja met wh en dubbel pee... :-)

Naambellen. Domainen die je moet spellen. Ik denk dat deze mensen nu bij de Nederlandse Publieke Omroep werken en denken dat een drieletterige domain moesten kopen. Dat hoeft in 2012 dus echt niet meer, content is water, google de sluis. Maak de eerste en de tweede zorgt dat klanten je vinden. 2012... Een ton voor een domein.

Femke Halsema is een redelijk goed twitteraar. Dus toen ze ok bezoek was in den vreemden schreef ze over de misstanden die daar waren in

Vervolgens twitetrde ze een deel twee en zie de reakties hierop (omgekeerd lezen)

Voor lezer is de les:
lees de context

Voor schrijver is de les,
wees bewust van het feit dat de lezer de contekst niet ziet.

Klinkt raar maar analoog aan
"Be liberal in what you accept, and conservative in what you send.", het Robustness Principle van mijn held Postel

Here my rants on a recent problem I had with AFS, also known as AppleFileServer. Before I continue on my complex problems and childish solution however, let me tell you that I do know a bit about internetworking, Unixes and troubleshooting. I made a living for over a decade as a network engineer and sysop. I know TCP/IP, I know Unix. Just to make clear that no matter how easy the solution of my problem is, I know how to get in trouble during the troubleshooting phase :-)

My problem? Let me tell you about my problem. I love Unixes yet have no time anymore to do maintenance and I just want a slick UI and a powerful GUI. So, I paid the appletax and switched all my machines from GNU/Linux (and a windows pc) towards the OSX platform. I have a couple of macbooks, an air, a mini and an iMac. Despite it being an Apple, I still like to make backups. Or rather, one day I might like to do a restore. Nobody likes backups.

So I have a huge external disk to my iMac and use TimeMachine on my macs to do their incremental backups towards this disk. All worked fine. And then one day, backups didnt work. None of my macs could mount any disk on my iMac; the host of my shared TimeMachineDisk. Yes, ping worked. Yes, I could share a screen. Yes, from my imac I still could mount all other disk on all the client. But not from any of the clients towards the iMac.

In fact, as soon as a client wanted to mount any disk on my iMac, it resulted in a very high CPU usage. My iMac has two CPU’s and all available CPU resources were being used by AppleFileServer.

So I googled. And believe me, I am not the only one with this problem. Far from as you can see in this autocomplete Google screenshot:

I did all the tricks, search for all the answers, used all the command line tools to see where the problem starts including TCP dumping the connection. I dsabled auto-disconnect in AFP editing the .plist files, removed spotlight indexing on all AFP volumes, deleted .SpotLight-V100 directories on AFP volume, verified that Host Cache Flushing is disabled, set the following default: defaults write com.apple.desktopservices DSDontWriteNetworkStores true, delete all DS_store files, disabled kerberos for AFP authentication, checked the maxThreads setting for AFP etc etc.

Then I found out that if the iMac /didnt/ had the mountpoint of the external disk (e.g., disk is off or umounted) I could mount all other shares via AFS form the clients. So the problem was within this mountpoint. I made a directory on the external disk and only shared that directory. Yes that worked. But TimeMachine needs a physical disk and I didnt feel like this solution was the way to go. I googled some more. And more. And yes....

All I had to do was *rename* the disc. Rename the disc from “Luchtbed” to “Drijfzand” and then... All worked....

Try this if you have the same problems and dont wont the same troubleshooting.

Today I thought it might be handy to change my username on a new Lion MacBook air to match the nameing convention of my other Unix/Apple boxes, from "bert boerland" towards the more unix command line friendly "bertboerland".

Once I did that I left the machine running and after some time the screensaver kicked in. Then when I wanted to login on the OSX, there was only a box with my OLD username already filled in and room for my password. Sure enough entering the right password (with the non selectable old username) resulted in a wrong combination.

There was no other way to log in (other then via SSH) towards the box. Yes, I actually had to reboot the box to be able to login again!

You can prevent this by ticking the boxes under preferences > user management as shown below (in Dutch). But having this default is rather stupid Apple!