running Linux at work with Windows apps

[Bill Sconce]

bscott at ntisys.com writes:

> On Tue, 12 Nov 2002, at 3:56am, tbuskey at attbi.com wrote:
>> One reason I ran VMware was to sync my visor via USB to 
>> a MeetingMaker server.  I think I remember that Win4Lin
>> 2.0 couldn't do USB.  I this true with newer versions?
> 
>   No, Win4Lin does not (yet) support USB in Windows.  (Some
>   USB devices on the Linux side (e.g., mice) will be
>   virtualized on the Windows side.)  It is a popular
>   wishlist item.  No idea if NeTraverse can or will be
>   adding support for it.
> -- 
> Ben Scott <bscott at ntisys.com>
 

USB... brings up a good point. 

The domains in which a Microsoft-replacement product must
perform differ widely.  In our case, there were only a few
Microsoft-API products ("win16" as well as "win32"! :) which
we needed to keep alive.  A far different environment from
having to do development on win32, or development on several
versions of winXX at a time, for instance. 

In the "few apps" domain Win4Lin does well - as for integrating the
legacy stuff into the Linux filesystem environment, as has been
previously pointed out.  Another example is the network stack.  One
more would be physical address to the parallel port, when you just
HAVE to use the win32 device driver. 

On the other hand, there are cases like USB, where support is
problematic.  This suggests another consideration - whether the
domain is just a few sunset apps, or whether it is contemplated
to still be adding new winXX apps which are going to need
emulation support. 

Mileage will vary, but I have no plans to find any more chains
to put around my ankle at this late date.  With freedom so near... 

Put another way, if there is a need continuing into the
future to keep up with proprietary produccts VMWare may be
a better choice.  Win4Lin's design target is more tightly
focused.  Remember, for instance, that Win4Lin's support has
always been limited to the DOS-based versions of the software
formerly known as Windows. 

 -Bill