Hmmm, I had a similar issue when using a laptop while waiting for my new work box to come in. I basically could not use MOI on it. It had a crappy ATi video card but that one you have should run it.

Can you please give this a try - make sure the MoI window is maximized, and then hold down the Ctrl key and click on the "MoI" caption in the upper-right corner of the window (next to the minimize/restore/close buttons).

This will pop up a debug menu, on it, pick the one named "Show Log". This will show a dialog that contains some text which are diagnostic messages that are output when things aren't working as expected. If you can copy and paste that text over here, it might help me figure out what part is not working properly.

Also, are you using the most recent beta release (Oct 9th) ?

Thanks,

- Michael

Here is the log that you asked for. Not sure if it makes a difference but this is a 64MB video card, but I am running 2 gigs of RAM.

.\Init.cpp 116: Moi starting up
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518
.\Direct3D.cpp 148: GetDeviceCaps failed hr = -2005530518
.\Direct3D.cpp 525: CreateDevice failed hr = -2005530518

Also I am using the Oct 9th edition

If you go to Start / Control Panel / Display / Settings tab, do you see 2 monitors listed in there?

Can you click on each monitor (click on the large blue boxes labeled "1", and "2"), and see if any of them does not have the "Extend my Windows desktop onto this monitor" setting checked on it?

You might try making sure each of those is checked, and also try flipping which one is set up as the primary monitor.

Also, can you please try rebooting your machine and see if that has any effect?

- Michael

One other thing to try - go to dxdiag.exe, and under the display tab, next to "Direct3D Acceleration", click "Disable". After that click "Enable". That might possibly re-initialize some stuff that is messed up in Direct3D for you.

- Michael