Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

hardly a 100% solution (Developers)

posted by ecm Homepage E-mail, Düsseldorf, Germany, 30.05.2011, 19:33

> Not an error, but yes a failure due to a rude TSR not acting responsibly!
> Being able to preempt both the foreground task and the OS itself is a
> privilege, with privilege comes responsibility - at least I was brought up
> thinking so.

In my method, there isn't any way for the TSR to determine properly that it acts "not responsibly". In your method of protecting the section by clearing the interrupt flag, there arguably isn't either: If the protection works as intended, the TSR won't pop up. If it fails (21.48 call, running in debugger, running in V86-mode?) the TSR has no way of determining you intended to leave the interrupt flag disabled.

> "Alternate method 1" sketched in my previous post, under CLI, would
> completely prevent the potential for such nuisance.

No, because as I alluded to, resident code could allocate the memory that would be required for your optimal allocation (say, a UMB of just the right size) before you enter your protected section of code.

---
l

 

Complete thread:

Back to the forum
Board view  Mix view
22049 Postings in 2034 Threads, 396 registered users, 185 users online (0 registered, 185 guests)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum