I have heard that Wine works best if you have a box that dual-boots
Linux and Windows. If you don't have windows dual-booted, you need to
set up a directory structure that mirrors what would be on Windows.
Getting Windows to work has involved rewriting many of the DLL's in the
Windows system directory (as well as other things). From what I know,
this is a work in progress and there are still significant bugs. But
maybe it's further along since I last checked the website.
Since I don't dual-boot, it wasn't worth the potential hassle. Win4Lin
was simply a question of "if it works, fine, if it doesn't, forget about
it". And it worked out of the box. Granted, my needs are simple: If I
need to make out a MSWord doc for somebody else, I can. I can also do
that with StarOffice, but it's nice to be able to run it through MSWord
to verify that MSWord likes it before I send it out.
edoc wrote:
>
> What, please, is the advantage of Win4Lin (or the more pricey VMWare)
> over Wine?
>
> >From what I read here Wine seems to get the job done ... with more to
> come ... http://www.icewalk.com/softlib/app/app_00356.html
>
> "Input, I need input!" (Short Circuit)
>
> Thanks! Doc
>
> > On Wed, Jun 13, 2001 at 03:26:09PM -0400, Robert Haeckl wrote:
> >
> > > Legacy M$ apps (meaning Office95/Office97) work well in Win4Lin.
> >
> > Question: supposedly under VMWare, Windows apps run more stably (fewer
> > crashes). Would you say the same is true for Windows apps running
> > Win4Lin? I'm thinking of replacing my wife's Windows with a SuSE system
> > running Win4Lin, and she's a power user. She _kills_ her system
> > routinely. It would help if I could say that her Windows apps wouldn't
> > crash as much (or Windows itself, for that matter).
> >
> > Paul
> >
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 18:58:45 EDT