Announcement

Collapse
No announcement yet.

Quake is crashing my computer when I exit

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Quake is crashing my computer when I exit

    Exactly what I said. I'm using windows ME and non-GL proquake. Every time I exit, the screen goes black (same when I alt-tab)

  • #2
    Mantan, Monster had a similar problem that was cured by updating video card drivers. I guess a good place to start is what video card are you using?

    If it is a Radeon or a GeForce, I'm sure an update will probably get it to work.

    It *could* be the operating system. You might trying adding -window -startwindowed to the command line and seeing if it crashes.
    Last edited by Baker; 09-05-2006, 02:10 AM.
    Quakeone.com - Being exactly one-half good and one-half evil has advantages. When a portal opens to the antimatter universe, my opposite is just me with a goatee.

    So while you guys all have to fight your anti-matter counterparts, me and my evil twin will be drinking a beer laughing at you guys ...

    Comment


    • #3
      (this is a non-helping post so please ignore if you don't like it)

      Step 1: Get rid of Windows ME
      Step 2: Get new OS
      Step 3: play Quake

      Comment


      • #4
        I agree. There should have been a class action suit with that ME version.
        www.Net-Tyme.com
        Lifes a game.. It's time to Play!
        Quake.net-tyme.com Pick your Poison.

        Comment


        • #5
          This happens to me with any version of Quake, with Win XP SP2 and nVidia drivers version 91.31

          The solution is to hit Win+L to go to the welcome screen, then go back.
          16:03:04 <gb> when I put in a sng, I think I might need nails
          16:03:30 <gb> the fact that only playtesting tells me that probably means that my mind is a sieve

          Comment


          • #6
            this used to happen to me too, with good drivers.

            solution: use a GL client.

            Comment


            • #7
              If I remember right, there was some kind of memory leak or something to that effect. I knew of them patching it through Microsoft Update. May be relevant.

              Windows ME was the only OS I never owned.

              I will find you... it's only a matter of time.

              Comment


              • #8
                Gunter, not registered here, says to add -nowindirect to your command line. This might possibly fix the problem your having.

                Comment

                Working...
                X