BlueBomberDude
Chieftain
Harkonnen - I finally got around to trying your fix and I must tell you that "YOU ARE THE MAN!". The game works 100% better now - awesome stuff.
Thanks Harkonnen!
Thanks Harkonnen!
jinif said:Is this something I can fix? I have 512 RAM, will getting more solve the problem?
Thanks
DaEezT said:Actually I think people who post things that are completly and utterly wrong (like "Virtual memory is disk space, not memory.") aggrevate the situation because people who don't know whats going on believe it and suddently you have half a dozent memory leak threads where everyone blindly joins the crusade started by a few ppl who posted a few technical terms without knowing what they mean. And I didn't patronize anyone, I pointed out some wrong info and I won't argue any points about who is qualified to draw conclusions or who isn't because online, everyone suddently turns into an expert for everything... so you can either believe me or not.
And I still won't preach the inner workings of PCs here, I gave up doing that online quite a while ago.
But Harkonnen seems like he is still enthusiastic enough to explain some of the stuff in detail(And he seems to know that he is talking about)
Just remember: memory leaks don't cause slowdowns and having more main memory doesn't really help either (at least on the average windows system).
Sevenhertz said:I'm awakening this old thread to ask if this problem has been solved yet?
Although I have enough RAM (640mb) to run the game ok, many Wonder Movies would stutter and/or lock up and force me to restart. After restart, the movie works fine.My game was running fine until the Sistine Chapel movie started to run.(I'm not saying the Sistine Chapel is the cause) Suddenly, it slows to a crawl and then dies. I checked my virtual memory, and my peak usage of the virtual memory (paging file) was 93%. So I bumped my virtual memory, but the same error occured (peak usage at ~60%). In fact, the same error occurs every time. I cannot get past the wonder movie.