initialisation fixes

with a custom build (read self compiled with trial and error as to what additional files needed pulling into the target directory)..

ran 'daemon', changed resolution, hit 'create profile'. BOOM. i did this several times, then went looking for logs. found an emtpy dir named 'crashlog.txt/'. cue patch one.

ran 'daemon', changed resolution, hit 'create profile'. BOOM. gdb with the segfault led me to patch two, some uninitialised strings. 

ran 'daemon', changed resolution, hit 'create profile'. no BOOM :). however black screen, then ended up at the same initial menu. several iterations later i finally see the empty profile name and add one allowing me to progress. so where was the error message telling me 'hey you're stupid, put a damn profile in there will you?'. cue patch three. trivial, but took a while to find. 'com_errorMessage' was getting cleared following a 'com_Error' / server reset caused by accessing the non-existant name in the 'createProfile' switch case. i now get a nice error message