> Now, on XP it still runs, but...
>
> * BGFX asserts at start, reason unknown.
>
> * Opengl crashes, probably video driver incapable of supporting it.
>
> * DDRAW and GDI work.
>
> * D3D gives only a black screen, even though directX passes all the dxdiag tests.
> Using DX9.0c. If you start a game from the command-line, it runs but you can't see
> anything. Current GIT version will freeze instead of showing the UI. If you tell it
> to show the old ui, then it doesn't freeze, but it's still black.
>
> I'm looking for suggestions from others that have XP on how to fix these issues - if
> it is fixable.
I can verify all these issues.
Upon testing 32-bit MAME 0.170+ compiled as of this revision:
https://github.com/mamedev/mame/commit/5258f167af35470690710e3f63069fc124f2dffc
Host machine: Dell Inspiron 700m
http://www.cnet.com/products/dell-inspiron-700m/specs/
(Positively pathetic hardware these days)
Video card: Intel(R) 82852/82855 GM/GME Graphics Controller
(ancient)
OS: Windows XP SP3 with latest drivers and updates
Game: Blasto (Gremlin, 1978)
Issues: See Pastebin for the full verbose log.
http://pastebin.com/1yMAYeK5
Comments:
- ddraw and gdi worked fine.
- opengl crashed as described.
- d3d seemed to run with the exception that you couldn't see anything, as mentioned above. I don't think it froze with the new UI since I was able to start the game blind.
- bgfx did not crash with a stack crawl but rather "This application has requested the Runtime to terminate it in an unusual way." with nothing logged.
- as it turns out, theme in common with Robbbert's test: Intel 855/865 graphics.
- Stiletto
Edited by Stiletto (02/11/16 12:38 PM)
|
Index 
Flat 
Re: MAME on XP
Reply
