From: Pete Kelly <pfkelly@bnr.ca>
Subject: Re: AutoDoubler 2.0 vs. MacOberon 2.4
X-Xxmessage-Id: <A6F5EA8C1202052D@45.5.140.47.in-addr.arpa>
X-Xxdate: Mon, 5 Oct 92 17:50:20 GMT
Organization: Bell-Northern Research/Northern Telecom
X-Useragent: Nuntius v1.1.1d11
Date: Mon, 05 Oct 1992 16:44:30 GMT

Subject: Re: AutoDoubler 2.0 vs. MacOberon 2.4
From: Edgar Knapp, knapp@cs.purdue.EDU
Date: 5 Oct 92 02:00:17 GMT
In article <19852@ector.cs.purdue.edu> Edgar Knapp, knapp@cs.purdue.EDU
writes:
>In article <1992Oct03.002347.8119@brtph560.bnr.ca> pfkelly@bnr.ca (Pete
Kelly) writes:
>>In article <19828@ector.cs.purdue.edu> Edgar Knapp, knapp@cs.purdue.EDU
>>writes:
>>>That's the second major problem with AD that surfaced in as many days
>>>(the first one was an incompatibility with SpeedyFinder7).  Talk about
>>>sloppy beta-testing...
>
>>Do you really think it's fair to expect a company to beta-test against
>>every bit of available shareware out there.  There are literally
hundreds
>>and the possible combinations astronomical.
>
>You are missing the point. Fifth Generation (then Salient) has been
>aware of the problem since version 1.04 and I said so im my opriginal
>posting). I do expect them to fix known compatibilty problems.
>
>>From what I've seen, SpeedyFinder7 and CopyDoubler are attempting to
>>accomplish similar things and are most likely mucking around in the same
>>Finder code, with one patching and the other possibly re-patching the
>>same thing. What do you expect ?
>
>Again, you failed to read my message carefully. I am not talking about
>CopyDoubler (CD) vs. SpeedyFinder, but AD vs. SpeedyFinder. If you try
>to run the former together, who knows what will ahppen. The latter
>two, however, I would expect to get along. And they don't, even with
>nothing else enabled.
>
>Please try and read postings a little more carefully before getting on
>other people's case.
>

I DID read it and was commenting GENERALLY on your "sloppy beta-testing"
shot, not your PERSONAL problem with MacOberon. Just because you started
the thread doesn't mean EVERY COMMENT reflects directly back on YOU.  If
that were the case we should be limiting this conversation to one-on-one
E-Mail. You should realize that before getting on MY case in a public
forum.

I have (and currently am) beta-testing several new products so I
appreciate that it's virtually impossible to cover all combinations.
That's why a good company allows as many testers as possible. You've
discovered a bug and that's annoying in itself.  Now you're REALLY
annoyed because you feel you've done your part and are still being
ignored. Maybe you should do a little more.  

I contend that perhaps you just haven't gotten to the right people. Have
you ever talked directly to Lloyd Chambers and had him TELL you he
wouldn't fix your problem ?  I spoke with him briefly at MacWorld Boston
and he seems generally committed to a quality product. After all, HIS
name was on it BEFORE Fifth Generation took over Salient. Lloyd has moved
to Fifth Generation probably as an executive and may be able to devote
more resources to helping you.  I'm sure he  has a phone and maybe even
an E-Mail address. It may be simply that your report was never passed up
the line at Salient and a three minute DIRECT conversation would clear
things up and make you less sensitive to the mention of these products. 

I believe it was YOU who digressed from the original thread and brought
up AutoDoubler incompatibilities with SpeedyFinder7.  I was broadening
the topic a bit and making MY point that anything which messes with the
Finder ( be it DD, AD, CD, SpeedyFinder7 or whatever) stands a very good
chance of breaking SOMETHING. 

I'm using DiskDoubler, AutoDoubler, (and recently) SpeedyFinder7 and
frankly haven't had a bit of trouble with incompatibilities even with
three and a half lines of inits.  I do expect, however, to have to make a
choice between SpeedyFinder7 and CopyDoubler for the reasons I originally
stated.

If you find further comments necessary, please use E-Mail.