Thursday, October 18, 2012

PS3 Repeatedly Cannot Connect to WLAN


Background

I have a PS3 (CHECHL04 80GB model from 2008 or so) which we are using predominantly for watching movies from the Playstation Store. Up to recently the PS3 was connected via cable to an Apple 1 TB Time Capsule which I used as WLAN router. The Time Capsule itself was connected to a cable modem.
Then, once in a sudden the Time Capsule quit its service... I wrote about this earlier.

Current Setup

I replaced the Time Capsule with a combination of an Apple Airport Express and a Synology DS212j NAS, the cable modem remained the same. Unfortunately, the Airport Express only has one LAN cable socket instead of the 4 like the Time Capsule or an Airport Extreme - which I did not buy due to budget reasons. The one cable socket I reserved for the connection of the DS212j, so the PS3 had to connect to the network via WLAN from now on.

Problems, Problems, Problems - WLAN & PS3 sucks

Everything started without problems - I configured the PS3 network settings (more or less everything on auto mode, the wlan password, ...) and it worked without problems. ... once ...
The next time I switched on the PS3 (I wanted to watch a movie together with my wife..) nothing worked - no connection to the network possible.
What followed was a couple of days nightmare of configuring the network settings again and again and trying all kind of permutations of the network parameters over and over. The wlan was always detected, I verified passwords and IP addresses (automatic and manual), tried the same on the Aiport Express side. Nothing worked...

At Long Last - The Helpful Hint

During my configuration exercises I scanned as well a thousand forums and blogs, without finding a helpful answer right away. In the end one discussion was helpful - unfortunately I cannot find it again to link it here.
In this thread, one author said that there is one speciality of apple wlan devices: if they are working in environments with many wlan routers around (what is the case for me), it switches to wlan channel 13 which causes problems for many client devices - and especially the PS3. The author adviced to manually set the wlan channel of the Airport to a channel lower than 12 or 10 (can't really remember).

I followed this advice and it worked like a fly and ever since. I tried a fixed channel 3 and 6 without problems. I set the PS3 network settings to mostly standard and automatic, no special tricks.

I hope this blog helps other frustrated PS3 network configurators ;)

Monday, October 15, 2012

POSTGIS Spacial Database Installation on a Mac OS X Lion System


Background

Presently I am working on a hobby project of mine where I want to develop a web application with Ruby on Rails which shall visualize data on maps. I essence I want to build a GIS application. After reading a couple of sources in the internet, it became obvious that it would be best to have a spacially enabled database - meaning a relational database with an extension so it can process queries for spacially arranged data. An example would be a simple query where you want to know the gas stations in a certain radius around your current location.
The resulting architecture I want to use is the following:

  • The system database I want to use will be PostgreSQL
  • To spacially enable the database, I want to use the PostGIS addon for PostgreSQL
  • To enable the communication between Rails and the PostGIS server, the activerecord-postgis-adapter is required
  • To be able to write "geospacial" ruby code, the GeoRuby gem is required
  • Furthermore, I want to do the map visualization with OpenLayers to be independent of commercial map services. 

Step 1: Installing the PostgreSQL

