[Wine] Re: self-fixing problems

ckx3009 wineforum-user at winehq.org
Wed May 28 06:29:45 CDT 2008

dimesio wrote:
> > If you're app isn't behaving as on windows, then you've got an actual
> > problem. Whatever the terminal prints out isn't necessarily a problem. 
> I know that. That's not the point. The point is that sometimes when you do have a problem, the terminal may give some useful information, but it's not necessarily as obvious as a dll not found. The preloader page zero problem is a perfect example of the kind of message I'm talking about--it points to a specific problem, with a known workaround, but the error message itself is not something a beginner would understand without reading the sticky at the top of this forum, which I assume is why you put it there. So the question is, are there any other such cryptic error messages that point to problems with known fixes that beginners could apply themselves if they only knew what the message meant in the first place?

this is exactly what i wanted to say.

the FAQ does not contain a list of problems that may be avoided by users in a specific way... so could be a good idea to create a little page with listed some common problems and the workaround for them.
and may be also a good idea to explain what is the meaning of the most frequent console messages. 
for example you could write:
"fixme" means that this problem can only be fixed by a developer, so don't pay attention to that or report that in "this specific way".
or something like:
"this_problem" means that you need to do the following things
[ list / workaround ]

something like this...so a normal user who want to solve himself the most common problems, can do this without searching all over the entire internet.

More information about the wine-users mailing list