wine users - Feb 2005 - Proper way of updating winetools?

After updating from, say winetools-2.10-jo to 2.11-jo (by rpm), I can't 
use the wt startup scripts like ie6, wmplayer etc. any longer, and I get 
an error message similar to "winetools hasn't been configured for this 
user. Run the base setup ..." But doing so would erase my ~/.wine 
directory and thus destroy my old setup including all my program 
installations, which of course I wouldn't like to happen.
Now, before doing the base setup, I could backup my .wine directory.
But how to restore it? By destroying the new one created by 
winetools-2.11? Which might lead to "winetools hasn't been configured 
for ..."
Perhaps I am missing something very obvious, so please help me out of 
this vicious cycle.
Klaus

Am So, Feb 20, 2005 at 06:50:35 +0100 schrieb Klaus-Peter
Schrage:
> After updating from, say winetools-2.10-jo to 2.11-jo (by rpm), I can't
> use the wt startup scripts like ie6, wmplayer etc. any longer, and I get 
> an error message similar to "winetools hasn't been configured for
this
> user. Run the base setup ..." But doing so would erase my ~/.wine 
Hi,

are you sure it does not tell you, "Wine has not been configured for
this user yet"? It is complaining about your Wine setup, not your
WineTools setup. If you have error messages, send them exact and
correct, please. WineTools searches for the availability of the
following program:

"$WINEDIR/drive_c/windows/regedit.exe"

where $WINEDIR is ~/.wine. If this program, which is a link to
/usr/lib/wine/regedit.exe.so (or whereever you installed Wine to), is
not there than you deleted it, did not use WineTools, or your setup is
not common to WineTools. This might be the reason if you don't have
drive_c as the C:\ entry. To solve this, create a symlink from your
entry (probably just called c) to drive_c.

Regards
	Joachim
-- 
"Never touch a running system! Never run a touching system?
          Never run a touchy system!!!"