So far, I used the Postgres.app (download on postgresapp.com) for my development (to be honest, my development is currently at chapter 9 of Michael Hartl's excellent tutorial of a micropost app). But I found out that Postgres.app is insufficient for the installation of the PostGIS enhancement, but a full PostgreSQL installation is required (see README.postgis in the PostGIS distribution files).
The latest PostgreSQL EnterpriseDB installation files for the common operation systems are available at enterprisedb.com.

PostgreSQL Installation Problem

During the installation I experienced a problem which has been seen by other users as well (see for instance this discussion thread): the installation starts without problems, runs all through, but hangs in the end with a message

  • "Loading additional SQL modules"

You can only click on "cancel" (what I did once...) which rolls back the whole installation. The discussion above gave the helpful hint:

  • hard stop the installation via the Activity Monitor
  • stop any processes called "postgres" running in the background
  • restart the installation once again with the same directories

This procedure makes the installation run once again and this time ending without any problems.

Step 2: Installation of PostGIS

I found a good description "installing PostGIS on Mac OS X and Ubuntu" by "juniorz" which I followed. Still, I ran into a couple of issues and obstacles which I will describe here.

First installation step ($ brew install postgis)


Firstly, I encountered the following error:
==> ./configure --prefix=/usr/local/Cellar/proj/4.8.0
==> make install
Error: The linking step did not complete successfully
The formula built, but is not symlinked into /usr/local
You can try again using `brew link proj'
The advice to run "brew link proj" actually did not fix the issue, I got another error message:
$ brew link proj
Linking /usr/local/Cellar/proj/4.8.0...
Error: Could not symlink file: /usr/local/Cellar/proj/4.8.0/bin/proj
Target /usr/local/bin/proj already exists. You may need to delete it.
To force the link and delete this file, do:
  brew link -f formula_name
What helped in the end was a forced deletion of proj:
$ brew link -f proj
A second error appeared for the GEOS library:
==> ./configure --prefix=/usr/local/Cellar/geos/3.3.5
==> make install
Error: The linking step did not complete successfully
The formula built, but is not symlinked into /usr/local
You can try again using `brew link geos'
Here the situation was a bit more difficult than for "proj". Neither worked "$ brew link geos" nor "$ brew link -f geos" as the system refused to delete it due to missing privileges. As well "sudo brew link -f geos" failed.
What helped here in the end was to use Finder and to manually delete the directories "geos" located in
/usr/local/Cellar/
/usr/local/include/
 Another issue appeared, when the system tried to download the required json library from
http://oss.metaparadigm.com/json-c/json-c-0.9.tar.gz
here the download process repeatedly stopped at a couple of downloaded percent. I was able to fix this by downloading the file json-c-0.9.tar.gz from github and to move it to the Homebrew installation directory
/Library/Caches/Howbrew/
With these little tricks I was able (Hooorray!) to install PostGIS.


Second installation step (initdb /usr/local/var/postgres)


No Issues.


Third installation step (pg_ctl -D /usr/local/var/postgres -l /usr/local/var/postgres/server.log start)


When performing the command above, I ran into the following error:
$ pg_ctl -D /usr/local/var/postgres -l /usr/local/var/postgres/server.log startserver startingsh: /usr/local/var/postgres/server.log: No such file or directory
This could be fixed simply by adding the required "postgres" directory to /usr/local/var/ with the help of the Finder.


Fourth installation step (createdb postgis_template)


This installation step needed as well some adjustment. Trying to execute the command as noted by juniorz, I got a password error, because the command was executed for my user who was unavailable in the DB. After a bit of reading I executed the command with the "-U" option, which allows to execute the command with explicitly giving a user name. I used the postgres default user, whic was the only one available in my local tes DB. With the -U option the command looks like this:
createdb -U postgres postgis_template
you will be asked to give the password after hitting enter

... Here I am stuck in the moment...

Monday, October 8, 2012

Google Chrome Crashes with Error "Chrome.exe - Bad Image" due to icudt.dll

Background

I have been using Google Chrome as standard browser on a Windows 7 Enterprise PC with Service Pack 1 ever since. Then, once in a sudden I get an error popup when I want to start Chrome telling me:

<path to user directory>\AppData\Local\Google\Chrome\Application\22.0.1229.79\icudt.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support.
 The search for solutions did not yield an immediate remedy, so I want to collect my experiences in a blog.

1. Attempt: Install Chrome over existing installation

First thing I tried was to simply go to the Chrome website and install it over the existing installation. I did not run the installation in administrator mode. And I did not download the installer explicitly to some directory.
Result: Failed

2. Attempt: Uninstall Chrome completely and Install again

By using the Windows control panel I uninstalled Chrome from my system, went to the Google website and re-installed Chrome again.
Result: This approach worked