Does Graal Support 64bit OS?
 

tried installing graal on my new pc the other day, about 10 seconds after it started installing its crashed, now whenever i click the installer you can see it flash up but instantly closes again..

They question is more if 64bit OS' support Graal. What kind of OS, XP 64, Vista 64 or Linux 64bit ?

XP 64bit, sorry for not mentioning that

nobody knows?

Graal works alright in Vista x64 RC1 aside from a few issues (no sound, issues with PMs/history causing freezing, runtime errors when exiting). I haven't tested it with the RTM build yet, but I probably will in the next few weeks.

I haven't heard about anything testing Graal with XP x64. I know that version has tons of driver issues though; it isn't supported well.

yeah thats what people have been saying but i haven't had any problems so far except with graal. my friends used it ever since it came out and the only problem he has had is graal aswell..

think it will work if i copy my graal folder from my old computer onto this one?

alright i gave it a try, i logged in and started up UN, i was running around for around 3 seconds before it crashed..
sorry about the triple post, but the game runs fine with in v3, tried the offline test but the v4 exe doesnt really work at all..

http://forums.graalonline.com/forums...ad.php?t=70476

After seeing that forum post I wonder about this.

Does Graal 4 have some type of memory checker? The Windows Emulator Microsoft built is indeed designed to run 32 bit applications, but in its own way. That would mean utilizing abnormally high amounts of memory from the 64 bit processor.

I can launch Graal 4 on XP 64, yea, but only after a fresh install. If it updates it wont run graal 4 anymore, and it would have to be completely redownloaded and installed. The EXE is somehow changing so it will not launch but I am attempting to look into this some.

So far the XP 64 wouldnt relaunch the game, but when I went back to XP 32 bit editions it would again run the exe.

Well so far I managed to atleast launch the game after clicking on it several.. hundred times. But its running for now, guess I probably could figure out why its running now, and not earlier.

**Seems that Graal 4 actually runs now, it might be possible something in the windows 64 has to configure the EXE or something to correctly run it, this might also be why Stefan says it works for some and not others. I have a feeling it might take windows several tries to properly run the application.

At this time it looks like a standard installation of XP x64 works fine after some time of retrying.

ok, i'll go back and click the exe a hundred tims, brb.

tried it, came up for a few seconds sometimes but usually crashed soon after.. didn't have any successes though..

Yes, there are memory checkers in Graal. Also it might help to turn off the code-execution protection.

how do you do that?

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.

damn, strangely enough launching teamspeak first makes graal run fine, i've been on for 10 minutes now and still not crashed..

i had itunes open when i did that, i just closed itunes and graal crashes instantly :P

wouldnt start for a while, had to get windows media player 11, itunes, teamspeak and 2 firefoxes up before it launched again..

yea, but when I launched JUST TS, it was rather clear to what needed to be done.

any idea how to get it running without launching 15000 programs?

The only possible way would be for Stefan to fix the program itself. I have to launch a few programs just to play, and there is no garuntee it won't randomly close on me. I am seriously starting to want to play another game with this graal, keeps closing out on me for no reason.

I spend more time at the login window TRYING to click connect 50 times to get onto GK.

...it closed again.. Serioulsy this is like the 50th time today!

Windows XP 64-bit edition is known to cause a lot of problems with existing software.

Unfortunately it is difficult for Stefan to fix the program when he does not have access to a 64-bit machine himself.

I will say it again, I would help if I could. Graal Staff are KNOWN to be paranoid.
How about a client that would report bugs to a graal sever automatically, so you could atleast SEE what is going wrong. I'd be more then happy to participate in something to better graal.

So far it seems like theres a sound and/or memory bug with graal4 in the windows 64bit environment, but I have no logs to check, or no debug program for it.

Upon further thought of the issue, a 32 bit codec or software to control something like a microphone could cause bugs in the system. Simply because windows 64 bit just refuses to use 32 bit drivers, though all our problems wouldnt exist if it was compatible with some sort of 32 bit to 64 bit driver emulation, but thats up to microsoft.

There is nothing inside Windows Event Viewer (Control Panel -> Administrative Tools), or your graal4console.log?

No sir, it crashes and reports nothing to the Windows event logger or the graal4console.log file.
I have not been able to locate anywheres on my computer yet to anything crashing or failing to load on the attempted launch of graal, without a teamspeak client running.

I would be atleast willing to beta test various settings or software if it would make any difference in the development in a Graal 4 client that is actually stable in 64 bit. If you simply ask others as well, I'm sure you could also find others that would participate in such a deed.

Unfortunately, 64 bit is not known to cause any problems at all. It is actually quite the opposite, the programs written in 32 bit, cause problems with 64 bit environments. Usually its a 32 bit driver or 32 bit interface to a driver that fails. The fail-safe of either the 64 bit Operating system, or the program will kick in and terminate either. Usually when the OS crashes, it never is pretty. When the Application crashes, there is little evidence of what occured.

My Question, would there be any possible way I could help debug the program?

I really just want to get onto GK and just play for a bit. Its becoming increasingly difficult to even keep the window running long enough to do anything at all. Times it closes when I try to message someone, or when I go check a forum post. Or even when I try to type to someone in game it might close. I find no setting to stop this program from closing itself out.

I have read on the forums somewheres, about an "anti-hacker" tool built into graal 4 client. This I feel is causing some serious problems to all the 64 bit users.

So far 64 bit has been the most stable version of windows I have been able to get ahold of for this particular computer. I do not like the idea of having to revert back to 32 bit for a small and supposedly simple application that takes less memory to run then an internet explorer window (or atleast it should). This is just getting out of hand and is annoying me. Would appreciate some feedback on the subject too.

** Took me 4 hours to actually get to my graal console window.. I'm play a mp3 file is why.. Ok atleast look at the sound system in graal 4 "FMod Sounds: using default sound driver". I don't know about you, but for some reason, even turning all my sounds off in the game I still get this message. So I really couldn't tell you if it was a sound driver problem or not.

Interesting, it would seem I have a "WDM" device driver for my Audigy 2 Zs sound card. While using my onboard sound and disabling this WDM driver, graal has become more stable under 64bit XP. Would anybody else like to check for WDM drivers? I would like to see if this is just a single anomoly I have found or is an actual problem for 64 bit graal users. It still crashes but not nearly as bad as it did with it enabled. Still we should consider that we might have a driver effecting some of our computers abilty to play graal on a 64 bit core.

WDM drivers are for ATi, if I'm not mistaken, and I've not found them to be very useful at all.

WDM (Windows Driver Model) " http://en.wikipedia.org/wiki/Windows_Driver_Model "
- From the Wiki page : "...Thousands of lines of support code are required for every driver..." atleast this explains why a simple driver is 30+ MB in file size.

Basically its usually a huge driver commonly in very easily screwed up Binary coding (I know this from my Linux computers), because you have to download it. The internet connections most people have are not the best. Its also easy for hardware errors like your harddrive or slightly faulty ram or even system lagg or other bad drivers to cause read errors in even just a few of the lines of code could cause severe damage from what I am understanding when I read that description from WDM.

To be truthfull, my computer is MORE stable with older WDM drivers for my Audigy 2 zs then the newer ones, not to mention even more stable when the entire bloody thing is disabled. So I am more definately thinking we have some bad drivers causing us alot of "hell" when we try to play.