Need help opening win prog in Mac/wine

[PatS]

`

Hi, need help opening win program. Other win progs don't seem to have a prob, or a winelog file opens to state "fix". Running Mac snow leopard 10.6.8, installed Wine 1.4.1 ..... Program having prob with is GAB (Guitar and Bass) written for Win by Gabriel Fernandez, download Guitar and Bass at: http://gfsoftware.com/glb_downloads.html ..... Mr. Fernandez told me if anyone can't figure this out to feel free to "contact him for inner workings of his software", his contact email is at the same address. I went through all the winetricks with him (and a linux? user/expert of Wine), successfully loaded all winetricks, but we couldn't figure it out, still didn't work. Was suggested I come here where a Mac user of Wine might be able to figure this out. The program GAB opens in Wine, but 2 dialogue windows pop up (preventing it from working fully). The 1st says "attempted to read or write protected memory". If I hit "continue" instead of quit program the 2nd box says something about "objects". Here is a screenshot of the 2 dialogue boxes: ok, they won't paste on this screen, am trying "upload attachment": ok, i can't get this into a format that will let me upload it.

Soooo.... If anyone running Mac/Wine can download this music program and run it on 1.4.1 hopefully you will get the same dialogue boxes when it opens and be able to help.

Suggestions of winetricks which I successfully loaded but didn't seem to work included ie6, winxp, dotnet20, directmusic, directplay, dmsynth, dsound... After that didn't work, one of the last suggestions from Mr. Fernandez was:

"I checked the screenshots. The problem is when GAB tries to load it's direct music wrapper library.
Try checking all the options related to DirectX in wine."

I tried that, that didn't work either.


Ok, that's my story, and I'm sticking to it...



Thanks for any and all help ahead of time.


Regards,

Pat


`

[dimesio]

