Hey mighty pete, here's more ntfs BS than any sane person should want :) http://www.digit-life.com/articles/ntfs/ I scanned it, and it seemed to have some useful info, though it is very pro MS (I'm not) I use win2k, because I can't afford a mac at this time, and there is really no alternative out there for consumer apps (Love linux, but there isn't a strong enough emulator that I can afford that doesn't drain the apps performance to a useless level....hopefully things will be very different in a year or so) Alekssander, something I thought about shortly after I left an earlier message, is the opengl stuff. Now that brings my system to it's knees and makes it beg for a cycle or two (I have it set to pretty low quality) Perhaps, if you are rendering a large scene, you should turn opengl off. When you think about those millions of polygons periodically being traversed and applied to some drawing algorithm, it is quite a demanding thing, indeed. It's worth a shot. I know my machine (750 mhz) is pretty much useless when the quality is turned up and I have a complex scene (menus take seconds or minutes to respond). Simply put, it is really a lot for the machine to handle. Try doing without it. As for vue and memory, I am a programmer, and I can think of a few odd things that could lead to vue having a limit, but I doubt that is the case. Most likely, the message you have given is due to a new operator returning null which is due to the OS having nothing left to give the app. I guess it is possible to blame Eon, but I suspect the real problem lies elsewhere. Just a thought, Eric