Shoot. I was hopeful for that one. Did you do his instructions exactly? He said to use at least version 1.1.39. Do you think there has been a regression since then? The latest stable is supposed to be guaranteed to have no regressions (that's my understanding), but since Livezilla isn't in the App DB, I don't think the latest stable can guarantee to not regress Livezilla. Maybe you should dig up WINE 1.1.39.
Cheers,
Jake
LiveZilla
-
jjmckenzie
- Moderator
- Posts: 1153
- Joined: Wed Apr 27, 2011 11:01 pm
LiveZilla
On 5/28/11, SpawnHappyJake <[email protected]> wrote:
the student' to do regression testing. Neither Dan nor I have time to
do this for each application that has failed due to a regression.
Thus we ask the reporter to please do so, or find someone who can
properly run a regression. There are hundreds of changes just between
versions and thousands of changes between releases. I would estimate
the number of changes between 1.1.39 and the current release as 1.3.21
at about 5,000. Fortunately, regression testing using git does not
mean that you have to remove every change to figure out which one
caused the problem. See the Wiki Regression testing page on how to do
this. And the first and most important step is confirming that
LiveZilla works with Wine 1.1.39.
James McKenzie
Git has versions into the 0.9 region. However, it is an 'exercise forShoot. I was hopeful for that one. Did you do his instructions exactly? He
said to use at least version 1.1.39. Do you think there has been a
regression since then? The latest stable is supposed to be guaranteed to
have no regressions (that's my understanding), but since Livezilla isn't in
the App DB, I don't think the latest stable can guarantee to not regress
Livezilla. Maybe you should dig up WINE 1.1.39.
the student' to do regression testing. Neither Dan nor I have time to
do this for each application that has failed due to a regression.
Thus we ask the reporter to please do so, or find someone who can
properly run a regression. There are hundreds of changes just between
versions and thousands of changes between releases. I would estimate
the number of changes between 1.1.39 and the current release as 1.3.21
at about 5,000. Fortunately, regression testing using git does not
mean that you have to remove every change to figure out which one
caused the problem. See the Wiki Regression testing page on how to do
this. And the first and most important step is confirming that
LiveZilla works with Wine 1.1.39.
James McKenzie
Re: LiveZilla
what's confirming that livezilla works with wine? whoever who confirmed that please pretty please tell me how to do it in steps even million I don't mind what matters is it worksjjmckenzie wrote:On 5/28/11, SpawnHappyJake <[email protected]> wrote:Git has versions into the 0.9 region. However, it is an 'exercise forShoot. I was hopeful for that one. Did you do his instructions exactly? He
said to use at least version 1.1.39. Do you think there has been a
regression since then? The latest stable is supposed to be guaranteed to
have no regressions (that's my understanding), but since Livezilla isn't in
the App DB, I don't think the latest stable can guarantee to not regress
Livezilla. Maybe you should dig up WINE 1.1.39.
the student' to do regression testing. Neither Dan nor I have time to
do this for each application that has failed due to a regression.
Thus we ask the reporter to please do so, or find someone who can
properly run a regression. There are hundreds of changes just between
versions and thousands of changes between releases. I would estimate
the number of changes between 1.1.39 and the current release as 1.3.21
at about 5,000. Fortunately, regression testing using git does not
mean that you have to remove every change to figure out which one
caused the problem. See the Wiki Regression testing page on how to do
this. And the first and most important step is confirming that
LiveZilla works with Wine 1.1.39.
James McKenzie
-
SpawnHappyJake
- Level 5
- Posts: 272
- Joined: Sun Feb 06, 2011 5:57 am
Recap
Hi KhalidAl,
James McKenzie brings up an important point that "the first and most important step is confirming that LiveZilla works with Wine 1.1.39."
He did NOT say that it was confirmed, he said that it needs TO BE confirmed.
Let me recap what I've been doing in this thread. I saw that maybe the tips and tricks first mentioned weren't doing it for you (though now that I look back I'm not sure if you did them yet), and I also saw that Livezilla was not in the App DB (application database).
So I Googled to see if anyone, anywhere knew how to get Livezilla to work in WINE. I also Googled to see if there were any alternatives to Livezilla that would work natively in your operating system. A native alternative is usually better than trying to get a program to work in WINE, but there isn't always an alternative, as is the case with computer games.
I understand now that you can't have an alternative, and must have Livezilla. My first post in this thread had a link to a place on the Internet were I found a post by Batrams who said that he got Livezilla to work in WINE. I also posted links to and listed alternatives to Livezilla in my first post.
I don't think that Batrams was lying. He probably did get Livezilla to work in WINE. We don't know exactly what kernel version he got it working in, but we know he got it working in Linux in WINE. We also know that he was using an older version of WINE... 1.1.39 at its oldest.
Then you said that you couldn't have an alternative. You didn't say whether or not you tried Batram's instructions or not. I thought that maybe you didn't follow the link, so copy and pasted Batram's post here to make sure you'd see them.
Then you say you can't uninstall Livezilla, and I say to nuke your WINE. You have to install all these parts in a certain order anyways, so you had to start over from a clean slate.
Then you say "same error ferking verdana font Sad". I still don't know if you followed Batram's instructions exactly. Hoping that you did, I move on to the next logical conclusion: WINE used to work with Livezilla in an older WINE version, but the current WINE version does not. This is called a regression.
Then James McKenzie brings up an important point that "the first and most important step is confirming that LiveZilla works with Wine 1.1.39."
He didn't say that it was confirmed, he said that it needs to be confirmed.
So first, please tell us if you followed Batrams's instructions exactly. To do them, you first need to nuke (completely clear, as in delete) your WINE. Then you follow his instructions. Probably uninstall and reinstall WINE as well, beforehand. The reason why you have to start clean is that the instructions are order-sensitive.
Batrams specifically warned that if it isn't done it in the right order, it will complain about missing fonts. Now it's complaining about a missing font, Verdana. This makes me wonder if it was done out of order or if you did the instructions with some remnants left from before, and not starting clean.
Have you tried both winetricks corefonts and winetricks allfonts ? If you haven't done Batram's instructions yet, don't do these until after you did. They are order-sensitive.
I also don't know if you followed the other people's instructions of installing .net or mono via winetricks, either.
So, first try Batram's instructions with the lastest WINE. If that doesn't work, try WINE 1.1.39, because Batrams said it worked on that version. As James McKenzie said, it is very important to find out whether or not it works in that version. That way, we can start trying later versions to find the last version that it works in, and report the regression.
Before you try WINE 1.1.39, you have to nuke your WINE and start over. Delete the dot wine folder, and uninstall WINE. Then install WINE 1.1.39. Then follow Batrams's instructions again.
I'm not promising that this will work, but I would think that it would. Hopefully compatibility wasn't lost with a newer Linux kernel.
I'm assuming you're trying to get Livezilla to work in WINE in Linux? What verison of Linux? What kernel version? 32 bit or 64 bit?
I don't mean to sound condescending, but we need to know what you're doing. Clarification is key.
Cheers,
Jake
James McKenzie brings up an important point that "the first and most important step is confirming that LiveZilla works with Wine 1.1.39."
He did NOT say that it was confirmed, he said that it needs TO BE confirmed.
Let me recap what I've been doing in this thread. I saw that maybe the tips and tricks first mentioned weren't doing it for you (though now that I look back I'm not sure if you did them yet), and I also saw that Livezilla was not in the App DB (application database).
So I Googled to see if anyone, anywhere knew how to get Livezilla to work in WINE. I also Googled to see if there were any alternatives to Livezilla that would work natively in your operating system. A native alternative is usually better than trying to get a program to work in WINE, but there isn't always an alternative, as is the case with computer games.
I understand now that you can't have an alternative, and must have Livezilla. My first post in this thread had a link to a place on the Internet were I found a post by Batrams who said that he got Livezilla to work in WINE. I also posted links to and listed alternatives to Livezilla in my first post.
I don't think that Batrams was lying. He probably did get Livezilla to work in WINE. We don't know exactly what kernel version he got it working in, but we know he got it working in Linux in WINE. We also know that he was using an older version of WINE... 1.1.39 at its oldest.
Then you said that you couldn't have an alternative. You didn't say whether or not you tried Batram's instructions or not. I thought that maybe you didn't follow the link, so copy and pasted Batram's post here to make sure you'd see them.
Then you say you can't uninstall Livezilla, and I say to nuke your WINE. You have to install all these parts in a certain order anyways, so you had to start over from a clean slate.
Then you say "same error ferking verdana font Sad". I still don't know if you followed Batram's instructions exactly. Hoping that you did, I move on to the next logical conclusion: WINE used to work with Livezilla in an older WINE version, but the current WINE version does not. This is called a regression.
Then James McKenzie brings up an important point that "the first and most important step is confirming that LiveZilla works with Wine 1.1.39."
He didn't say that it was confirmed, he said that it needs to be confirmed.
So first, please tell us if you followed Batrams's instructions exactly. To do them, you first need to nuke (completely clear, as in delete) your WINE. Then you follow his instructions. Probably uninstall and reinstall WINE as well, beforehand. The reason why you have to start clean is that the instructions are order-sensitive.
Batrams specifically warned that if it isn't done it in the right order, it will complain about missing fonts. Now it's complaining about a missing font, Verdana. This makes me wonder if it was done out of order or if you did the instructions with some remnants left from before, and not starting clean.
Have you tried both winetricks corefonts and winetricks allfonts ? If you haven't done Batram's instructions yet, don't do these until after you did. They are order-sensitive.
I also don't know if you followed the other people's instructions of installing .net or mono via winetricks, either.
So, first try Batram's instructions with the lastest WINE. If that doesn't work, try WINE 1.1.39, because Batrams said it worked on that version. As James McKenzie said, it is very important to find out whether or not it works in that version. That way, we can start trying later versions to find the last version that it works in, and report the regression.
Before you try WINE 1.1.39, you have to nuke your WINE and start over. Delete the dot wine folder, and uninstall WINE. Then install WINE 1.1.39. Then follow Batrams's instructions again.
I'm not promising that this will work, but I would think that it would. Hopefully compatibility wasn't lost with a newer Linux kernel.
I'm assuming you're trying to get Livezilla to work in WINE in Linux? What verison of Linux? What kernel version? 32 bit or 64 bit?
I don't mean to sound condescending, but we need to know what you're doing. Clarification is key.
Cheers,
Jake
I don't even dare to quote what you wrote because it would turn the thread to a 10 pages one thanks for you effort to make things clearer...
Yeah I followed the instructions by Baram or so and no luck but I also believe I know nothing about regression how to do it and stuff all what I did is removed wine and re-installed it
Could you please tell me if possible how regression is done?
Yeah I followed the instructions by Baram or so and no luck but I also believe I know nothing about regression how to do it and stuff all what I did is removed wine and re-installed it
Could you please tell me if possible how regression is done?
-
SpawnHappyJake
- Level 5
- Posts: 272
- Joined: Sun Feb 06, 2011 5:57 am
Ok. Thank you. Did you delete the dot wine folder as well as uninstalling and reinstalling Wine? What version(s) of wine did you try?
What did it do? Did the Livezilla window at least pop-up? Same error as before? Complained about the font missing? Batrams said to do winetricks corefonts. So you did that. How about now doing a winetricks allfonts on top of that? Did you remember the wininet urlmon at the end?
Hope it gets working for you.
As far as the regression thing, I haven't done those. I just learned that there even was a regression list yesterday. James McKenzie told us.
The first step is to find a version of Wine that runs Livezilla. Doesn't have to run it perfectly. As long as Livezilla is usable. Even Batrams didn't get it working perfectly.
After we find a version of Wine where Livezilla works (along with winetricks and any other magic we have to throw at it), then we can start doing the regression dance.
DanKegel thought that winetricks ie7 might help.
Cheers,
Jake
What did it do? Did the Livezilla window at least pop-up? Same error as before? Complained about the font missing? Batrams said to do winetricks corefonts. So you did that. How about now doing a winetricks allfonts on top of that? Did you remember the wininet urlmon at the end?
Hope it gets working for you.
As far as the regression thing, I haven't done those. I just learned that there even was a regression list yesterday. James McKenzie told us.
The first step is to find a version of Wine that runs Livezilla. Doesn't have to run it perfectly. As long as Livezilla is usable. Even Batrams didn't get it working perfectly.
After we find a version of Wine where Livezilla works (along with winetricks and any other magic we have to throw at it), then we can start doing the regression dance.
DanKegel thought that winetricks ie7 might help.
Cheers,
Jake
I will do it when I finish my shift today I have deleted the folder yes and did everything apart from the urlmon because I didn't find it in winetricks I installed it from dlls.com and placed it in system32 and in the tutorial it said ie6 not ie7 but it doesn't matter I will do that as well I'm not bothered if there ain't smileys or bold/italic formats it's just to get it to work so I can remove windows hopefully by the way it complained of different font this time which is sans serif regular while I had it in fonts as micross.ttf tried to find it anywhere but I couldn't all of them were paid and so plus it might not even be the regular one that livezilla is complaining about..I would like to thank you guys every one in this community who's trying to help it's highly appreciated warm regards from warm EgyptSpawnHappyJake wrote:Ok. Thank you. Did you delete the dot wine folder as well as uninstalling and reinstalling Wine? What version(s) of wine did you try?
What did it do? Did the Livezilla window at least pop-up? Same error as before? Complained about the font missing? Batrams said to do winetricks corefonts. So you did that. How about now doing a winetricks allfonts on top of that? Did you remember the wininet urlmon at the end?
Hope it gets working for you.
As far as the regression thing, I haven't done those. I just learned that there even was a regression list yesterday. James McKenzie told us.
The first step is to find a version of Wine that runs Livezilla. Doesn't have to run it perfectly. As long as Livezilla is usable. Even Batrams didn't get it working perfectly.
After we find a version of Wine where Livezilla works (along with winetricks and any other magic we have to throw at it), then we can start doing the regression dance.
DanKegel thought that winetricks ie7 might help.
Cheers,
Jake
-
SpawnHappyJake
- Level 5
- Posts: 272
- Joined: Sun Feb 06, 2011 5:57 am
Egypt? How are you people? Heard you were shut out from the Internet for a while there.
Glad you're connected now. Thanks for the warm regards from warm Egypt. And I send my warm regards from the cool, moist, cloud-covered, southern Oregon Coast (part of the Pacific coast of USA).
I've always admired the Pyramids in Egypt and in Mexico. How did they build them?
Those pyramids are just as much of a mystery as Batrams getting Livezilla to work in WINE.
I'm not clear on what you said you installed/ acquired from dlls.com. By the way, when I go to dlls.com, it says that the domain name is up for sale.
Maybe it's time to try directly coping in font files.
When you get to it, don't forget to post the WINE version you are using.
Cheers,
Jake
Glad you're connected now. Thanks for the warm regards from warm Egypt. And I send my warm regards from the cool, moist, cloud-covered, southern Oregon Coast (part of the Pacific coast of USA).
I've always admired the Pyramids in Egypt and in Mexico. How did they build them?
Those pyramids are just as much of a mystery as Batrams getting Livezilla to work in WINE.
I'm not clear on what you said you installed/ acquired from dlls.com. By the way, when I go to dlls.com, it says that the domain name is up for sale.
Maybe it's time to try directly coping in font files.
When you get to it, don't forget to post the WINE version you are using.
Cheers,
Jake
I am afraid I built a pyramid of wines on top of one anotherSpawnHappyJake wrote:Egypt? How are you people? Heard you were shut out from the Internet for a while there.
Glad you're connected now. Thanks for the warm regards from warm Egypt. And I send my warm regards from the cool, moist, cloud-covered, southern Oregon Coast (part of the Pacific coast of USA).
I've always admired the Pyramids in Egypt and in Mexico. How did they build them?
Those pyramids are just as much of a mystery as Batrams getting Livezilla to work in WINE.
I'm not clear on what you said you installed/ acquired from dlls.com. By the way, when I go to dlls.com, it says that the domain name is up for sale.
Maybe it's time to try directly coping in font files.
When you get to it, don't forget to post the WINE version you are using.
Cheers,
Jake
I didn't mean dlls.com it was another website that offered free native dlls
I think I'm using the latest one to start with and then I removed it and installed the mentioned version with apt link thingy
Once I finish my shift for today I will remove all wine and winetricks and live zilla and start from scratch again do you know how to install urlmon because I didn't find it in the gui of winetricks thing not even by typing "sh winetricks urlmon" but I did it the way I mentioned downloaded the dll from a website and placed it in the wine system32 folder if that would do then it doesn't matter.
-
SpawnHappyJake
- Level 5
- Posts: 272
- Joined: Sun Feb 06, 2011 5:57 am
Honestly, I have no idea how to install "wininet urlmon". I'm just trying to bring what I'm hoping is a solution that I found in one forum, into this forum. I'm just a middleman bringing solutions to people, hopefully.
With a little Googling, it looks like I was actually talking about 2 things here. I thought "wininet urlmon" was one thing, but wininet appears to be one dll, and urlmon appears to be another dll. So I guess they are just dlls that you copy in. Where you copy them too, I don't know. You could run a search on a Windows partition and find out, provided they are installed.
Cheers,
Jake
With a little Googling, it looks like I was actually talking about 2 things here. I thought "wininet urlmon" was one thing, but wininet appears to be one dll, and urlmon appears to be another dll. So I guess they are just dlls that you copy in. Where you copy them too, I don't know. You could run a search on a Windows partition and find out, provided they are installed.
Cheers,
Jake
-
jjmckenzie
- Moderator
- Posts: 1153
- Joined: Wed Apr 27, 2011 11:01 pm
Jake:SpawnHappyJake wrote:Honestly, I have no idea how to install "wininet urlmon". I'm just trying to bring what I'm hoping is a solution that I found in one forum, into this forum. I'm just a middleman bringing solutions to people, hopefully.
A script, written by Dan Kegel and maintained by Dan and others, is called winetricks. There is a Wiki page just for it, detailing how to obtain and use it.
For example: To install wininet and set its dlls to native you would use
winetricks wininet.
The script has grown a bit since first conceived and it actually helps install programs as well now.
Maybe, a little familiarity with the tools used to help with Wine would be in order now.
Also, Google is NOT your friend when dealing with Wine problems. There are solutions out there that are not needed anymore and some that are plain dangerous (they can cause massive amounts of hair removal through pulling...)
I always recommend using the Applications Database FIRST. If there is no entry, then add one with the current state of affairs for the program. As you find solutions, add them. As you find functionality changes with different versions of Wine, update the entry. Take a program that is not in the database, add it and become a maintainer. This helps Wine greatly and the best thing that a non-programmer could do for Wine.
And for all of your suggestions here on the Forums, thank you.
Now back to my regularly scheduled programming on Wine.
-
SpawnHappyJake
- Level 5
- Posts: 272
- Joined: Sun Feb 06, 2011 5:57 am
Dlls Found
Hi KhalidAl!
To confirm you, I just searched my Win XP partition, and urlmon.dll and wininet.dll are both in the system32 folder. C:\WINDOWS\system32 in my case.
Did you try "sh winetricks wininet" yet? I know you said "sh winetricks urlmon" didn't work for you, but maybe the other will.
Cheers,
Jake
To confirm you, I just searched my Win XP partition, and urlmon.dll and wininet.dll are both in the system32 folder. C:\WINDOWS\system32 in my case.
Did you try "sh winetricks wininet" yet? I know you said "sh winetricks urlmon" didn't work for you, but maybe the other will.
Cheers,
Jake
Guys I think I'm completely messed I've downloaded the version that some people said it works it's a bz2 tar file but the only thing I think it's like a source code of wine that I need to compile myself but it was called development version...Anyway I downloaded the tar and uncompressed it and then ran the ./configure thing to compile it it required flex and bison no problem installed them now what? I don't see any gui for wine or something
I don't see any gui for wine or something-
SpawnHappyJake
- Level 5
- Posts: 272
- Joined: Sun Feb 06, 2011 5:57 am
A GUI Mess? No. A CLI (silly) Mess.
What happens if you go to terminal and do:
wine winecfg.exe
?
Step two would be making sure you succeeded in compiling WINE from source. Go to terminal and do "wine --version". Is this the version you compiled?
Next try would be to do this in terminal:
cd [path to where you hope you succeeded in compiling WINE]
wine --version
Does it even output the wine version? If so, is this the version you compiled from source?
If you have more than one version of WINE present, make sure you use them with different WINEPREFIXES.
Here is an EXCELLENT howto on how to use WINEPREFIXES:
http://forum.winehq.org/viewtopic.php?t=2501&highlight=
If you use WINEPREFIXES, every time you want to run a program in WINE (except for the possible exception of with one version of wine and one default WINEPREFIX with that one version of WINE), you have to run a program through terminal, or a launcher or something that sets the WINEPREFIX - every time.
Please note that I haven't compiled WINE from source, but I have compiled other things from source, and I can say a few things that should apply.
The tar.bz2 file is the source code. They like to call those tarballs.
Did you succeed in compiling WINE from source? Did you do "make install"? Did you have any other versions of WINE installed at the time you compiled? If you succeeded in compiling WINE from source, but didn't do "make install", you will have to run it out of the folder you compiled it in; it isn't copied over to where Linux looks by default when you tell it to run a program. So if you compiled WINE from source, but didn't do "make install", and had no other versions of WINE present on the system, and went to a new terminal and just entered "wine", it would say that it can't find anything to run called "wine". If you changed the directory of terminal to where you compiled it, and THEN entered "wine", it would output the wine help (default parameter when no other parameters are specified). Doing a "make install", from the directory of where you compiled WINE, copies WINE over to where Linux looks by default to run a program, and then you could just enter "wine" in a new terminal and it would output the wine help. At that point you can delete the folder you compiled wine in.
Please note that your package manager is not aware of any program you compiled from source. So you cannot use Synaptic to remove WINE that you compiled. You have to delete it manually.
I believe there is a prefix option that lets you say where you want WINE to go after you compile it and do "make install", so that one version of WINE can be in one place, and another version of WINE can be in another place. Don't confuse this with WINEPREFIX, which lets you have different WINE "drive_C + registry" folders, which you will wind up wanting to do, I'm sure.
I don't think compiling WINE from source would put all those shortcuts in your main menu, unless "make install" does that. It's possible that you compiled a version of WINE that doesn't have a GUI (for configuration).
I just installed Linux Mint 11 64 bit on my computer yesterday and am getting that all set up. Hopefully I can help better by actually having WINE and Linux and being able to test some things.
Hey, quick question: If you install WINE through MacPorts, does that make it Port Wine?
That last one was a joke, for those that didn't get it.
Yeah, I've had this computer for 6 years, and just this year found out it is a 64 bit computer by accident. It came with 32 bit WinXP. When booted in a 32 bit OS, the processor reports itself as 32 bit. So that's what I thought it was. So when I switched to Linux, I installed 32 bit Linux. HardInfo (in Linux) consequently still said "32 bit".
wine winecfg.exe
?
Step two would be making sure you succeeded in compiling WINE from source. Go to terminal and do "wine --version". Is this the version you compiled?
Next try would be to do this in terminal:
cd [path to where you hope you succeeded in compiling WINE]
wine --version
Does it even output the wine version? If so, is this the version you compiled from source?
If you have more than one version of WINE present, make sure you use them with different WINEPREFIXES.
Here is an EXCELLENT howto on how to use WINEPREFIXES:
http://forum.winehq.org/viewtopic.php?t=2501&highlight=
If you use WINEPREFIXES, every time you want to run a program in WINE (except for the possible exception of with one version of wine and one default WINEPREFIX with that one version of WINE), you have to run a program through terminal, or a launcher or something that sets the WINEPREFIX - every time.
Please note that I haven't compiled WINE from source, but I have compiled other things from source, and I can say a few things that should apply.
The tar.bz2 file is the source code. They like to call those tarballs.
Did you succeed in compiling WINE from source? Did you do "make install"? Did you have any other versions of WINE installed at the time you compiled? If you succeeded in compiling WINE from source, but didn't do "make install", you will have to run it out of the folder you compiled it in; it isn't copied over to where Linux looks by default when you tell it to run a program. So if you compiled WINE from source, but didn't do "make install", and had no other versions of WINE present on the system, and went to a new terminal and just entered "wine", it would say that it can't find anything to run called "wine". If you changed the directory of terminal to where you compiled it, and THEN entered "wine", it would output the wine help (default parameter when no other parameters are specified). Doing a "make install", from the directory of where you compiled WINE, copies WINE over to where Linux looks by default to run a program, and then you could just enter "wine" in a new terminal and it would output the wine help. At that point you can delete the folder you compiled wine in.
Please note that your package manager is not aware of any program you compiled from source. So you cannot use Synaptic to remove WINE that you compiled. You have to delete it manually.
I believe there is a prefix option that lets you say where you want WINE to go after you compile it and do "make install", so that one version of WINE can be in one place, and another version of WINE can be in another place. Don't confuse this with WINEPREFIX, which lets you have different WINE "drive_C + registry" folders, which you will wind up wanting to do, I'm sure.
I don't think compiling WINE from source would put all those shortcuts in your main menu, unless "make install" does that. It's possible that you compiled a version of WINE that doesn't have a GUI (for configuration).
I just installed Linux Mint 11 64 bit on my computer yesterday and am getting that all set up. Hopefully I can help better by actually having WINE and Linux and being able to test some things.
Hey, quick question: If you install WINE through MacPorts, does that make it Port Wine?
That last one was a joke, for those that didn't get it.
Yeah, I've had this computer for 6 years, and just this year found out it is a 64 bit computer by accident. It came with 32 bit WinXP. When booted in a 32 bit OS, the processor reports itself as 32 bit. So that's what I thought it was. So when I switched to Linux, I installed 32 bit Linux. HardInfo (in Linux) consequently still said "32 bit".
Re: A GUI Mess? No. A CLI (silly) Mess.
Jeepers man it took me quite sometime reading that but it's awesome I have downloaded the version that worked with livezilla or other peeps said it did 1.1.39 or so and I have compiled it but I didn't make and make install yet will need to wait till daily shift is done again and try if it doesn't have a gui it makes life more harderSpawnHappyJake wrote:What happens if you go to terminal and do:
wine winecfg.exe
?
Step two would be making sure you succeeded in compiling WINE from source. Go to terminal and do "wine --version". Is this the version you compiled?
Next try would be to do this in terminal:
cd [path to where you hope you succeeded in compiling WINE]
wine --version
Does it even output the wine version? If so, is this the version you compiled from source?
If you have more than one version of WINE present, make sure you use them with different WINEPREFIXES.
Here is an EXCELLENT howto on how to use WINEPREFIXES:
http://forum.winehq.org/viewtopic.php?t=2501&highlight=
If you use WINEPREFIXES, every time you want to run a program in WINE (except for the possible exception of with one version of wine and one default WINEPREFIX with that one version of WINE), you have to run a program through terminal, or a launcher or something that sets the WINEPREFIX - every time.
Please note that I haven't compiled WINE from source, but I have compiled other things from source, and I can say a few things that should apply.
The tar.bz2 file is the source code. They like to call those tarballs.
Did you succeed in compiling WINE from source? Did you do "make install"? Did you have any other versions of WINE installed at the time you compiled? If you succeeded in compiling WINE from source, but didn't do "make install", you will have to run it out of the folder you compiled it in; it isn't copied over to where Linux looks by default when you tell it to run a program. So if you compiled WINE from source, but didn't do "make install", and had no other versions of WINE present on the system, and went to a new terminal and just entered "wine", it would say that it can't find anything to run called "wine". If you changed the directory of terminal to where you compiled it, and THEN entered "wine", it would output the wine help (default parameter when no other parameters are specified). Doing a "make install", from the directory of where you compiled WINE, copies WINE over to where Linux looks by default to run a program, and then you could just enter "wine" in a new terminal and it would output the wine help. At that point you can delete the folder you compiled wine in.
Please note that your package manager is not aware of any program you compiled from source. So you cannot use Synaptic to remove WINE that you compiled. You have to delete it manually.
I believe there is a prefix option that lets you say where you want WINE to go after you compile it and do "make install", so that one version of WINE can be in one place, and another version of WINE can be in another place. Don't confuse this with WINEPREFIX, which lets you have different WINE "drive_C + registry" folders, which you will wind up wanting to do, I'm sure.
I don't think compiling WINE from source would put all those shortcuts in your main menu, unless "make install" does that. It's possible that you compiled a version of WINE that doesn't have a GUI (for configuration).
I just installed Linux Mint 11 64 bit on my computer yesterday and am getting that all set up. Hopefully I can help better by actually having WINE and Linux and being able to test some things.
Hey, quick question: If you install WINE through MacPorts, does that make it Port Wine?
That last one was a joke, for those that didn't get it.
Yeah, I've had this computer for 6 years, and just this year found out it is a 64 bit computer by accident. It came with 32 bit WinXP. When booted in a 32 bit OS, the processor reports itself as 32 bit. So that's what I thought it was. So when I switched to Linux, I installed 32 bit Linux. HardInfo (in Linux) consequently still said "32 bit".
thanks for your help but I don't know why would I need to set prefix or is it a must to configure it and I'm on 32bit laptop with 32 bit natty 11.04-
jjmckenzie
- Moderator
- Posts: 1153
- Joined: Wed Apr 27, 2011 11:01 pm
LiveZilla
On 6/3/11, KhalidAl <[email protected]> wrote:
ask elsewhere for assistance.
Since this is outside the scope of this project, you are going to haveGuys I've compiled it successfully but as root [Laughing]
Is there anyway to carry on running it without the error of missing x11
driver as I'm a root I searched all the forums and that's how I knew it's
from running it as a root user or can I even share it through root so I can
run it through another user?
ask elsewhere for assistance.
-
jjmckenzie
- Moderator
- Posts: 1153
- Joined: Wed Apr 27, 2011 11:01 pm
LiveZilla
On 6/3/11, KhalidAl <[email protected]> wrote:
to get XQuartz because it is a known problem and has a workaround/fix.
In your case, you may have to add your user to the video group. That
may fix the problem, but it is a workaround. All users should be able
to touch X11, not just root, That would be the 'final' fix. My
comment was directed at that, not a solution. I don't use Linux (yet)
and thus could not address your concern.
A search of the forums and the use of our friend Google is in order at
this point. (Yes, this has been encountered before.)
Fixing the root problem with X11 is not. We recommend to MacOSX usersIt's completely in the scope because that's the result of following some of
the instructions
to get XQuartz because it is a known problem and has a workaround/fix.
In your case, you may have to add your user to the video group. That
may fix the problem, but it is a workaround. All users should be able
to touch X11, not just root, That would be the 'final' fix. My
comment was directed at that, not a solution. I don't use Linux (yet)
and thus could not address your concern.
A search of the forums and the use of our friend Google is in order at
this point. (Yes, this has been encountered before.)
Re: LiveZilla
Man do you actually think that I would know that it's because of using the user root if I havn't searched the error was just saying it can't find the x11 driver and that's it so yeah I did search I'm not demanding anything but just to bear with me till I get it working I've never used this version so I can't find any docs/support apart from here so if you don't mind tell me how to add root to the video usersjjmckenzie wrote:On 6/3/11, KhalidAl <[email protected]> wrote:Fixing the root problem with X11 is not. We recommend to MacOSX usersIt's completely in the scope because that's the result of following some of
the instructions
to get XQuartz because it is a known problem and has a workaround/fix.
In your case, you may have to add your user to the video group. That
may fix the problem, but it is a workaround. All users should be able
to touch X11, not just root, That would be the 'final' fix. My
comment was directed at that, not a solution. I don't use Linux (yet)
and thus could not address your concern.
A search of the forums and the use of our friend Google is in order at
this point. (Yes, this has been encountered before.)
-
jjmckenzie
- Moderator
- Posts: 1153
- Joined: Wed Apr 27, 2011 11:01 pm
LiveZilla
On 6/5/11 7:27 AM, KhalidAl wrote:
Since this is outside of Wine's domain, I'm going to ask that you use
Google and your Linux distribution's forums. I did recommend that you
look at the forum as this has been encountered before and I did not and
should not provide this answer (I'm not a Linux user and MacOSX does not
suffer from this problem.)
You don't add root to the video users group, you add the normal user.jjmckenzie wrote:
do you actually think that I would know that it's because of using the
user root if I havn't searched the error was just saying it can't find
the x11 driver and that's it so yeah I did search I'm not demanding
anything but just to bear with me till I get it working I've never
used this version so I can't find any docs/support apart from here so
if you don't mind tell me how to add root to the video users
Since this is outside of Wine's domain, I'm going to ask that you use
Google and your Linux distribution's forums. I did recommend that you
look at the forum as this has been encountered before and I did not and
should not provide this answer (I'm not a Linux user and MacOSX does not
suffer from this problem.)
Re: LiveZilla
Well then we can wait for a WINE user who has been using linux I'm not requiring information on how to do it on a specific distro all what I need to know is how to compile and run an application on this version while I'm doing that I got a WINE output error which I believe so if for this community because not every one from my distro community needs to do or has done what I'm trying to dojjmckenzie wrote:On 6/5/11 7:27 AM, KhalidAl wrote:You don't add root to the video users group, you add the normal user.jjmckenzie wrote:
do you actually think that I would know that it's because of using the
user root if I havn't searched the error was just saying it can't find
the x11 driver and that's it so yeah I did search I'm not demanding
anything but just to bear with me till I get it working I've never
used this version so I can't find any docs/support apart from here so
if you don't mind tell me how to add root to the video users
Since this is outside of Wine's domain, I'm going to ask that you use
Google and your Linux distribution's forums. I did recommend that you
look at the forum as this has been encountered before and I did not and
should not provide this answer (I'm not a Linux user and MacOSX does not
suffer from this problem.)
-
Martin Gregorie
LiveZilla
On Wed, 2011-06-08 at 06:05 -0500, KhalidAl wrote:
to set the permissions for groups, users and files. This is general
Linux knowledge, not specific to any particular distro.
Using Wine needs more knowledge than how to click icons on the desktop,
so you have some learning to do.
If you're a power Windows user (i.e. can use its command line and know
more than just clicking buttons and expecting things to 'just happen')
getting a copy of "Linux in a nut shell", and looking up stuff as you
need it will see you right, but the book does assume that you're up to
speed with at least one other OS and can use a command line. If this
isn't you, you're better off with a book that explains the basics:
"Linux for Dummies" is generally well regarded for a complete Linux and
OS newbie.
Martin
What you need to find out how the Linux permission systems works and howjjmckenzie wrote:Well then we can wait for a WINE user who has been using linux I'm notOn 6/5/11 7:27 AM, KhalidAl wrote:
You don't add root to the video users group, you add the normal user.jjmckenzie wrote:
do you actually think that I would know that it's because of using the
user root if I havn't searched the error was just saying it can't find
the x11 driver and that's it so yeah I did search I'm not demanding
anything but just to bear with me till I get it working I've never
used this version so I can't find any docs/support apart from here so
if you don't mind tell me how to add root to the video users
Since this is outside of Wine's domain, I'm going to ask that you use
Google and your Linux distribution's forums. I did recommend that you
look at the forum as this has been encountered before and I did not and
should not provide this answer (I'm not a Linux user and MacOSX does not
suffer from this problem.)
requiring information on how to do it on a specific distro all what I
need to know is how to compile and run an application on this version
while I'm doing that I got a WINE output error which I believe so if
for this community because not every one from my distro community
needs to do or has done what I'm trying to do [Crying or Very sad]
to set the permissions for groups, users and files. This is general
Linux knowledge, not specific to any particular distro.
Using Wine needs more knowledge than how to click icons on the desktop,
so you have some learning to do.
If you're a power Windows user (i.e. can use its command line and know
more than just clicking buttons and expecting things to 'just happen')
getting a copy of "Linux in a nut shell", and looking up stuff as you
need it will see you right, but the book does assume that you're up to
speed with at least one other OS and can use a command line. If this
isn't you, you're better off with a book that explains the basics:
"Linux for Dummies" is generally well regarded for a complete Linux and
OS newbie.
Martin
Thanks for your reply could you please tell me how to completely uninstall it?dimesio wrote:You are not supposed to compile as root; only "make install" is done as root.KhalidAl wrote:Guys I've compiled it successfully but as root
Uninstall the version you compiled as root and build Wine as a normal user.
