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.
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 :=}
Philippe
Eric Wood <[EMAIL PROTECTED]> writes:
> The thing that would help a lot of people out would be for wine to output to
> a log file with a list of files that the program *tried* to access. All too
> many times, a program would give a vague error without telling you what .dll
> or file it tried to access. Some gueswork is involved and when you flood
> your windows/system directory with 10 million .dlls then your program would
> get a little farther then bomb with another vague error.
>
> I know wine has a debug function but it's not motivating to learn when the
> main problem is just a missing file.
>
> -Eric Wood
>
> -----Original Message-----
> From: Bernhard Rosenkraenzer <[EMAIL PROTECTED]>
>
>
> >On Fri, 4 Feb 2000, Bret Hughes wrote:
> >
> >> Does wine work for the 32 bit stuff?
> >
> >Yes.
>
>
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
