delorie.com/archives/browse.cgi | search |
Xref: | news-dnh.mv.net comp.os.msdos.djgpp:2128 |
Path: | news-dnh.mv.net!mv!news.sprintlink.net!simtel!news.kei.com!news.mathworks.com!uunet!in1.uu.net!noc.near.net!das-news2.harvard.edu!oitnews.harvard.edu!news.sesqui.net!uuneo.neosoft.com!news!sandmann |
From: | Charles Sandmann <sandmann AT praline DOT no DOT NeoSoft DOT com> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Locking memory for interrupt routines. |
Date: | Wed, 20 Sep 1995 20:59:50 CDT |
Organization: | NeoSoft Internet Services +1 713 968 5800 |
Lines: | 6 |
References: | <811601482 DOT 13133 AT alphdyn DOT demon DOT co DOT uk> |
Reply-To: | sandmann AT clio DOT rice DOT edu |
Nntp-Posting-Host: | praline.no.neosoft.com |
To: | djgpp AT sun DOT soe DOT clarkson DOT edu |
Dj-Gateway: | from newsgroup comp.os.msdos.djgpp |
> What I am finding is that my lock function works in a windows DOS box and > fails when I run the program directly from DOS. You are not adding the base of the CS/DS selector to the memory, so you are locking the wrong place in memory (conventional memory in your example).
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |