[Wine] Re: self-fixing problems

[vitamin]

hendrik wrote:
> On Mon, May 26, 2008 at 11:35:03AM -0500, vitamin wrote:
> 
> > 
> > ckx3009 wrote:
> > 
> > > 
> > > vitamin wrote:
> > > 
> > > > 
> > > > Sure - learn C, win32api, Wine source. Find the place that prints that "little problem" and ... fix it or implement missing functionality.
> > > > 
> > > 
> > > but this means to became a wine developer...
> > > 
> > > 
> > 
> > Pretty much - yes.
> > 
> > 
> > ckx3009 wrote:
> > 
> > > 
> > > this reply seems to want to say: leave to devs the dev's work...
> > > 
> > 
> > Yup. How else can you fix a ... "fixme" if it's telling about not implemented functionality?
> > 
> > 
> > ckx3009 wrote:
> > 
> > > but in this way we (users) will never be able to help with our own work about little things the dev team...
> > > 
> > 
> > What you can do as a user - look for real problems with applications you are running not imaginary problems in a form of some debug information printed by Wine.
> > 
> 
> I suppose the next question is:  How can naive users distinguish real 
> problems from debug messages?  Maybe there should be a guide for that!

Just read them and try to understand I guess. If a message says "can't findMFC42.DLL" then install that dll. See FAQ for this.