JP> 16-bit OS/2 (/i.e./ version 1.x) provides only a means for directly
JP> reading the RTC hardware, Dos16GetDateTime().  It returns the date
JP> and time as a broken-down structure, the members of which are either
JP> UCHARs or USHORTs.  The `Year' field, in particular, is a `USHORT'
JP> meaning that the data structure can cope with years up until the
JP> year 65535.

Excellent!! Directly and unequivocally answers my question! Thank you 
very much! [:)

You did raise another interesting point, however:

JP> (The Dos32GetDateTime() function is still there, for backwards
JP> compatibility and ease of porting 16-bit applications, but this is
JP> really the wrong way to obtain the system time on 32-bit OS/2, since
JP> it hits the clock hardware directly.)

Are you saying that DOSQuerySysInfo() does not get its information 
directly from the clock? If not, how does it keep track of the time?


JP> Operating system kernels are generally the wrong place to look for
JP> Year 2000 problems.

[:))) Yeah, I know. But in my work I can't afford to approach my job in 
a lacadaisical fashion. I've got to know the facts with as little doubt 
as possible.

Thanks for all the info. Take care and TTYL.

---
 þþ Using a TNC is another way to really use a C=64.                        

--- AdeptXBBS v1.11y (FREEWare/2)