in the classic preferences classic support is using 252/2026 kb and Forge is using 5.2/20.4 mb (i gave around 20 megs instead of 7 in the get info thingy)
these numbers were gathered while running the marathon infinity map file in visual mode. running sigma forge on a few poly map gave me similar results.
i'm gonna try trash the pref file (oh the good old trick)
removing the RAM would be kind of hard because i'm in my apartment now and i got no tools here to open up the iBook. while i had them back home on the farm. (i was there few days ago)
note: i also tried to run classic without extensions, it didn't do much. but i noticed today when i started to use forge that it "lagged" less but still used similiar amount of memory.
: Unless it's bad RAM, which could cause the effect you described. Also, it
: could be a corrupt extension in the Classic environment, like a QuickTime
: extension or OpenGL or who knows what. That Classic system preferences
: does allow you to control what extensions load (by opening the Extensions
: Manager at Classic startup) or turning them all off. The same system
: preferences also give you memory information of the classic programs
: running if you're using 10.3 or 10.4. Last but not least, Classic
: applications do allow you to specify in their Get Info dialog box how much
: RAM they should use...if you're concerned that Forge uses too much, give
: it a generous, but limited RAM allocation and see if Classic ends up using
: a lot more than that. Good luck. :)
: