wine users - Jan 2005 - General comment s on Wine/WineTools - how does a new user setup Wine the very first time?

Hi,
   I've been messing with Wine and WineTools off and on for a couple
of days now. In general I can certainly see the bright future out
there, but so far it eludes me.  I've used various versions of Wine
successfully before, but with recent Wine I'm having little luck. I'm
on an FC2 machine with a custom kernel but can switch to Gentoo if
required. I've tried both wine-20041019 and wine-20041201 with
identical results.

   I'm hoping that a Wine guru somewhere can lead me in the right direction.

1) If I have a user's account that has never run Wine before then what
is the proper way to run Wine the very first time. Assume that the
user has no .wine directory and that Wine was just built in some
subdirectory from source. I've been using one of the following 3
commands to get the .wine directory built:

wine --version
wine notepad
wine regedit

All three commands seem to get .wine built, but is this the right way
to start? I'm never sure what to do with wineinstall as it seems to
want to build code which isn't appropriate for all user accounts.

2) WineTools won't install IE6 so far no matter what I try. It always
hangs somewhere in the middle of downloading or installing IE6.
However, outside of WineTools I can execute the same IE6 setup program
and it works correctly. I fear it has somethign to do with the two
commands that WineTools requires for setting up links where the second
command didn't work for me.

   Hopefully someone can answer these questions in the next day or two
and I can try again from scratch. If there are any other hidden
directories or files that need to be set up or removed before I retry,
please let me know. All I see today are the .wine directory and a
winetools log file.

   I'd really like to make this work.

thanks,
Mark

Am Do, Jan 06, 2005 at 08:50:25 -0800 schrieb Mark
Knecht:
> 1) If I have a user's account that has never run Wine before then what
> is the proper way to run Wine the very first time. Assume that the
> user has no .wine directory and that Wine was just built in some
> subdirectory from source. I've been using one of the following 3
> commands to get the .wine directory built:
When you build wine on yourself I think there is no default config
created when you type wine, but I'm not sure, because I always use and
recommend the prebuild variants from winehq. If you use them you can
type one of the commands. Wine creates the .wine when it does not exist.
If you use WineTools you will get a suitable config by executing the
"Base setup" no matter whether you have an existing .wine directory. I
recommend that way.
> 2) WineTools won't install IE6 so far no matter what I try. It always
> hangs somewhere in the middle of downloading or installing IE6.
> However, outside of WineTools I can execute the same IE6 setup program
> and it works correctly. I fear it has somethign to do with the two
> commands that WineTools requires for setting up links where the second
> command didn't work for me.
Sounds interesting. Did you go through the whole "Base setup"? This is
extremely important. If you don't the install will fail! You MUST create
a new fake drive with WineTools, install Arial and dcom98 before you
continue with IE6.
> and I can try again from scratch. If there are any other hidden
> directories or files that need to be set up or removed before I retry,
> please let me know. All I see today are the .wine directory and a
> winetools log file.
WineTools cares for all of that. The right way is just to go through the
whole "Base setup". But I don't know exactly how it works with
selfcompiles versions. Try a prebuild binary from winehq, please.

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