Date:	Sun, 5 Aug 2001 13:19:51 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Andrew Cottrell <acottrel AT ihug DOT com DOT au>
cc:	djgpp-workers AT delorie DOT com, Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Subject:	Re: Windows 2000 utime query
In-Reply-To:	<011e01c11d8c$b8c72390$0a02a8c0@acceleron>
Message-ID:	<Pine.SUN.3.91.1010805130951.11228A-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sun, 5 Aug 2001, Andrew Cottrell wrote:

> > > I  may have found another low level problem with Win2000, this time with
> > > utime.
> >
> > Another known problem which wasn't fully debugged yet.
>  I just searched the mail archives fro the last year and didn't spot any
> messages. Has this been previously discussed?

Try looking for messages which talk about touch or utime.  I don't 
remember the subject, but I do remember the problem being reported, more 
than once.

> I added printing of AX after the int21 call and the results are included
> below, it appears that the function 5701h / 5705h / 5707h are not supported.
> I also tested AX=5707 and it also failed with a value in ax of 0x0001 and
> flags = 0x0003.

Are they insane??  Function 5701 was introduced with DOS 2.0!  How can 
they fail to support it and not risk breaking existing programs?

Could you please play with values of date and time passed to function 
5701, to see if the failure is limited to some special values?

Failing that, I think this is such a blatant bug that it should be 
reported to Microsoft with a vengeance.

> After looking at Ralph Brown interrupt list and doing some searching I
> wonder if there is something missing as it seems strange for these functions
> not to be supported under Windows 2000.

To say the least.  Perhaps the Microsoft Knowledge Base has something 
about this?

- Raw text -