On Saturday October 13 2007 22:54, Dan Sawyer wrote:
> I don't recall using that command. I have erased the .reg files in
> /.wine and the first call of wine recreates them. Is that an alternative?
No, it isn't because registry isn't whole wine prefix. But why not just to
follow my advice? Did you try to use winetricks?
BTW, you by definition already DID used wineprefixcreate if you have ~/.wine
with *.reg files, drive_c, etc. It is called automatically if you havn't wine
prefix directory yet (location of wine prefix directory is determined by
environment variable WINEPREFIX and is ~/.wine by default). And of course it
is creating *.reg files too in your case.
All of above you can read in its man page, it is short and I already
explained what you need to do if you don't know the "man" command.
Please note that currently there is no guarantee that wineprefixcreate will
update existing prefix correctly. This is something that should be fixed
before WINE 1.0 but currently (re)moving your ~/.wine is good practice for
doing clean test. Of course you can move it back again with all your programs
and files when you're done with testing.
> I haven't isolated the regression yet. The later levels are working in
> the test system. However attempts to upgrade prod fail.
This is easy and can be done in just few minutes. Upgrade to 0.9.47 and just
execute:
mv ~/.wine{,~}
wineprefixcreate
Then install application where you found a regression as usually. If
regression is still there then proceed to next step.
This step is very simple. Downgrade to last working WINE version and try
again. If it does work then you're almost done. In fact you are ready to
report regression to http://bugs.winehq.org at this point.
Next you can do regression testing to find out what patch broke your app.
Don't worry you don't need to be a programmer to do a regression testing. In
fact it is so simple that everyone can do it and this is especially important
if your application isn't free and has no free trial because in this case it
is very unlikely to find a person who will do the regression test for you.
In short just read instructions at http://wiki.winehq.org/RegressionTesting .
On modern hardware regression test will took about 20-40 minutes (time depends
on how big "window" of your regression test). On old hardware it will took
more.
If for some reason you cannot do regression test please fill bug report "as
is". This is better than nothing and will took just a few minutes. However if
you do regression testing you will help developers quickly fix your problem.
Thanks for using WINE.
_______________________________________________
wine-users mailing list
wine-users@xxxxxxxxxx
http://www.winehq.org/mailman/listinfo/wine-users
