2nd UPDATE 5/23/2004US or 23/5/2004EURO - Added bug fix to all files discovered by inskipp, and added fixes and missing file by I-don
Here are a few new examples from the 'Windows Game Programming for Dummies' book, Chapter 5, and now Chapter 6. See the readme.txt file for instructions on how to setup . Had a cold last week so took a few days longer to code and post . Chapter 7 has no examples so will do Chapter 8. Now you should see some better and better examples in directdraw from here on out . And also hopefully improve my fasmlib library as well.
Any problems let me know and I'll see what I can do.
MadMatt

I thought I could learn something from your fasm window game programming examples. But I must warn any Win95 users, don't event try to run these example on your computer!

Before I explain more, here is my PC specs that I used for test these code:

Intel P3 450Mhz
128MB Ram
4 MB Direct3D Video Card
Windows 95B OS
Internet Explorer 5.1
DirectX 7

It goes the same to your previous examples. All your included or re-compiled executable binaries will freeze the whole windows system threads and only left mouse freely until you press any key and everthing is stoned(remember old DOS Stoned virus?). I test every of each binaries (the original and re-compiled with fasmw 1.52). Stupid of me, I thought this examples also different and test it again. I hate all the system freezing. I guess, it's not compatible with basic Win32 or 386 based processor system. Perhaps, only for P4 and above.

So, I'm giving up on these example. Sorry, no more...!!!

i-don.

Sorry i-don, to here your having such bad problems with the examples . I only have a windows xp system to test these on. I've heard of no other complaints, someone wrote that it worked on windows 2000 pro. I don't know what could be causing your problems . My first thought would be alignment problems. My programs use only as of now, standard 386 instructions. Another is that your OS is very old and outdated. Can you run all the examples provided with FASMW? I was wondering if anyone with windows 98 can run these examples without problems?

Same problem on Win98. My system:

Celeron 333@417
128 MB RAM
Windows 98 (first edition)
Internet Explorer 6
DirectX 8.1
RIVA TNT2

Hello everyone, I have a new version of the chapter 5 winlines example that uses a completly different method to draw lines on the screen, and just as fast. Actually, multitasking on windows xp seems to work better with this new version, and hopefully will work equally well with win 95/98/me systems as well.

I found error in all previos examples. It was the EndPaint fuction, it tooks 2 parameters, not only a pointer to PAINTSTRUCT
I replaced

to

And all works great now.[/code]

Great solution Inskipp. Thanks a lots. Now I can enjoy to learn these great examples converted by madmatt. madmatt, sorry for giving you a troubles, but I think it's worth it as we know where the problem lies. I'm also found the case-sensitive procedure call bug in cpu.asm file. Below I attached fixed for all examples for other win98x users save the time on fixing it. Here the screenshot for the first example and updated source code.

Thanks all,

i-don.

THANK YOU , Inskipp. Well, now I'm all red faced, can't believe it was such a simple solution. I was looking in all the wrong places. I'll have to double check my code and parameters next update. Thanks for posting the fixes as well! Hopefully everything works on your systems now. I-don, no problem, I've just started learning windows assembly as well. I do know 32-bit dos programming quite well, and I took that knowledge and applied it to what I'm doing now, which makes things a little easier (and also some of the code: fasmlib), but even so, the way windows does things is still a whole other world for me. Well, anyways, updates should come a bit faster now that I'm over my cold.... stay tuned
MadMatt

P.S. Thanks to every one for your input

To everyone, this should be the final fixes needed for these files to work on all windows os'es now. When new examples come out, I'll post them with the date that they were posted, and it will be easier to see if you have the latest version and bug fixes of the examples.