 | | | OT Re: Codeweavers Produts (Beware the rant) | OT Re: Codeweavers Produts (Beware the rant) 2003-11-03 - By Ed Greshko
Back
On Tue, 2003-11-04 at 06:55, Jeremy White wrote:
> Forgive the length of the reply; but this touches me deeply.
And forgive the extensive snipping...
> <unwarranted rant >
> I can get access to a test copy; never mind the insult of
> the $179 fee.
> </unwarranted rant >
<tongue in cheek >
Yes, it is get almost as bad as those M$ folks and their "M$ Developers
network " where they charge you ~$800/year to use their stuff. But, I
guess M$ is better since you do get some lovely CD carrying cases.
</tougue in cheek >
Based on the bulk of your mail I think I failed to make my point.
I am *not* surprised that the Codeweavers ' products are failing on
RHEL. It is often that previous versions of applications will break
when a new OS comes out. And, sometimes, they even break the OS. So,
it really wasn 't necessary for you to defend yourself to such a degree.
> So, the curt, one line responses were *not* from
> anyone at CodeWeavers. You can view the ticket here:
>
http://www.codeweavers.com/site/support/tickets/browse/?ticket_id=34046
;s_author=Ed.Greshko%40greshko.com
> and see that the responses were from a 'Volunteer '
> unaffiliated with CodeWeavers. His responses were, actually,
> the proper answers, but his abruptness would not be tolerated
> in one of my employees.
My point (source of my ill advised rant) is that when a "Volunteer "
responds to a ticket the recipient sees
"Person 's Name <plugin-support@(protected) > "
and cannot determine that they have in fact gotten email from a
"Volunteer ".
I 'm perfectly capable of making a fool of of myself without being
tricked into it. So, my strong suggestion would be to change your
system such that it is very clear where responses are coming from.
So, again, the open ticket system is fine....just need to ensure that the
identities are clear. Currently, they are not.
> I 'm sorry if this wasn 't clear; I 'll see if we can 't tweak
> the email headers to better convey this.
Don 't hedge. Take the Nike approach and "Just Do It! ".
> You can see that we sometimes get it right; check out Chris 's
> ticket here:
>
http://www.codeweavers.com/site/support/tickets/browse/?ticket_id=34029
> (note the 59 minutes to first response; nice work, Mike <grin >).
OK.... I 'm waiting for official responses for tickets 34043, 34045, and
34046.
> And I understand your frustration with Mike 's answer, Chris,
> but to be blunt, he 's right. Wine runs *completely* in user
> space. There is no technical way that it can be Wine 's fault
> that a system lockup occurs - if the system locks up, it 's
> a driver/kernel issue. Doesn 't mean Wine isn 't one of the finest
> regression test tools on the planet... <grin > And it doesn 't
> mean we won 't try to help you find the source of the problem.
As an "end-user " I 'd prefer to hear something along the lines of "..and
we look forward to working together with Red Hat to resolve the
problem... ". It is so much nicer to see a cooperative effort as opposed
to finger pointing.
> I 'm sorry for the very long rant; thanks for listening. I hope
> you 'll give us a chance to get it right on RHEL for you.
I 'll wait.... Just hope that I don 't get too used to Open Office in the
mean time. :-)
--
"An opinion is like an asshole - everybody has one. "
- Clint Eastwood as Harry Callahan, The Dead Pool - 1988.
|
|
|