Jump to content
  • Advertisement

Archived

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

Mike38722

Writing Assembly interrupt for 13h

This topic is 6110 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''m trying to make a program with graphics in Assembly. My computer freezes when I try to use int 10h to load VGA mode 13h. I''m using Windows 2000 on a Thinkpad. If anyone could help, it''d be greatly appreciated.

Share this post


Link to post
Share on other sites
Advertisement
Windows 2000 doesn''t allow direct hardware access. You won''t have much luck trying to change video modes in assembly.

Share this post


Link to post
Share on other sites
*WHY* would you want to use VGA 13h in Windoze?
My suggestion: Either use DOS (since this is more like a DOS programming technique) or switch to DirectX/OpenGL.

---
Allow me to clear my head for once...
Stop polluting the air!

Share this post


Link to post
Share on other sites
quote:
Windows 2000 doesn''t allow direct hardware access. You won''t have much luck trying to change video modes in assembly.

It works fine for me.

Share this post


Link to post
Share on other sites
Let me clarify myself.

I'm writing a DOS program, but I'm trying to run it with a full-screen under Command Prompt in Windows 2000.

The following sequence of instructions freezes my computer:

mov ah, 0
mov al, 13h
int 10h

Is there something I was supposed to do, but I didn't? Is there another register I'm supposed to load that I haven't?

Edited by - Mike38722 on November 20, 2001 3:47:20 PM

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
Those instructions are priviledged - can''t be run in user mode - aka "ring3" - they have to be issued at "ring0". DOS doesn''t exist on W2K - don''t confuse a console with DOS - they only look the same :-)
Like the other poster mentioned - you''ll need to use DX, OGL or - gasp - GDI.

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
To follow up - there are workarounds - (search google for "callgate" - also search for the online version of "Undocumented Windows NT") - using a dll to interface with device drivers and such. This workaround is such a pain that you might as well use DX/OGL/GDI.

Share this post


Link to post
Share on other sites
quote:
The following sequence of instructions freezes my computer:

mov ah, 0
mov al, 13h
int 10h



Sorry, I can''t help, all I can say is that this code works fine on my computer with Windows 2000, so it seems strange that you have problems...

Share this post


Link to post
Share on other sites

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!