Re: [Cooker] [discuss] wine configuration
. > > > Easy wine configuration stuff should happen at some point; I just don't think > it should be quite yet. > The easiest WINE config would be : 1. A config file pre-configured for a dual-boot computer with the assumption that Windows is installed in a standard way on drive C:\ (Perhaps a CD-ROM could be configured for r:\?) -- /etc/wine.conf.windows 2. A config file pre-configured for a Linux-only computer with no Windows installed -- /etc/wind.conf.linux 3. The "stock" config file -- /etc/wine.conf.default. If WINE is selected for install, a post-install script could select from one of the three, copying it to /etc/wine.conf - it could even check for the presence of C:\ and make the choice automatically. Then WINE would run "out of the box". If the user later upgraded, then they would have to determine if /etc/wine.conf was appropriately configured, but at least they would have a starting point. I would also suggest that each config file include a few examples of how to run, from the command line, a few typically-installed Windows programs, especially those in C:\Program Files (that funky syntax). If WINE is installed, adding commonly installed programs to AppFinder and adding them to the menu automatically would be even nicer. Hoyt
Re: [Cooker] [discuss] wine configuration
On Mon, May 29, 2000 at 08:22:20AM +0300, ron peake wrote: > Hi > Corel's Office 2000 for Linux is based on Wine and runs fine at > least on RH6,1. (No time available to install on Mandrake 7,02 as > yet, but I will do it.) > No crashes, no lockups, no problems. It seems rather stable to me. I've heard of some issues about Corel Office, but there are a few points to make beside that: 1) Corel's version of Wine is not the same as the Wine project. Corel forked an existing version of Wine and worked on it in-house for a few months. A few months ago they gave people read-access to their CVS tree, but patches must still be extracted from their version. (BTW, Wine has a BSD license, so there's no legal problem with this) 2) The wine configuration file and command-line prompts are still in flux; for example, in Wine 2430 the "-managed" command-line option was moved into wine.conf. This kind of thing would cause problems for a DrakWine-type of configuration. :) 3) The Wine team themselves say that it's alpha, developer-only release. They still have major changes planned that will break some programs. Now their version of stable may be a lot stricter than ours -- but let's draw an analogy to kernels. I've been running 2.3.x kernels for ages now (until I installed 7.1 beta3; that is. No ReiserFS in the standard kernels :) without any problems. But if AC says that it isn't stable, I think that a distro shouldn't include it as part of their main functionality. Just because the developers say that it isn't ready yet. Easy wine configuration stuff should happen at some point; I just don't think it should be quite yet. -- This is my sig. I shall insert something witty here soon.
Re: [Cooker] [discuss] wine configuration
Hi Corel's Office 2000 for Linux is based on Wine and runs fine at least on RH6,1. (No time available to install on Mandrake 7,02 as yet, but I will do it.) No crashes, no lockups, no problems. It seems rather stable to me. Ron Graham Percival <[EMAIL PROTECTED]> said: > On Fri, May 26, 2000 at 08:04:07AM -0400, Gallagher wrote: > > 1. Preconfigured Wine > > 2. Associated Wine with .exe files in KDE/Gnome > > 3. Graphical config for Wine > > This is something that should be done eventually (though I'm expecting it to be > hooked into the "support for other binaries" at the kernel level, rather than > associations in file managers) but not in > the very near future. The Wine group is currently discussing whether they can > shoot for a version 1.0 and what needs to be done first; I don't think that > they expect to reach that by the end of the year. I think that Wine is too > volatile right now (not that it's a bad project; far from it.) > > -- > Graham Percival > > --
Re: [Cooker] [discuss] wine configuration
VMWare is wonderful but is also VERY trying on a system. Also... sometimes it isn't as "virtual" as "virtual machine" sounds. If your virtual machine hangs it can do serious damage to the windows registry. Trust me I know ;) - Original Message - From: B. K. Barley <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, May 27, 2000 11:41 PM Subject: RE: [Cooker] [discuss] wine configuration > Isn't the whole windows binaries/wine kinda pointless with VMWare around? I > know that it's a very expensive piece of software, but I've used it and it > really did much better the wine. At least it did run all my apps (except > those crucial to timing) albeit a little slow. When I get the money, I do > intend on buying a copy of it. > > Bryan > > -Original Message- > From: Graham Percival [mailto:[EMAIL PROTECTED]] > Sent: Friday, May 26, 2000 11:19 AM > To: [EMAIL PROTECTED] > Subject: Re: [Cooker] [discuss] wine configuration > > > On Fri, May 26, 2000 at 08:04:07AM -0400, Gallagher wrote: > > 1. Preconfigured Wine > > 2. Associated Wine with .exe files in KDE/Gnome > > 3. Graphical config for Wine > > This is something that should be done eventually (though I'm expecting it to > be > hooked into the "support for other binaries" at the kernel level, rather > than > associations in file managers) but not in > the very near future. The Wine group is currently discussing whether they > can > shoot for a version 1.0 and what needs to be done first; I don't think that > they expect to reach that by the end of the year. I think that Wine is too > volatile right now (not that it's a bad project; far from it.) > > -- > Graham Percival >
Re: [Cooker] [discuss] wine configuration
Kaixo! On Fri, May 26, 2000 at 08:03:46AM -0400, Gallagher wrote: > Suggestions: > 2. Associated Wine with .exe files in KDE/Gnome Nice. But only for intel platform, not for alpha, sparc, ppc,... as wine is not an emulator on those (until bochs can provide the hardware emulation). For Gnome just have the wine rpm include that file: ===/usr/share/mime-info/wine.keys=== application/x-ms-dos-executable: open=wine -managed %f view=wine -managed %f icon-filename=some-nice-default-icon.png and have the line 0 string MZ application/x-ms-dos-executable added to /etc/mime-magic -- Ki ça vos våye bén, Pablo Saratxaga http://www.srtxg.easynet.be/PGP Key available, key ID: 0x8F0E4975
RE: [Cooker] [discuss] wine configuration
Isn't the whole windows binaries/wine kinda pointless with VMWare around? I know that it's a very expensive piece of software, but I've used it and it really did much better the wine. At least it did run all my apps (except those crucial to timing) albeit a little slow. When I get the money, I do intend on buying a copy of it. Bryan -Original Message- From: Graham Percival [mailto:[EMAIL PROTECTED]] Sent: Friday, May 26, 2000 11:19 AM To: [EMAIL PROTECTED] Subject: Re: [Cooker] [discuss] wine configuration On Fri, May 26, 2000 at 08:04:07AM -0400, Gallagher wrote: > 1. Preconfigured Wine > 2. Associated Wine with .exe files in KDE/Gnome > 3. Graphical config for Wine This is something that should be done eventually (though I'm expecting it to be hooked into the "support for other binaries" at the kernel level, rather than associations in file managers) but not in the very near future. The Wine group is currently discussing whether they can shoot for a version 1.0 and what needs to be done first; I don't think that they expect to reach that by the end of the year. I think that Wine is too volatile right now (not that it's a bad project; far from it.) -- Graham Percival
Re: [Cooker] [discuss] wine configuration
On Fri, May 26, 2000 at 08:04:07AM -0400, Gallagher wrote: > 1. Preconfigured Wine > 2. Associated Wine with .exe files in KDE/Gnome > 3. Graphical config for Wine This is something that should be done eventually (though I'm expecting it to be hooked into the "support for other binaries" at the kernel level, rather than associations in file managers) but not in the very near future. The Wine group is currently discussing whether they can shoot for a version 1.0 and what needs to be done first; I don't think that they expect to reach that by the end of the year. I think that Wine is too volatile right now (not that it's a bad project; far from it.) -- Graham Percival
Re: [Cooker] [discuss] wine configuration
Guillaume Cottenceau <[EMAIL PROTECTED]> writes: > A good idea -- only problem is that [IMHO, i almost never used wine] you > must be root to run wine no? noip. -- MandrakeSoft Inchttp://www.mandrakesoft.com In travel.--Chmouel
Re: [Cooker] [discuss] wine configuration
- Original Message - From: "Gallagher" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 26, 2000 8:04 AM Subject: [Cooker] [discuss] wine configuration > Suggestions: > > 1. Preconfigured Wine Excellent idea. > 2. Associated Wine with .exe files in KDE/Gnome Search C:\ drive for apps that are known to work and install in menu. > 3. Graphical config for Wine > Doesn't this already exist or am I thinking of dosemu, which BTW with the release of version 1.0 could use this same treatment. Hoyt
Re: [Cooker] [discuss] wine configuration
On Fri, 26 May 2000, John Grange wrote: > Guillaume Cottenceau wrote: > > > A good idea -- only problem is that [IMHO, i almost never used wine] you > > must be root to run wine no? > > > > -- > > Guillaume Cottenceau > > no you can be a normal user > the only reson for being root is if the config dir / and the drives selected > for wine (wich are actualy dirs ) are only wrtitable for root. easy way around > this is in the wine.conf file put $HOME/wine as the C drive or something to > that affect. > > -DarkWlf Wine configuration can be improved in the rpm shipped with future Mandrake distros. Some neat proposals are included in the wine documentation " A small WINE distribution guide. ". urpmi wine ; less /usr/doc/wine-*/distributors In short, they give rationales and sample implementations to allow maximum out-of-the-package functionality (root only has to urpmi/rpmdrake the package), while leaving users possibility of personal configuration for windows software, without world-writable directory or other undesirable thing. ; Using this trick we have in fact two windows installations in one, we ; get the stuff from the readonly installation and can write to our own. You may even get what a real windows environment lack: true multi-user compatibility, even with software that need to write in c:\windows. Why worry, I don't use windows software, anyway... :) but other people may need that. -- Stéphane Gourichon - Laboratoire d'Informatique de Paris 6 - Équipe AnimatLab "Bonjour, je suis un virus de signature de mail. Copiez moi dans votre fichier signature pour que je me propage désormais avec vos mails. Merci."
Re: [Cooker] [discuss] wine configuration
On Fri, May 26, 2000 at 03:23:27PM +0200, Guillaume Cottenceau wrote: > Gallagher <[EMAIL PROTECTED]> writes: > > > Suggestions: > > > > 1. Preconfigured Wine > > 2. Associated Wine with .exe files in KDE/Gnome > > 3. Graphical config for Wine > > > > > > I was using another distribution the other day, I currently run Mandrake > > and then whichever new promising one comes out. When using the new distro > > I noticed that when browsing through a Windows' parition the .exe files > > were already associated with wine in KDE. I thought this was great! The > > wine configuration was decent enough that it ran a couple programs > > flawlessly without even having to touch a configuration file! Now I know > > changes will need to be made by most users in order to improve > > performance, but initial configuration being already associated with .exe > > files in KDE is a great option. Oh in case it helps I was using Caldera > > eDesktop. Also, I don't know if one currently exists but a graphical > > configuration for Wine would be great! > > A good idea -- only problem is that [IMHO, i almost never used wine] you > must be root to run wine no? Of course not. -- David FAURE [EMAIL PROTECTED], [EMAIL PROTECTED] http://home.clara.net/faure/ KDE, Making The Future of Computing Available Today
Re: [Cooker] [discuss] wine configuration
Guillaume Cottenceau wrote: > Gallagher <[EMAIL PROTECTED]> writes: > > > Suggestions: > > > > 1. Preconfigured Wine > > 2. Associated Wine with .exe files in KDE/Gnome > > 3. Graphical config for Wine > > > > > > I was using another distribution the other day, I currently run Mandrake > > and then whichever new promising one comes out. When using the new distro > > I noticed that when browsing through a Windows' parition the .exe files > > were already associated with wine in KDE. I thought this was great! The > > wine configuration was decent enough that it ran a couple programs > > flawlessly without even having to touch a configuration file! Now I know > > changes will need to be made by most users in order to improve > > performance, but initial configuration being already associated with .exe > > files in KDE is a great option. Oh in case it helps I was using Caldera > > eDesktop. Also, I don't know if one currently exists but a graphical > > configuration for Wine would be great! > > A good idea -- only problem is that [IMHO, i almost never used wine] you > must be root to run wine no? > > -- > Guillaume Cottenceau no you can be a normal user the only reson for being root is if the config dir / and the drives selected for wine (wich are actualy dirs ) are only wrtitable for root. easy way around this is in the wine.conf file put $HOME/wine as the C drive or something to that affect. -DarkWlf
Re: [Cooker] [discuss] wine configuration
Gallagher <[EMAIL PROTECTED]> writes: > Suggestions: > > 1. Preconfigured Wine > 2. Associated Wine with .exe files in KDE/Gnome > 3. Graphical config for Wine > > > I was using another distribution the other day, I currently run Mandrake > and then whichever new promising one comes out. When using the new distro > I noticed that when browsing through a Windows' parition the .exe files > were already associated with wine in KDE. I thought this was great! The > wine configuration was decent enough that it ran a couple programs > flawlessly without even having to touch a configuration file! Now I know > changes will need to be made by most users in order to improve > performance, but initial configuration being already associated with .exe > files in KDE is a great option. Oh in case it helps I was using Caldera > eDesktop. Also, I don't know if one currently exists but a graphical > configuration for Wine would be great! A good idea -- only problem is that [IMHO, i almost never used wine] you must be root to run wine no? -- Guillaume Cottenceau
