Quote:
Originally Posted by ReBorn_Spirit
I actually have to launch Media player 11, Internet Explorer 7, My computer, and another folder, and one Teamspeak program before I have enough memory in use that graal doesnt find so much as it actually has, but it likes to crash until I click start.
Basically I believe that Graal is just finding too much memory and thinks something is wrong and closes to prevent "something" from getting broken or hacked. Even though I don't have any memory editing programs, I think this is the problem with the 64 bit windows XP.
The real simple reason is with XP x64, it has a ton of memory from the 64 bit processor to utilize.
|
Perhaps I was only Partially correct, Recently found out I have only to launch my Teamspeak program, it deals with people talking over the internet for "in game" voice chatting. Well I don't use it to chat to anyone really, but I do use it so they can talk to me. Anyways, I load up my Teamspeak program in Windows XP x64 and I can play graal all I want, because it actually launches. I'll admit this, I don't know all that much about programming, but I DO know that you can only use certain rescources when they are free. If I wanted to reprogram graal 4 for a 64 bit OS, with what I know now, I'd probably start by checking for issues with audio in the games programming.