Re: [Bugs-r-devel] [R] R2WinBUGS and calling WinBUGS in Crossover MAC BETA

[Rodney S. <rsp...@hp...>]

Ahha... =20
Finally, something that I can answer.  If I'm at the terminal command =
prompt, and type:=20
open /Applications/OpenBUGS\ 2.2.0/winbugs.exe
then, first DarWINE starts, then XDarwin or whatever it is called, and =
then
OpenBUGS!!!

The Fonz gives Richie motorcycle riding advice
Fonzie:  ... where a helmet and never smile!=20
Richie:  Why not?
Fonzie:  You get bugs in your teeth



-----Original Message-----
From: Kenneth Benoit [mailto:kb...@tc...]
Sent: Tue 12/12/2006 4:42 PM
To: Rodney Sparapani
Cc: gre...@bf...; Ben Bolker; =
bug...@li...
Subject: Re: [R] R2WinBUGS and calling WinBUGS in Crossover MAC BETA
=20
Hi - That, plus the difficulty I encountered in getting Darwine to work=20
at all, led me to remove it and to install Crossover Mac Beta instead.=20
It works just great with WinBUGS 1.4, running it quickly and completely=20
*except* that first I have to start Crossover and then choose the=20
installed WinBUGS from the programs menu to start it.  (and then it pops =

right up and runs fine!)

So the only question seems to be: how to get it started from the command =

line which R2WinBUGS can call??

Ken


Rodney Sparapani wrote:
>=20
>> Rodney (can you please join to bugs-r development list) reported that =
he
>> was able to start OpenBUGS under Intel Mac, but not WinBUGS. Maybe he
>> can say more.=20
> Hi Guys:
>=20
> Couldn't really follow the discussion.  But, WinBUGS does not work =
with
> DarWINE, although, OpenBUGS does.  I'm using v. 0.9.21 DP, but this =
hasn't
> changed going back to about v. 0.9.10 DP.  And, before
> that OpenBUGS doesn't work either.
> I've spent a lot of time trying to
> figure it out, but it's madness.  WINE and R are written, more or =
less,
> from the Linux standpoint.  Compiling R even on industry-standard
> Solaris can be tricky and WINE on Solaris is virtually impossible.
> Mac OS X adds its own wrinkles.  Many of the infrastucture that R =
requires
> are already there, but often R chooses to install a slightly different
> compiler and/or library and you are pulling out your hair trying to=20
> figure out
> what you are supposed to do and why.  Of course, a professional Mac
> developer would figure this out in a couple of minutes, but we=20
> statisticians
> must suffer for our art :)
>=20
> And to add insult to injury, I tried to subscribe to the mailing list
> on sourceforge, but I couldn't figure it out.  There is this obnoxious
> adware that sourceforge employs that covers the search dialog.  No
> matter what I did in Firefox 2.0, I couldn't get past it.
>=20
> Rodney