This is the official DMDX release page. Ken is still working on the user level documentation, till then DMDX only comes with my help files for documentation and with the new indexing of keywords these are not so bad anymore. They assume you know what Dmastr is and what it is attempting to do. Any questions are to be directed to Ken Forster, kforster@u.arizona.edu and not to me.
Things that I know don't work:
Missing Network. Don't have network software installed but no network connection. The way the network routines (for remote monitoring) are currently built they will hang for either (a) a very long time or (b) for ever trying to do DNS resolutions (I don't have the patience to see if it is the later or former). The code needs to be restructured, unfortunately the way it needs to be restructured is a way I deliberately avoided when creating the code for good reasons. One day I'll fix it, till then don't use TimeDx and DMDX to test your network, make sure it works first or if your machine must be disconnected from the network don't have network software installed.
Color 255255255 is black on some machines, maybe a DX 3 vs. DX 5 thing.
Notes.
Files named DMDXPASS are special versions with passpoints turned on, they generate dmdxpass.txt in the current directory which can be used by me to figure out where DMDX crashed. These should not be used unless you have been instructed by us to do so as I do not update this unless I have to. Files named DEMOS are bundled demo item files and materials.
If you get an error, before asking us for help try the latest version, it will change on a daily basis. SPECIAL NOTE:- This file (official.htm) will not get necessarily get updated as the binaries are updated, you will have to look at the file dates and sizes, I simply change the binaries too often to be updating HTML files all the time as well.
Should you wind up with a hung DMDX and ESC brings no joy (in the form of an Abort? dialog) then CNTRL-ALT-DEL followed by ENTER (sends a message to DMDX to terminate, but it's hung so this won't work) and then CNTRL-ALT-DEL followed by two ENTERs should get you back to the desktop (now explorer sees that DMDX is hung so it's asking you if you want to kill DMDX this time). You may or may not (more likely not) recieve any feedback from the task manager as this is occuring as the GDI will more than likely be writing to a screen buffer that is not visible (on account of GDI being initialized before all the DirectX stuff is, this is normal and expected behavior -- the lack of feedback that is, not the crash). In order to get the desktop back CNTRL-ESC can be used (on some systems). DMDX will still have to be killed CNTRL-ALT-DEL however.
DMDX Official Page.