http://bugs.winehq.org/show_bug.cgi?id=13915
--- Comment #38 from Evan Goers megatog615@gmail.com 2009-12-10 22:16:28 --- (In reply to comment #37)
It seems to be a problem related to addressing so... Maybe sysctl values can change that. Like I said, changing some kernel adress randomization, like stated by someone before my interventions, does change the behaviour. It changes from "Don't start" to "Start but crash".
So, maybe a list of sysctl values, related to adressing, or the kernel configuration used would maybe allow to pinpoint the source of the problem correctly. Anyway, if that works, could you give us your game version and the content of "obse_loader.log", located in the game folder ?
I'm using OBSE 0017b, Oblivion 1.2.0.416(Shivering Isles).
To add to the mystery, if you use OBMM to launch Oblivion, it actually launches obse_loader.exe, which in turn launches Oblivion.exe. It does *not* crash if you use OBMM to run Oblivion enhanced with OBSE.