`
Soooo.... :| If anyone running Mac/Wine can download this music program and run it on 1.4.1

1.4.1 is old; try the latest development release, currently 1.5.13.

[PatS]

ok, thanks for reply, I will give that a try, yet being a complete "compiling" non-adept, could use some pointers how to install 1.5.13 on mac 1.6.8 running snow leopard. went to http://www.winehq.org/download/ , and I see several downloads there, debian, redhat etc, which do I use for Mac... and... when I download the correct one, is there a particular wine-page that will help walk me through something I have no clue how to do....? Thanks in advance for the help...

Pat

[doh123]

ok, thanks for reply, I will give that a try, yet being a complete "compiling" non-adept, could use some pointers how to install 1.5.13 on mac 1.6.8 running snow leopard. went to http://www.winehq.org/download/ , and I see several downloads there, debian, redhat etc, which do I use for Mac... and... when I download the correct one, is there a particular wine-page that will help walk me through something I have no clue how to do....? Thanks in advance for the help...

Pat

try getting macports.... makes it easy. I'm assuming your 1.4.1 trial wasn't normal Wine, but probably WineBottler...

With MacPorts you just need to install Xcode, then with MacPorts it will download and compile everything you need for Wine and you'll be ready to use it. Just recall that Macports... and all of normal Wine usage in OSX is all in Terminal, there is no GUI integration for Wine itself.

[PatS]

try getting macports.... makes it easy. I'm assuming your 1.4.1 trial wasn't normal Wine, but probably WineBottler...

With MacPorts you just need to install Xcode, then with MacPorts it will download and compile everything you need for Wine and you'll be ready to use it. Just recall that Macports... and all of normal Wine usage in OSX is all in Terminal, there is no GUI integration for Wine itself.

Ok, attempting intelligent reply [w/questions]


First, ok, originally searched "download wine", downloaded it, screen popped up showing both wine and winebottler, I guess I unknowledgedly slid them both into "Applications". Able to operate most Windows progs by bringing up Wine "FileManager" [and using Winetricks] and simply clicking on installed desired .exe file.

Question 1: After I do Macports, Xcode etc, and (hopefully) install Wine properly, will I still be able to open Wine FileManager and click on exe files to run progs, are am I (mis)understanding that after I (miraculously) properly do the Wine 1.5.13 install I will have to open all files from Terminal? [again, unknowledgeable newbie here] [never worked with a "Terminal" ].

Second, found Macports, can get that, if Xcode isn't on my "ancient macbook" disk (some places say it is) [http://www.davidbaumgold.com/tutorials/wine-mac/ someone give this guy a job, heh...] then i have to get a developers account w/Apple, found it there, 4 gigs, no prob.

2nd question: Is there a simple command that will "uninstall" all current Wine/Winebottler off my system...?

Appreciate the assistance from people. I'm sure I'm neither the first nor last newbie here with questions.

Thanks all for the patience and guidance. Greatly appreciated.


Pat




"Knowledge is smart. Wisdom is his accountant."

[doh123]

Question 1: After I do Macports, Xcode etc, and (hopefully) install Wine properly, will I still be able to open Wine FileManager and click on exe files to run progs, are am I (mis)understanding that after I (miraculously) properly do the Wine 1.5.13 install I will have to open all files from Terminal? [again, unknowledgeable newbie here] [never worked with a "Terminal" ].

its command line, but you could also just run winefile from command line as well then double click your exe file sure... thats possible...
typing in...
wine winefile
should do it, but most people just launch the program directly from terminal instead of launching winefile

2nd question: Is there a simple command that will "uninstall" all current Wine/Winebottler off my system...?

WineBottler along with all other 3rd party apps that may use Wine aren't supported here. I don't use it myself so I have no idea if there is any uninstall tool, but I'd assume you could trash the WineBottler and Wine apps, then you need to delete the main "wineprefix" that it created (I guess it created) so that normal Wine can use it for default too. by default Wine will use ~/.wine ... which means in your home folder a folder named .wine is made where your registry files and drive_c and stuff for Wine will be found. Like normal Unix, starting with a . on the folder means its hidden, so Finder won't see it unless you've taken extra steps to view hidden files. If you want to delete your wineprefix, you can always do a...
rm -rf ~/.wine
just make sure you type that exactly right, because you do not want to delete something else by mistake...
it may be safer to delete it through Finder instead.
type
open ~/.wine
in Terminal, and it will show it in a Finder window even though its hidden and you can do it in Finder.


Getting down normal Wine usage can be difficult. Thats why 3rd party programs exist like Crossover, Wineskin, WineBottler, PlayOnMac, etc... that all use Wine. If you choose to use any of those, they have their own avenue of support and not this forum.

[PatS]

Question 1: After I do Macports, Xcode etc, and (hopefully) install Wine properly, will I still be able to open Wine FileManager and click on exe files to run progs, are am I (mis)understanding that after I (miraculously) properly do the Wine 1.5.13 install I will have to open all files from Terminal? [again, unknowledgeable newbie here] [never worked with a "Terminal" ].

its command line, but you could also just run winefile from command line as well then double click your exe file sure... thats possible...
typing in...
wine winefile
should do it, but most people just launch the program directly from terminal instead of launching winefile

2nd question: Is there a simple command that will "uninstall" all current Wine/Winebottler off my system...?

WineBottler along with all other 3rd party apps that may use Wine aren't supported here. I don't use it myself so I have no idea if there is any uninstall tool, but I'd assume you could trash the WineBottler and Wine apps, then you need to delete the main "wineprefix" that it created (I guess it created) so that normal Wine can use it for default too. by default Wine will use ~/.wine ... which means in your home folder a folder named .wine is made where your registry files and drive_c and stuff for Wine will be found. Like normal Unix, starting with a . on the folder means its hidden, so Finder won't see it unless you've taken extra steps to view hidden files. If you want to delete your wineprefix, you can always do a...
rm -rf ~/.wine
just make sure you type that exactly right, because you do not want to delete something else by mistake...
it may be safer to delete it through Finder instead.
type
open ~/.wine
in Terminal, and it will show it in a Finder window even though its hidden and you can do it in Finder.


Getting down normal Wine usage can be difficult. Thats why 3rd party programs exist like Crossover, Wineskin, WineBottler, PlayOnMac, etc... that all use Wine. If you choose to use any of those, they have their own avenue of support and not this forum.

Alright, this is going to be an interesting experience.

I'll use MacPorts, rather have communication with the knowledgeable people here.

One question I forgot to ask, where and which Wine should I download. Again, I went to the downloads section and there are several ones there for Redhat etc, I don't have the knowledge yet about which one to download.

If you can steer me right on that, already put Xcode on the Mac from system disk, probably close to ready to begin, just need the right Wine file to download to get started.

Thank you (all) for your time and consideration. I'll post back here if it all actually works, heh.

Greatly appreciated.


Pat

[doh123]

One question I forgot to ask, where and which Wine should I download. Again, I went to the downloads section and there are several ones there for Redhat etc, I don't have the knowledge yet about which one to download.

no where... Macports handles it for you.

the macports command you'll want is

port install wine-devel

wine-devel is the latest development version, if you just try normal Wine it'll give 1.4.1. But Macports will download the source and build it for you, along with everything else you need... all automated.

[PatS]

One question I forgot to ask, where and which Wine should I download. Again, I went to the downloads section and there are several ones there for Redhat etc, I don't have the knowledge yet about which one to download.

no where... Macports handles it for you.

the macports command you'll want is

port install wine-devel

wine-devel is the latest development version, if you just try normal Wine it'll give 1.4.1. But Macports will download the source and build it for you, along with everything else you need... all automated.

Ok, got everything installed (one presumes), xcode, x11, macports... went into terminal, typed port install wine-devel .....it returned this message:

Error: Insufficient privileges to write to MacPorts install prefix.

I'm sure it's a simple fix, I just haven't been able to figure it out yet.


Pat

[PatS]

ok, i found some site that said enter into terminal:

port search wine ..... did that.... brought up 6 things including wine-devel

entered: sudo port install wine-devel .....asked for my password.... entered it....

am now watching terminal screen attempting downloads/installs of various things...

ok, guess i'm on my way.... yes....?


Regards,

Pat

[PatS]

ok, I've never seen so much fetching verifying extracting configuring building staging installing activating and cleaning in my life... heh....

still working and scrolling Question: got 2 messages in terminal so far, let me know if it's advisable to do what these say (when this reaches the end):

# Startup items have been generated that will aid in
# starting dbus with launchd. They are disabled
# by default. Execute the following command to start them,
# and to cause them to launch at startup:
#
# sudo launchctl load -w /Library/LaunchDaemons/org.freedesktop.dbus-system.plist
# launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist

and:

To make python 2.7 the default (i.e. the version you get when you run 'python'), please run:

sudo port select --set python python27


Regards,

Pat

[PatS]

Update: Ok, took care of all that (above). Macports installed. Automated (successful) install of wine-devel.

Now, apparently, comes the hard part. So, tried to (re)install one of my Windows programs (that I had previously installed on 1.4.1). [Learning "terminal" isn't as easy as it looks.] The install file executed, window popped up "you need to install mono-0.0.4.msi".

Downloaded mono-0.0.4.msi ..... attempted to install. And, ok, I'm an ignorant *newbie*, hmmm.

So I admit, I have no idea how to do anything.

Have the wine-mono-0.0.4.msi in my downloads directory. So tried (from WineHQ faq):

wine msiexec /i wine-mono-0.0.4.msi

This is what I got back:

fixme:storage:create_storagefile Storage share mode not implemented.
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot

I know I'm missing something simple, but it's complex to one such as I, heh... and making mistakes doing this, and not knowing how to correct them, eventually eats my brain.

In 1.4.1 it was all graphical interfaces, download file, hit it, it would install to the right place (normally) or bring up log screen saying which directory to place it in.

I was able to go into a vast directory, heh, and bring up a Winetricks screen, it appears there are about 40? less options on that screen than in this devel.

Love it tho... was amazing to watch it all unfolding (loading/installing) in "terminal"... took a few hours... can't imagine learning how to "compile from scratch"... am learning... just limping along tho....


Any help appreciated.


Pat

[doh123]

Update: Ok, took care of all that (above). Macports installed. Automated (successful) install of wine-devel.

Now, apparently, comes the hard part. So, tried to (re)install one of my Windows programs (that I had previously installed on 1.4.1). [Learning "terminal" isn't as easy as it looks.] The install file executed, window popped up "you need to install mono-0.0.4.msi".

Downloaded mono-0.0.4.msi ..... attempted to install. And, ok, I'm an ignorant *newbie*, hmmm.

So I admit, I have no idea how to do anything.

Have the wine-mono-0.0.4.msi in my downloads directory. So tried (from WineHQ faq):

wine msiexec /i wine-mono-0.0.4.msi

This is what I got back:

fixme:storage:create_storagefile Storage share mode not implemented.
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot

I know I'm missing something simple, but it's complex to one such as I, heh... and making mistakes doing this, and not knowing how to correct them, eventually eats my brain.

In 1.4.1 it was all graphical interfaces, download file, hit it, it would install to the right place (normally) or bring up log screen saying which directory to place it in.

I was able to go into a vast directory, heh, and bring up a Winetricks screen, it appears there are about 40? less options on that screen than in this devel.

Love it tho... was amazing to watch it all unfolding (loading/installing) in "terminal"... took a few hours... can't imagine learning how to "compile from scratch"... am learning... just limping along tho....


Any help appreciated.


Pat

Its all a great learning experience. I get kind fed up with it all so made all my own build tools and made Wineskin to be a porting tool, then decided share it with others... its a lot easier to use in some ways, but its still not "normal wine" so its not supported here, but it makes my life a lot easier You can check it out if you want to, but its kind of fun to learn it all from the source code, compiling, and command line perspective.

Wine 1.4.1 is actually exactly the same as what you just did... you were using WineBottler before, not Wine itself. There is always confusion there because the guy who makes WineBottler decided to call his main app that houses Wine just "Wine.app" so a lot of people end up thinking that its normal Wine when its not.

Not sure on the Mono thing... normally if mine needs Mono, it prompts me and lets me download and install all right there, no extra steps needed. Did you make sure you deleted the ~/.wine folder that WineBottler made, so its not trying to use the old one... could be causing problems.