Jump to content
Sign in to follow this  
chiefwhosm

aken64.sys

Recommended Posts

Hi,

Built the game from source, went smoothly enough bar the 503 errors ;) On getting in game, windows vista 64bit home premium alerted me to a non-digitally signed driver:

aken64.sys

that was attempting to run, and warning me that all drivers had to be digitally signed, and this driver would not be allowed to run.

After clicking OK, the error went away and the game continued, seems to be running just fine.

Just wondering what it actually is, and how much of a problem it poses by not being allowed to run?

Chief :)

Share this post


Link to post
Share on other sites

Aken and Mahaf are somewhat fitting (see http://www.touregypt.net/godsofegypt/mahaf.htm) names for a kernel-mode service and user-mode library that calls it to action. They are used for mapping physical memory and port I/O, which are required for ACPI table access and proper high-resolution timing due to various bugs in chipsets and Windows XP.

If disabled, the timer falls back to the usual Windows API routines, which are prone to problems (see http://www.gamedev.net/community/forums/to...opic_id=451305; the PDF referenced therein is now located at http://algo2.iti.uni-karlsruhe.de/wassenberg/timer_test.zip).

The driver isn't signed because I don't have the means of doing so; if you are able or know someone who can, help would be very much appreciated.

Share this post


Link to post
Share on other sites

http://www.verisign.com/code-signing/conte...code/index.html

Bit expensive huh.

You say it's for Windows XP, well i'm on Vista, do the same chipset problems occur. If not couldn't the 0ad code be altered to detect the OS and thus not bother loading the driver on versions of windows over XP.

Of course, this error will only affect 64bit users I think.

Chief :)

Share this post


Link to post
Share on other sites

> Bit expensive huh.

Yeah, that's out of the question :/

You say it's for Windows XP, well i'm on Vista, do the same chipset problems occur. If not couldn't the 0ad code be altered to detect the OS and thus not bother loading the driver on versions of windows over XP.

Vista+ already have such a driver built into the OS, so there's hopefully no need for ours (barring any further screwups and bugs). I suppose it would be possible to disable the corresponding code on Vista - would you be interested in doing so?

You can also launch with -wNoMahaf on the command line for the same effect.

Of course, this error will only affect 64bit users I think.

hm, why would the driver signing only be an issue on amd64?

Share this post


Link to post
Share on other sites
would you be interested in doing so?

I'm no coder :) I was just lucky in the fact that compiling to the wiki's instructions went without a hitch ;)

hm, why would the driver signing only be an issue on amd64?

Because 64-bit versions of windows have to have their drivers signed. This restriction isn't on 32bit versions.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...