DX099: i just tested with the current development version of wine, and works fine here. did you try in a fresh prefix?
Justice has quit
Justice joined the channel
DX099
slackner: yeah, that's a fresh prefix with only corefonts and d3d9 installed
slackner
DX099: well, in your log its not a fresh prefix, otherwise msxml3.dll would exist
DX099
slackner: ok, I'll try again
ah it seems to work on a completely new prefix.
so do I have to install it in a certain order?
Haaninjo has quit
slackner
DX099: usually the order doesn't matter, at least corefonts and d3d9 should not cause any problems i guess
DX099: but maybe you also installed other overrides in your steam prefix
DX099
slackner: I don't remember any overrides, I created that steam profile a few moments ago
anyway, thanks for your help, I'll try installing d3d9 as the last lib
slackner
DX099: if you find an easy way to reproduce it, feel free to tell me, then i'll take a look if its expected or a bug
DX099: but if installing in a different order works around the issue, thats the easiest method of course ;)
DX099
ok
I'm trying to see if I can get a game run. Depending on how complicated it is, I may come try to reproduce faster
towo` has quit
qptain_Nemo has quit
lg188 joined the channel
qptain_Nemo joined the channel
c_korn has quit
ok
the game works quite well despite choppy audio and weird xbox 360 controller input problems
also, do two programs running on the same profile share the same memory space ?
slackner
DX099: you mean running in the same wine prefix? no, they do not share memory
however, for the program it looks like they run on the same windows machine
DX099 has quit
DX099 joined the channel
DX099
hmm... disconnect... so I had another question: how do you run two programs on the same wineserver, so that they can detect each other
slackner
DX099: just set the same WINEPREFIX variable, then they will connect to the same wineserver
DX099
slackner: it appears they don't. Program B needs program A to be launched to work. If I run A from CLI and then B from CLI with the same profile, B doesn't work. However, if use "wine explorer" with virtual desktop and launch them by clicking and stuff, B works...
slackner
DX099: no, the difference must be something else. are you sure you typed exactly the same wineprefix? maybe the working directory is not set correctly for one of the programs?
DX099: some programs also expect to be started with "wine start app.exe" instead of just "wine app.exe"
DX099
slackner: I may have failed on the working dir setting, I'll try again with your hints
slackner: you were right :)
so GUI launch programs within their working dir
good to know
slackner
DX099: yep. on windows most developers do not pay much attention to the working dir, because its usually always set correctly
DX099: (only very few people start apps from a cmd.exe terminal ;) )
DX099
ah thanks for the educative comment :)
now to try reproducing the stuff earlier
ehoover has quit
slackner: P.S. couldn't reproduce the issue I complained about earlier
so I guess I'm set for today with Wine. Thanks a lot for your support slackner.