delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/2001/05/01/06:25:32

From: "The Owl" <theowl AT freemail DOT c3 DOT hu>
To: sandmann AT clio DOT rice DOT edu, djgpp-workers AT delorie DOT com
Date: Tue, 1 May 2001 12:24:14 +0200
MIME-Version: 1.0
Subject: Re: win2000/ntvdm/djgpp (fwd)
Message-ID: <3AEEAAEE.11546.7F1F43B@localhost>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp-workers AT delorie DOT com

uhm, i think i forgot to cc this one...

------- Forwarded message follows -------
From:           	The Owl <theowl AT freemail DOT c3 DOT hu>
To:             	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Subject:        	Re: win2000/ntvdm/djgpp (fwd)
Send reply to:  	theowl AT freemail DOT c3 DOT hu
Date sent:      	Mon, 30 Apr 2001 21:18:25 +0200

> > the set-PSP event chain is started by a dpmi app issuing a pm int 21.
> 
> Yes, but where does this PM Int 21h come from?

i was talking about the first proposed workaround, ie. issuing a pm int 21
in a dpmi app (somewhere in libc) and how the chain of events would look
like (to show how it would fix the problem by restoring the correct value
in _CurrentPSPSelector in ntvdm). maybe i misunderstood your questions and
answered the wrong thing?

> I'm sorry for this nitpicking, but I'd like to have a clear
> understanding of this issue, in case we do decide to issue a PM Int
> 21h as a means of solving this.

no problem, i think i must have lost track somewhere, please restate
your questions.

> If Int 21h/AH=51h works, it is indeed safer, because it shouldn't do
> any harm when the program runs on DOS.

agreed, and i would personally prefer it to int 21/50.

> The main reason I hesitate to go with the patch is that it might be
> impossible for users to do that.

i am aware of this and i actually did not mean to say that the possible
workarounds were mutually exclusive. rather i wanted to provide one
'quick' solution for those of us who did not want to wait until the
second solution is made available in the next release of djgpp. in
other words, the pm int 21 workaround must be implemented regardless
of the existence of the patch, the question at this time is, which one,
50 or 51 (based on my knowledge and the messages in this thread so far,
i think 51 is the way to go).

> So I would like to modify the library to issue a PM Int 21h/AH=50h in
> the case the program runs on NT or W2K, and post the diffs here, in
> case you could rebuild Make and your other applications used to test
> this, and see if the problem is solved by this change.  Would that be
> okay?  will you have time and resources to make these tests?
> 
> I can also provide another set of diffs that use Int 21h/AH=51h, so
> you could see if it indeed works, again, if you think you will be able
> to test that.

of course, i will test out anything, just let me know what to patch.
i expect the whole patch would be a few lines in assembly, so if you
give me the file name and line number, i can work it out myself and
quickly test it here (both 50 and 51).
------- End of forwarded message -------

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019