You can look at the book yourself on Archive. That very first page lists it requiring a MASM compatible compiler, and a Windows compatible C compiler. With some of the code requiring Win95 or NT. So you'll want a 32-bit compiler.

How about reading it and finding out for yourself?

https://www.drdobbs.com/parallel/graphics-pro … -book/184404919

Although if you don’t mind me saying, from all your other posts it seems like you’re trying to run before you can walk… I’d focus on getting to grips with the fundamentals of programming in C since that seems to be your preferred language before going anywhere near assembly.

Thanks for this information. I was wondering if it was MASM and Win 95. In my limited view I had no idea there was an assembler for Windows 95 but now I know something about it.

As for C, I finished a textbook on C called "C How to Program" by Paul & Harvey Dietel. The examples in the book are works of a genius. However, the book doesn't help you also be proficient. Learning assembly code is the most practical way to become a programmer. Otherwise you have to study computer architecture. And I really only care about how the processor works. I found out MASM is alive today and it comes with visual studio. I am reading a book called "Assembly Language for x86 processors" by Kip Irvine. Several years ago I completed a course in trade school on digital electronics. Processors are the next step in the progression. Otherwise you have the computer Science curriculum of a university. They take courses in computer organization and study several semesters of calculus. Useful to becoming a developer. But I just want to stick with a practical set of courses. Hands on.

Too bad they dropped inline assembly in x64 in Visual C. Now you'll need to compile assembly into its own module if you want to use it in x64 targets.