Classic GWorld Error???

Discussion in 'Mac Apps and Mac App Store' started by wrldwzrd89, Feb 18, 2004.

  1. wrldwzrd89 macrumors G5

    wrldwzrd89

    Joined:
    Jun 6, 2003
    Location:
    Solon, OH
    #1
    I have Mac OS 10.3.2 "Panther" on my (new) 17" iMac. I'm trying to play an old game that requires the Classic environment (Infinity Quest II) and was never ported to Mac OS X. When I try to open it, I immediately get the following message: "Fatal Error! GWorld Error!". After I dismiss the message, the program quits. I tried trashing the program's preference file and reinstalling the program. I've also tried using it under Mac OS 10.2.X "Jaguar" on an older Mac and experienced the exact same problem. I haven't tried it yet on a still older Mac I have that can't run Mac OS X (it is running Mac OS 9.0 - Mac OS 9.1 won't install). Any ideas?
     
  2. TEG macrumors 604

    TEG

    Joined:
    Jan 21, 2002
    Location:
    Langley, Washington
    #2
    Try increasing the program's memory allocation. Clcik on the Application in question then go to file get info, click on memory, and double what ever numbers are there. I have had similar problems with programs in Classic, and it seems to be the only way for them to run in OSX, especially if they are suppossed to use less than 256 Colors.

    TEG
     
  3. wrldwzrd89 thread starter macrumors G5

    wrldwzrd89

    Joined:
    Jun 6, 2003
    Location:
    Solon, OH
    #3
    Thanks TEG, I will try this when I get home later today (I'm at work now and using Windows, so I can't currently test it).
     
  4. wrldwzrd89 thread starter macrumors G5

    wrldwzrd89

    Joined:
    Jun 6, 2003
    Location:
    Solon, OH
    #4
    It worked!

    Doubling the memory allocation made the GWorld error message go away. Thanks Again!
     
  5. HexMonkey Administrator

    HexMonkey

    Staff Member

    Joined:
    Feb 5, 2004
    Location:
    New Zealand
    #5
    If you're curious as to what the problem actually was, I suspect that it was referring to an offscreen graphics world. These are basically something that an application can draw on before copying to the monitor, a common use being to eliminate flickering. For example, if you have five layers of graphics, you could draw them on the offscreen graphics world, and then copy the end image to the screen, as opposed to drawing each image to the screen, which is five times as many window drawings. Unfortunately, these need a lot of memory, since they store all the information about colour for each pixel. A lot of older games are made for 256 colours, so when you try and run it in more, this error is likely to occur (because you need 3 or 4 times the memory for millions of colours). So the solutions are to a) Increase memory as previously stated (preferable) or b) Change to 256 colours.
     

Share This Page