As another win4lin 1.0/upgrade to 2.0 customer, I must say that I expect
at least a fairly nominal upgrade price, if not free. For me,
win4lin2.0 was the first useable version for what I wanted. And I've
had more than a few problems with both 1.0 and 2.0, some of which still
haven't been solved. For example, the interaction between ALSA sound
drivers and win4lin which has been reported by a number of people on
this list. I've had an open trouble report on this with netraverse for
over 10 days with nothing more than the nominal reply that it was
received and one request from them to run the support.sh script and send
them the results. No reply to the reports in this group or any real
attempt from Netraverse support to reply to my trouble ticket. Also,
I've had a problem ever since I've used win4lin with the networking
hanging up in winsock after a while. The only solution there has been
to restart win4lin. Again, despite some efffort, Netraverse hasn't been
able to solve that one. Letely, I've also had problems with the serial
port performance. For example, I haven't been able to sync a fairly
large file to my Pilot through win4lin. The connection eventually times
out part way through the transfer. I've never managed, despite reading
and trying all the help, to get printing to work except to a file, so
I've been stuck with a two step process for printing (print to a file
and then print the file from Linux). These problems have led me to try
out VMWare and I haven't had any of the same problems with that product.
For example, the pilot sync worked first time with the same files I
couldn't get over in win4lin. Sound works without problems with the
ALSA drivers, printing works fine, etc.
Now, there are some things I like better about win4lin and I would like
to see if some of my problems are fixed in win4lin3.0. But at this
point, I would view win4lin3.0 as a bug fix release (particularly this
close to the 2.0 release) to get things working which should have
worked. From that point of view, I'm not really willing to pay much for
an upgrade. If it costs me much, then I'm going to have to serioiusly
consider whether or not I'd be better off spending the money on VMWare
Express instead. I like the performance of win4lin and I would like to
see the product succeed, but I also want a product which works reliably
for me and I'm not there yet with win4lin.
My view, FWIW.
Scott
> Date: Fri, 23 Mar 2001 20:00:10 -0700 (MST)
> From: Michael L Torrie <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Subject: Re: [Win4Lin-users] Win4Lin 3.0 and 2.4.x Kernel support
> Reply-To: [EMAIL PROTECTED]
>
> I agree somewhat. I don't expect a free upgrade. But I do expect to pay
> an upgrade price for an upgrade. I think that Netraverse would be wise to
> treat its existing customer base well, because we are the ones who are
> recommending or not recommending this product to friends, coworkers and
> folks on the net wanting to try out linux and still have windows
> capabilties. The features of 3.0 are impressive. But perhaps it's a
> little late, unless it now supports ME, since Windows 98 is no longer
> available on new machines and is fading away (not that ME is a real
> upgrade). Soon microsoft will be wooing people to a nt-based platform,
> XP, designed for home, gaming, and professional use. It will be a huge
> challenge to make win4lin run that OS. I am willing to shell out for
> win4lin 3.0, if anything to help netraverse continue to develop exciting
> software to bridge the gap between linux and windows.
>
> I saw OS X in action as was very impressed. Here's somethig OS X does
> that win4lin could do for windows on Linux. If you want to run a
> "classic" mac app, it boots up, in a little vm, OS 9. The programs,
> though, can run in windows on the OS X desktop, so you don't even know
> you're running old apps in a vm. Suppose win4lin could use a special
> graphics driver and intercommunications system to grab a windows window
> from the win4lin desktop (hidden) and draw it in a normal X window. Then
> have a simple mechanism for doing clip board stuff, and we'd have the same
> effect. The communications mechanism could pass commands back and forth,
> to launch programs, etc.
>
> I will watch win4lin's progress with interest.
>
> Michael
>
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
