red_marvin did it, ans so can I...

[red_Marvin]

I did what? :???:

[adosorken]

Ralfie Brown has long had the net's definitive interrupt list.

If my memory serves me correctly, it still resides at www.ctyme.com/rbrown

Ralf Brown is the uncrowned king of the PC. Hands down.

[Zack]

Then let's crown him:
:king:
Btw all, here it is...

Crappy picture, taken with a webcam, but still, I am so bloody freakin' excited. COMES WITH MASM 6.15 FULL! And examples, tons more...aaaah...

[adosorken]

The neat thing about MASM 6 is that later you can take that knowledge and use MASM32 (not made by Microsoft though) to make Windows applications. Identical syntax, afaik.

[Zack]

Um. MASM compiles 32-bit Windows apps. At least, it teaches 32-bit protected-mem coding in the book, and assembles with MASM 6.15.

[Rhiannon]

Um. MASM compiles 32-bit Windows apps. At least, it teaches 32-bit protected-mem coding in the book, and assembles with MASM 6.15.

32-bit protected mode isnt Windows, it's......protected mode.

[Zack]

'Tis what I meant, m'dearie.
My point is, you certainly can assembly Windows apps with MASM 6.15.

[adosorken]

It's a pretty decent book, but I wouldn't trust MASM 6.15 with Windows applications. And 32 bit protected mode isn't the same as a Windows application...when one says "32 bit protected mode", it means it's an app that runs in DOS protected mode. When one says a Win32 application, that's different. Like I was saying though...you can use that knowledge of MASM 6 with the more modern MASM32 when you want to do Windows programming. You can chance it with MASM 6.15, but I wouldn't if I were you... Hence why I hinted to a better assembler MASM32 is what I'm using for final assembly in OBDS. It's an awesome little workhorse

[Zack]

What's wrong with MASM's Windows assembling? Seemed to work fine.
And...thanks for clearing up that confusion about protected mode being different from Windows Apps.
Then I have a question about DOS protected mode. How do you do stuff like put pixels without interrupts, if you can't access vid memory?

[adosorken]

For SVGA modes and stuff, you have a large buffer in memory that is, from what I understand, like a large 13h (all points accessable in one huge array, so to speak). I don't use pmode DOS so I don't know details, you might want to look at Allegro's sourcecode or find nifty articles on the 'net. Suggestion: find the Black Book (sp?) by Abrash.