Re: Rubywand's new award! Plus, a few Questions

[nathan@visi.com (Nathan Mates)]

In article <34F7519A.885105CC@swbell.net>,
Rubywand  <rubywand@swbell.net> wrote:
>> Your idiotic programming practices which have been shot down 
>> many times this week?
>     No fair! Tripping over mutilated, sliced-up half-wits is not the
>same as being shot down.

   Um, you're the one who's totally refused to look at any evidence to
the contrary this whole week. You're the one who's acting like you
flushed your brains down the toilet, but still have for some crazy
reason, forgotten to tell your fingers that when hitting the 'post'
button.

>> mouth off for everyone to see. Such uncalled-for abuse about wrong
>> programming advice is why csa2 has become such a wasteland for actual
>> programmers who care about the truth

>    "Truth"? You should not use words unless you know what they mean.

   I can program, and do so correctly on the GS. You're the one
spouting lies about tool patches, suitability, and bughunting. Sorry,
but the truth of the matter is that you've only refused to listen to
the truth about OS bugs. Why have you totally refused to deal with the
other OS bugs I brought up, like the one on System 6.0.1's
_ChooseFont? Why have you totally refused to deal with the truth of
the code in ROM causing this bug? You're hiding from the truth behind
a shield of lies, flames, and idiocy. And it's only making you look
like the idiot.

>>, and about the facts.

>     You mean like a game that causes machines running the standard OS--
>the one all those other programs run on with no problem-- does not have
>a BUG? Perhaps it has escaped your notice that there is _no_ popular,
>installed OS under which the particular game will run without bombing
>some user systems.

   As I've detailed *many* times already, the OS has the bug. What
part of the ROM code addresses where I detailed it did you not
understand? On a ROM 3, look at FE/0342 and tell me why Apple's logic
is faultless. Or a ROM 01 at roughly +$1D4 into the L=$57FE block of
TS2. Explain to me exactly HOW the OS is supposed to deal with
toolsets after it has unloaded them from memory incorrectly? Wolfy
follows the rules. Most people do not have problems. For those that do,
patches to the OS are available.
>     By the way, as you may recall, we worried about, identified, and
>discussed the bug for roughly a week on the world's largest Apple II
>newsgroup without getting a word of feedback from the creator.

   First, did you bother reading the documentation in the least and
emailing the author first? Since you did not, it's safe to assume
you're just as much the illiterate fool as you've shown to be with the
OS bug facts and the truth above. You cannot follow the rules in the
least, of COURSE you're gonna be ignored. 

   By the way, I seem to have missed the bit in the csa2 charter that
said programmers did have to read it. Perhaps in your idiotic rantings
and ravings at a recent full moon you had a delusional moment to that
effect, but it's certainly not in the truth. 

>>    "Normally" does not mean *always*, except in the pirating idiot's
>> guide to English, I suppose. Also, were you a *real* GS programmer
>> with 2 brain cells to fire off occasionally,

>     Granted, the above description aptly describes some (not all) of
>those "*real* GS programmers" who have tried to tell us that a bug is
>not a bug. I guess "2 brain cells" makes it kind of tricky debating with
>'half your brain tied behind your back', doesn't it?

   It is an OS bug, as it exists in the ROM code. Now as you cannot
handle that truth, you're gonna act the idiot. Go away, back under the
rock whence you came from, pirating liar.

>     1. The same bunch who put out your doc put out the OS which has
>some serious bugs, including at least one associated with the CALL
>described. In such a doc, the expression "can use" means "can use if you
>want to try and are willing to test the results". 

   Really? I seem to have missed that line in reading Apple's notes.
Would you please point out chapter and verse where that was said, or
are you reading the atoms between the lines to come up with such a
pathetic excuse. 

>     According to the credits, you did some last-minute modifications to
>the game. Was the CALL to SetTSPtr one of your modifications?

   Not in the least. I sent Sheppy some code previously in
TurkeyShootGS for use in speeding up screen draws (particularly on
slot GSs), and helped squash a totally different bug just before
release. Sheppy put in that call of his own free will more than a week
before the game was released, and neither he nor any of the regular
testers encountered it before release. Many others tried launching and
quitting the game up to 30 times in a row, never once crashing. Since
you've already proven you can't handle technical truth, I think
challenging you to explain why the bug *didn't* bite them would be way
over your head.

>     Why all the secrecy?
>     Was it really so difficult to level with us from the start?

   Secrecy? It's been clear from the beginning-- this is an OS bug,
and I've said where and why it happened. You're the one inventing
conspiracies, inventing stories about who did what, inventing bullshit
about how to program the GS, and how to debug things. You've been the
illiterate idiot seeing things that don't happen, and refusing to
accept the truth when presented to you. We have been telling the
truth, but since you've apparently been standing a little too close to
a few aboveground nuke tests, you can't see that worth a damn. In your
fantasyland, we're wrong. But, in reality, you're only proving that
you should not be ever be allowed to be trusted again as factual.

   Go back to your trailer trash home, watch the X-Files some more,
and put on your tinfoil-lined pants and hat... the GS conspiracy is
going to beam some more thoughts into you if you don't watch out.

Nathan Mates

--
<*> Nathan Mates http://www.visi.com/~nathan/      <*>
# What are the facts? Again and again and again-- what are the _facts_?
# Shun wishful thinking, avoid opinion, care not what the neighbors
# think-- what are the facts, and to how many decimal places? -R.A. Heinlein