Found what appears to be the problem. If you use XWine to alter the config file - or just look at it, but save it at the end, it alters the file. The most recent re-install i played with, it copied the last line of the file to the top, above the first line. Since the file no longer starts with WINE REGISTRY Version 2 wine gets indigestion, complains is not a valid file, and exits.
Removing the bogus line fixes the file, then wine runs ok V. On Tuesday 10 June 2003 11:28 pm, Per Øyvind Karlsen wrote: > On Tuesday 10 June 2003 16:58, Vincent Meyer, MD wrote: > > Hello, > > > > Is anyone having success with the current XWine and wine in cooker? > > > > XWine seems to break wine when used to edit the config files - even if > > no changes are made. The next time XWine is invoked it bombs, with a > > console message complaining that wine has to be installed. > > > > wine seems to not be able to find programs - even when they're in the > > same directory. I remember there being a patch for a similar problem, > > which i thought was in the current RPM. > > > > V. > > I did fix the problem I think you're thinking of in 20030408-2mdk, also I > applied rcc's patch in 20030408-3mdk, things seems to work just fine here, > but if you have problems, please give me detailed bugreports:) > also, I have'nt done any work on wine lately due to problems with > docbook-utils (required to build wine) :\ > > rpm [EMAIL PROTECTED] hawkeye]$ rpm -q --changelog wine|more > * tir apr 29 2003 Per Øyvind Karlsen <[EMAIL PROTECTED]> 20030408-3mdk > > - fix summary for utilities package > - be sure to own /usr/lib/wine (thx to olivier) > - rcc <[EMAIL PROTECTED]> > o make winstyle paths work (ie C:\\xxx xxx\\yyy) > o changed argument handling > o changed interpreter to bash because we're using bash extensions > > * ons apr 16 2003 Per Øyvind Karlsen <[EMAIL PROTECTED]> 20030408-2mdk > > - changed summary too > - make wine able to handle spaces in filenames again
