Jack Stein wrote in a message to Bill Shaughnessy:
BS> The original question was whether or not there might be
BS> several versions of OPUS floating around. I responded
BS> affirmatively, because I've suspected that for a long time.
JS> Yes, and you used your connections with Stu and Willie as
JS> the basis for that suspicion.
I used the connection with Stu, and the non-connection with Willie as
one manifestation of the phenomonon. There was no getting away from the
connections with Stu - He was, and still is an uplink of mine, and what good
is an uplink if you are unable to exchange mali with him. As far as the
non-connection with Willie, he was the one who started to raise the fuss.
Instead of him in comparison to Stu, I could have used any one of several
thousand OPUS systems worldwide. Besides, I also included several other
manifestations.
BS> As far as running CRC's, I don't know that it really would
BS> tell us anything.
JS> It would tell you if Stu and Willie were or were not running
JS> the exact same copy of OPUS.EXE, and it seems they are, as
JS> someone did this test, Willie I believe. So you are back to
JS> square one, and for sure this suspicion of yours has no
JS> basis, which all of us suspected. We can now move on to
JS> other suspicions.
I agree that Willie posted some figures. As you suggest, I have
drawn my own conclusions.
BS> Back in the days when I was running OPUS, I did have
BS> some problems, and I did manage to correct them. My
BS> investigations at that time did strongly indicate a problem
BS> in OPUS, and I reported that problem in this very echo.
JS> Yes, but I recall none of us suspected the problem was in
JS> OPUS, rather in you're hardware, or modem setup or
JS> something, but not a bug in OPUS. Is my recollection
JS> correct?
You, along with several others, none of whom are posting in the
current thread, tried your best to help me out of what seemed to be a modem
problem. I know you were as surprised as anyone when the cause of my problem
turned out to be a bug in OPUS. If I were to put OPUS back on line, I could
reproduce that problem ad infinitum. I very sincerely doubt that I could
produce the same problem on your barefoot OPUS. The thing that irks me about
that problem is that while we were trying to figure out what was wrong,
someone in the echo knew what the problem was, but would not open his or her
mouth.
JS> The only problem I have with OPUS is it can be hung when
JS> certain callers screw up a D/L, this is very rare, and must
JS> be something stupid that only a few callers manage, I don't
JS> know if its OPUS, my set-up or what, but it's rare enough, I
JS> don't care much, and I devised a recovery scheme that works.
Does the recovery system work when you go on vacation? :-)
JS> For sure you brought some life into the ye old meadow...
Thank you, Jack. Unfortunately, this thread brought some very
unpleasant aspects of this echo, and I mean aspects that should never have
surfaced. BBS'ing is supposed to be fun, but that is not the attitude that
was displayed here. I'll go so far as to say that Michele Marie Dalene is
due some very major and sincere apologies. But I don't think they'll appear.
Bill
--- timEd 1.01
---------------
* Origin: THE PINCHOT ROADS - (412) 741 4276 (1:129/291)
|