On Fri, 4 Feb 2000, Philippe Moutarlier wrote:
> Well, my main problem about wine is that I still don't know what it
> can actually run or not. Almost anything that was of interest to me
> would NOT run. I checked on the "success lists" and I could never run
> what was suposedly ok on the list. Probably one of the options you
> need to tweak but it is not very clear how it should be done.
That list includes everything that was once run successfully in wine.
There are some things that worked in older versions, and don't work
anymore in newer ones, then there's stuff that depends on some DLLs from
windoze being copied in, as well as some stuff depending on configuration
(the configuration stuff should be fixed in the 20000202-2 RPM.)
Also, wine has some problems with most porgrams' installers. Many times,
installing a program on an actual windoze box, then tarring the directory
it created and copying it over to the linux+wine box helps. (Or so people
say - I haven't been anywhere near a windoze box for years. ;) )
> I regularly (twice a year) recompile wine and try to see if it became
> usefull. No luck so far. Vmware is infinitely more usefull. More
> expensive too :={ and more resource consuming. I guess the next time
> for trying wine is coming now :=}
The big problem with wine is that it's staying legal - therefore, it
can't do well on undocumented functions (reverse engineering is illegal in
most countries), which M$ makes heavy use of.
Maybe if the DOJ comes to a fair decision...
LLaP
bero
--
The first time Microsoft makes something that doesn't suck is when they
start making vacuum cleaners.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
