http://bugs.winehq.org/show_bug.cgi?id=22467
--- Comment #10 from edward savage epssyis@gmail.com 2010-05-05 05:07:54 --- Right, using the current git you can get NS2 test engine running by setting your VideoMemorySize to an insane value. Via regedit add HKEY Current User -> Software -> Wine -> Direct3D and a key of VideoMemorySize and a value of upwards of a GB or more. NS2 will crash complaining of lack of memory if I have this value any less than ~800mb while my card only physically has 256mb.
I don't know how much luck you will have with 1.1.43 but the mmdevapi issue appears to have cleaned up some time between 41 and current git.
There are a couple of changes to Wine between the known good case that ran well (5 FPS+) and it running worse that make finding any regression really time consuming. On top of this there are many issues with the Engine Test itself. I would suggest a better approach would be to isolate bugs with the graphics only and attempt to fix those and wait for the next Engine Test release.
With the graphics bugs addressed I'm pretty confident an optimised NS2 will run rather well. I will update this bug when I've had a chance to track down the graphics errors that are being generated.