• Re: 0000000F, 00000003 error

    From David Lanahan@lanahandavid@gmail.com to comp.sys.mac.misc on Mon May 30 00:24:24 2022
    From Newsgroup: comp.sys.mac.misc

    On Wednesday, March 1, 2017 at 2:28:38 PM UTC-5, Auric__ wrote:
    evalc2636 wrote:

    On Sunday, September 24, 1995 at 10:00:00 AM UTC+3, T. Kelley Boylan wrote:
    Thank goodness for having a backup system, but there's still a lot of
    data on a drive that, without warning, came up with a sad Mac and

    0000000F
    00000003

    What be this thing, and if you know what it is, how do I circumvent it? >>
    Many thanks.

    -Kelley-

    0000000f 00000003 that code hapend to me playing a game it was weird the game screen was black and there was only a code (0000000f 00000003) I
    read the crash file and it was a renderer crash
    You know, that information probably might have been more useful to Kelley if it had been posted closer to the original post... over ***21 YEARS AGO!*** Except, in 1995, Kelley was using either a 68k machine or a PowerPC, where the error codes may very well have been completely different.

    Fucking Google Groupies.

    --
    There's a big difference between a BUTTER KNIFE and a BUTTERFLY KNIFE.
    --- Synchronet 3.19c-Linux NewsLink 1.113
  • From Wolffan@akwolffan@zoho.com to comp.sys.mac.misc on Mon May 30 09:52:54 2022
    From Newsgroup: comp.sys.mac.misc

    On 30 May 2022, David Lanahan wrote
    (in article<dca5b80f-9a34-4702-b834-829332c85ec0n@googlegroups.com>):

    On Wednesday, March 1, 2017 at 2:28:38 PM UTC-5, Auric__ wrote:
    evalc2636 wrote:

    On Sunday, September 24, 1995 at 10:00:00 AM UTC+3, T. Kelley Boylan wrote:
    Thank goodness for having a backup system, but there's still a lot of data on a drive that, without warning, came up with a sad Mac and

    0000000F
    00000003

    What be this thing, and if you know what it is, how do I circumvent it?

    Many thanks.

    -Kelley-

    0000000f 00000003 that code hapend to me playing a game it was weird the game screen was black and there was only a code (0000000f 00000003) I read the crash file and it was a renderer crash
    You know, that information probably might have been more useful to Kelley if
    it had been posted closer to the original post... over ***21 YEARS AGO!*** Except, in 1995, Kelley was using either a 68k machine or a PowerPC, where the error codes may very well have been completely different.

    Fucking Google Groupies.

    --
    There's a big difference between a BUTTER KNIFE and a BUTTERFLY KNIFE.

    Bloody hell. Not one, not two, but _three_ attempts to zombify a necrothread from _1995_.

    What is it about Google Groups users that they can’t bloody look at the posting dates? 1995. Zombified in 2017, twice. Zombified _again_... and using an empty post. All three zombi attempts made by Google Groups users.

    --- Synchronet 3.19c-Linux NewsLink 1.113
  • From Auric__@not.my.real@email.address to comp.sys.mac.misc on Tue May 31 17:09:38 2022
    From Newsgroup: comp.sys.mac.misc

    Wolffan wrote:

    What is it about Google Groups users that they can't bloody look at the posting dates? 1995. Zombified in 2017, twice. Zombified _again_... and
    using an empty post. All three zombi attempts made by Google Groups users.

    It's The September That Never Ended, Part II.
    --
    Between two evils, I choose the competent one.
    --- Synchronet 3.19c-Linux NewsLink 1.113