Archived

This topic is now archived and is closed to further replies.

OS Compatability Help

This topic is 5579 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I built and debugged my game on Win XP Home Ed., and so far that''s the only OS it doesn''t crash on... Can anyone provide my with some things to look out for, pertaining to DirectX programming, pointers, etc. that might be problematic for a game running on various different OS-es? I''ve tried my game on Win 98 and XP Professional (both with the DirectX requirements met or exceeded; game is written in 8.0). My game runs on other XP ome Editions, if that means anything. The "Details" of the crash in Win 98 are the following: AMERICAN FRONTIER MAN caused an invalid page fault in module AMERICAN FRONTIER MAN.EXE at 017f:00401b48. Registers: EAX=00000000 CS=017f EIP=00401b48 EFLGS=00010206 EBX=00690000 SS=0187 ESP=0079fd50 EBP=0079fd54 ECX=fffffffd DS=0187 ESI=00000000 FS=5a07 EDX=00000000 ES=0187 EDI=00000000 GS=0000 Bytes at CS:EIP: 8b 08 8b 15 4c 8c 43 00 52 ff 51 08 a1 50 8c 43 Stack dump: fffffffd 0079fdac 004013e0 00000001 00000001 00000080 0079fd7c 0079fe28 00426618 00ce0e60 00000030 00000023 00401288 00000000 00000000 00400000 Again, if anyone has some general insight, or if those details suggest that I''m doing something stupid, please reply. Thanks a bunch.

Share this post


Link to post
Share on other sites
Well, I brought the ol'' source code to my Win 98 machine and started debugging. Turns out the LPDIRECT3D8::CreateDevice(...) function is failing during initialization. I''ll check into reasons this might occur, and repost if I can''t figure anything out. Thanks for the help!

Share this post


Link to post
Share on other sites
Yeah it seems that XP is very forgiving when it comes to pointers and access violations and the like. I have written a game in Win98 that crashes at a certain point (due to access violation) but nothing happens at all in XP.

''Your theory of a donut shaped universe is intriguing Homer'' - Stephen Hawking

Share this post


Link to post
Share on other sites
Well I haven''t been able to discover anything helpful. Anyone care to tell me what it means if CreateDevice(...) fails? What kind of problem does this indicate? Hopefully it''s a hardware incompatibility and we programmers can just tell the end user to upgrade Thanks in advance!

Share this post


Link to post
Share on other sites
Is it the same hardware as the XP one? Perhaps you''re asking for capabilities the hardware doesn''t support...

Also, XP, if anything, would be less forgiving with respect to access violations, etc. It''s probably a bad driver or something in 98 that''s causeing the AV.

If I had my way, I''d have all of you shot!


codeka.com - Just click it.

Share this post


Link to post
Share on other sites