Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

indirect far jmp - calling old INT problem (Developers)

posted by bretjohn Homepage E-mail, Rio Rancho, NM, 14.05.2012, 21:42

> This will set the Interrupt Flag and/or Trap Flag too early (inside your
> code) if they were clear for your entry and set for the calling code. Right
> here, that might not be a concern, but in general this is incorrect and
> should be avoided (especially if your handler does not return to the caller
> right after the call it made has returned).

You are correct. If you need to do a bunch of "clean-up" or additional processing after issuing the INT 85h (more than simply restoring BP like we do here), you would probably at least want to issue an STI (or CLI, as appropriate). In this example, the state of TF and IF don't affect or significantly delay anything critical, so it doesn't really matter.

 

Complete thread:

Back to the forum
Board view  Mix view
22762 Postings in 2122 Threads, 402 registered users (0 online)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum