Can DCOM98 be brought back?

[GoogleCodeExporter]

What steps will reproduce the problem?
1. winetricks DCOM98
2.
3.

What is the expected output? What do you see instead?
Used to install DCOM98

What version of the product are you using? On what operating system?
MacOSX, 20110417_0

Please provide any additional information below.
I am using a game that sees to not run except with dcom98 installed. It's 
really a VB app, not written by me. Used to be, I could use winetricks to 
install dcom98 and all would be fine. Now, I can not. I would request it be put 
back into winetricks.

Original issue reported on code.google.com by s...@fatula.us on 6 May 2011 at 6:50

[GoogleCodeExporter]

No, sorry, dcom98 does not work with current wine.

If you were using wine-1.0.2 or maybe wine-1.2.2, you might be able
to run dcom98, but right now, it just explodes.

Better to file a bug at http://bugs.winehq.org for the individual app
that doesn't work with current wine.  

Original comment by daniel.r...@gmail.com on 6 May 2011 at 1:14

• Changed state: WontFix

[GoogleCodeExporter]

It would be nice to have dcom98 as it is needed to run WinBUGS. Exploding 
sounds bad...hope it can be resolved.

Original comment by MVedom...@gmail.com on 8 Jul 2011 at 5:57

[GoogleCodeExporter]

I see there's a bug report for winbugs, 
http://bugs.winehq.org/show_bug.cgi?id=18672
but I can't reproduce the problem.
Are you quite sure you can't run winbugs with wine-1.3.22
without dcom98?  What happens if you do?

Original comment by daniel.r...@gmail.com on 8 Jul 2011 at 6:20

[GoogleCodeExporter]

So I may be in the wrong area as I'm putting wine on OSx 10.6.8 not linux. 
According to 
<http://www.aidanfindlater.com/installing-openbugs-in-mac-os-x-using-winebottler
> I have to have dcom98 for winbugs to work without a blackbox (Trap 101) 
error. Ha ha, I don't really know what that means or why dcom98 is needed or 
what it does. I've been searching around trying to get winbugs to work on my 
mac and hours of searching lead to that blog among many others. I'm currently 
doing what Aidan recommends in his note. Thanks for any help, and for 
responding so quickly.

Original comment by MVedom...@gmail.com on 8 Jul 2011 at 6:43

[GoogleCodeExporter]

winebottler has a very old version of wine.

I'd suggest using a newer version of wine somehow, perhaps with Codeweavers 
Crossover (http://codeweavers.com), perhaps with PlayOnMac, perhaps by building 
it yourself.  

Original comment by daniel.r...@gmail.com on 8 Jul 2011 at 6:49

[GoogleCodeExporter]

Ok, thanks for your help and suggestions.

Original comment by MVedom...@gmail.com on 8 Jul 2011 at 6:54

[GoogleCodeExporter]

To anyone else who is having this problem I found a workaround to install 
winbugs14 on mac osx and have it work with R that seems to work ok although it 
is VERY roundabout. There's probably a better way but all the ways I found did 
not work out for me. Following daniel.r...@gmail.com's suggestion I installed 
PlayOnMac and then did some tinkering. Here's what I did:
1. installed wine using MacPorts following these directions (takes a LONG time 
~1hour) :http://davidbaumgold.com/tutorials/wine-mac/
2. then using macports installed winetricks: terminal: $ sudo port winetricks
3. at some point, in the terminal, run: $ sh winetricks nocrashdialog
This should stop the blackbox from showing up when you get to the PlayOnMac 
steps later
4. downloaded the Winbugs14.exe installer file, the patch, and the license from 
here : http://www.mrc-bsu.cam.ac.uk/bugs/winbugs/contents.shtml
5. Installed in wine. First in the terminal cd to the directory containing the 
Winbugs14.exe installer file like david baumgold instructs. While in that 
directory type: wine WinBUGS14.exe
6. Eventually winbugs will pop up and you'll probably have a blackbox popup 
ignore it (don't click OK). 
7. Now open the patch file you saved: File-->Open then find it and open it. 
Then go to Tools-->Decode and click "Decode All". Two prompts may come up, 
click OK to both. Now do the same thing with the license file and then Exit.
8. The problem is, MacPorts ports wine version 1.2.3 but in order for Winbugs 
to work without the blackbox error you need version 1.3.9. Soooooo....
9. Install PlayOnMac (go here:http://www.playonmac.com/en/download.html) 
Download and install it. Run it and go to Tools-->Manage Wine Versions and then 
add 1.3.9
10. Then in PlayOnMac click Install then on the bottom left click "Install 
unsupported application". Click Next-->Install a program in a new prefix--> 
name it something that makes sense-->Check "Assign Wine Version to 
Program"-->Assign Wine 1.3.9 to your program--> if prompts come up about Gecko 
click install--> then browse to the unzipped folder containing WinBUGS14.exe--> 
add an icon, name it, and browse to same file
11. That should do it. WinBUGS14 should now work and you should have an icon in 
PlayOnMac that works. If you want to just run it straight from R then continue 
on. Otherwise, hope this helped!

12. To get it to interact with R you have to make sure the actual directory 
with all the Winbugs stuff (folder called WinBUGS14) is in the prefix that you 
just named under the "Program Files" (in my system it was in 
/Library/PlayOnMac/wineprefix/TheNameYouPicked/drive_c/Program Files/". You'll 
need sudo privileges to copy it there. You'll also need to create folders named 
Gecko and Freetype in a folder you create ("share") and place the Gecko folder 
and freetype (downloading each... google them) folder respectively in share. (I 
know the Gecko and Freetype thing isn't clear, but that did it for me, if 
someone knows better please speak up).
13. Setup R as it says here: 
http://www.stat.columbia.edu/~gelman/bugsR/index.html 
14.Settings in bugs() for R2Winbugs to work
useWINE=T, WINE="~/Library/PlayOnMac/WineVersions/1.3.9/bin/wine",
bugs.directory="~/Library/PlayOnMac/wineprefix/NameYouPick/drive_c/Program 
Files/WinBUGS14/", 
WINEPATH="~/Library/PlayOnMac/WineVersions/1.3.9/bin/winepath",
working.directory=NULL,

I realize this is super convoluted but hopefully it helps somebody.

Original comment by MVedom...@gmail.com on 12 Jul 2011 at 1:37

[GoogleCodeExporter]

Indeed, it's a useful writeup.   It probably belongs somewhere else, but this 
is a good start :-)  

Original comment by daniel.r...@gmail.com on 12 Jul 2011 at 1:50

[GoogleCodeExporter]

you can also just use openbugs instead of winbugs, since it does not rely on 
Win98 architecture

Original comment by puruc...@gmail.com on 7 Sep 2011 at 9:11