Wine and iexplore.exe

[James McKenzie]

  On 9/19/10 3:57 PM, David Boles wrote:
> On 9/19/2010 6:53 PM, James McKenzie wrote:
>>    On 9/18/10 5:54 PM, JD wrote:
>>> On 09/18/2010 05:48 PM, James McKenzie wrote:
>>> Yeah.. I decided to dump it.  I uninstalled everything "wine".
>>> Not worth all the jumping through hoops to make it work right.
>> There is this saying, if you want to run Windows, then run Windows.
>> VBox and VirtualBox do a good job.  However, we are here to support
>> Linux, and if we don't report problems with Linux programs, they don't
>> get fixed...
>>
>> (I know that I'm basically preaching to the choir here, but some folks
>> figure that problems will be fixed by magic.)
> You mean that it does *not* work that way? Really?  I always thought
> that the Linux Gnome handled bugs.  :-)
:)  The Gnome is on vakay.

Actually, if you don't report Wine bugs, they basically don't exist.  
The developers have enough to do trying to implement the Windows32/64 
Applications Programming Interface (API) to go out and find bugs on 
their own.  Now, if a problem affects their 'favorite program' then it 
will get reported.  If it breaks the self test sequence, it will get 
reported, but it if bothers foobar2000 and none of the developers own or 
care about foobar2000, then it is up to the user to report the bug.  
Just like what happened with several kernel builds.  "But it works here" 
almost became a mantra until a big corpora user stepped in and said "It 
don't here, we are paying $$$$$ for support, fix the damn thing."

This is a fact of life and one of the reasons this project exists.

James McKenzie