Wehner, P. and Krüger, R.: SENSE – Intelligent Storage and Exploration of large Document Sets.Poster Session of the 43. Jahrestagung der Gesellschaft für Informatik (INFORMATIK 2013), Koblenz, Germany, Springer, 2013
Do note that the SENSE project is funded by the German Federal Ministry of Education and Research (bmbf) under grant No. 01IS11025A and constitutes a part of “KMUInnovativ: IKT” initiative.
Have fun. P
ps. I’m also eagerly looking forward to dive into the “Tag der Informatik” on Wednesday, September 18, 2013.
I remember a time when virtual box users got stuck when trying to run full screen ubuntu guests on ultrabooks with the (as of that time) unusual screen resolution of 1366×768 pixels. Of course, 1366×768 pixels was quite an esoteric resolution at the times of virtual box 4.0.x or so and the emulated graphics driver was simply not (yet) aware of such a circumstance. However, trying to set up an current ubuntu 12.10 guest on the latest vmware player 5.0.2 environment, targeting another 1600×900 ultrabook full screen resolution, showed up to produce the same issue again and I’m not the very first to learn alike, see the vmware threads for example.
The basic problem, as depicted above, is that the guest os just does’nt see the actual native resolution of the hardware because the emulated graphics driver does not provide or list it on request. It will, on the other hand, be able to run that resolution though. Ever tried to find the missing resolution in your display settings with no luck? Then switched the guest os to full screen and, plop, it is there? Then bounced the guest os and the game starts from scratch (and you get this oversized X error window of unsuccessful attempts to apply the latest resolution setting in ~/.config/monitor.xml)? Welcome at Denny’s!
Wehner, P. and Krüger, R.: Semantic-guided Communication & Composition in a Widget/Dashboard Environment.Proceedings of the 5th International Workshop on Lightweight Integration on the Web (ComposableWeb), 13th International Conference on WebEngineering (ICWE’13), Aalborg, Germany, Springer, 2013
The problem of oracle dll files being still active (and locked against modification) inspite of a clear shutdown of all oracle services on windows has been around for lightyears it seems.
What changes, though, is the net of dependencies that has to be checked prior to an upgrade or patch execution to find the processes that actually keep hooking up the dll’s in question. I was hit again lately, when trying to apply the server 22.214.171.124 Patch 18 (the APR2013 bundle patch) on win x64. The infamous error message on executing opatch apply read:
Oracle Interim Patch-Installationsprogramm Version 126.96.36.199.3
Oracle Home : e:\oracle\product\11.2.0\dbhome_2
Central Inventory : C:\Program Files\Oracle\Inventory
Verifying environment and performing prerequisite checks...
Prerequisite check "CheckActiveFilesAndExecutables" failed. The details are:
Following files are active :
Recommended actions: OPatch needs to modify files which are being used by some processes.
OPatch failed with error code = 41