To: opendos AT delorie DOT com
X-Comment-To: "da Silva, Joe" <Joe DOT daSilva AT emailmetering DOT com>
References: <01FD6EC775C6D4119CDF0090273F74A4022040 AT emwatent02 DOT meters DOT com DOT au>
Message-Id: <2.07b7.NWIX.GCAS3I@belous.munic.msk.su>
From: "Arkady V.Belousov" <ark AT belous DOT munic DOT msk DOT su>
Date: Tue, 24 Apr 2001 16:59:42 +0400 (MSD)
Organization: Locus
X-Mailer: dMail [Demos Mail for DOS v2.07b7]
Subject: RE: DOS issues #1.1
Lines: 35
MIME-Version: 1.0
Content-Type: text/plain; charset=koi8-r
X-MIME-Autoconverted: from 8bit to quoted-printable by postbox.mos.ru id f3OEA1N18503
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id JAA32178
Reply-To: opendos AT delorie DOT com

X-Comment-To: da Silva, Joe

óÁÌÑÍ!

24-áÐÒ-2001 13:52 Joe DOT daSilva AT emailmetering DOT com (da Silva, Joe) wrote to
"'opendos AT delorie DOT com'" <opendos AT delorie DOT com>:

>>      Below my addition to RBIL (just for programmers note):
>> ______________O\_/_________________________________\_/O______________
>> - `B-1A00':
>> >BUG: Under W4WG midnight flag may not be returned (AL is zero, even if
[...]
dJ> Yes ... I'm sure your explanation of the problem is correct,

     I know this, because may prove this with the working sources. :) :(

dJ> although I found this problem using just M$-DOS or PC-DOS
dJ> (ie. no Windoze involved).

     This only mean _another_ bug/problem.

dJ> However, the suggested solution does not work! Years ago,

     This works for me! And I even don't know precisely why: if I not see
the midnight flag after B-1A00, then why it seen by DOS, _if I not call_
B-1A00 function (as I say, if I see midnight flag after B-1A00, then DOS not
see it after this; flag in memory remained uncleared before DOS calling) and
check midnight flag only through direct memory access?!

dJ> I tried to write a TSR to do exactly this. However, although
dJ> under normal circumstances this was well behaved, it "hung"
dJ> the PC every once in a while (probably due to re-entrancy
dJ> issues with DOS)! Then I discovered that DR-DOS 6.0 did
dJ> not have this bug, so the solution was to change to DR-DOS
dJ> (BTW, DR-DOS 7.0X is also OK).