Wow, that would be super kind to have a MoI demo for Wine to test with!

I went ahead and installed the Microsoft DirectX 9.0 SDK (Summer 2004) in Wine and continued some testing. Starting the Text3D.exe now results in a backtrace:

wine: Unhandled page fault on read access to 0x00c66c7c at address 0x430ddf2b (thread 0009), starting debugger...
Unhandled exception: page fault on read access to 0x00c66c7c in 32-bit code (0x430ddf2b).
...
Backtrace:
=>0 0x430ddf2b _xrenderdrv_ExtTextOut+0x95b() in winex11 (0x0032f708)
1 0x4282ef38 _ExtTextOutW+0xeb7() in gdi32 (0x0032f958)
2 0x0102ff13 in text3d (+0x2ff12) (0x0032f9bc)
3 0x01030980 in text3d (+0x3097f) (0x0032fa84)
4 0x01031de8 in text3d (+0x31de7) (0x0032faac)
5 0x0101f4e8 in text3d (+0x1f4e7) (0x0032fc30)
6 0x0107e657 in text3d (+0x7e656) (0x0032fd44)
7 0x0107fbc3 in text3d (+0x7fbc2) (0x0032fd78)
8 0x0101fe65 in text3d (+0x1fe64) (0x0032feb0)
9 0x7b84ebbc _call_process_entry+0xb() in kernel32 (0x0032fec8)
10 0x7b851a77 _start_process+0x66() in kernel32 (0x0032ff08)
11 0x7bc65d8c _call_thread_func_wrapper+0xb() in ntdll (0x0032ff28)
12 0x7bc66e8a _call_thread_func+0x89() in ntdll (0x0032ffa8)
13 0x7bc65d52 _call_thread_entry_point+0x11() in ntdll (0x0032ffc8)
14 0x7bc3f39e _start_process+0x1d() in ntdll (0x0032ffe8)
…

But I also tried the SkinnedMesh.exe and the StateManager.exe and both ran fine! I think they are much closer to MoI's needs with displaying meshes. So I think basic 3D functionality via Wine/DX9 is supported on the GMA X3100 hardware. The rest I hope is just tuning registry and dlls…

Will have a closer look at Wineskin today.

Looking forward happily,
Chyman