From:	Ben Peddell <killer DOT lightspeed AT bigpond DOT com>
User-Agent:	Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.1) Gecko/20020826
X-Accept-Language:	en-us, en
MIME-Version:	1.0
Newsgroups:	comp.os.msdos.djgpp
Subject:	uclock() still out by 1 in 65536
Lines:	17
Message-ID:	<4wyBa.45993$1s1.615094@newsfeeds.bigpond.com>
Date:	Fri, 30 May 2003 11:42:42 +1000
NNTP-Posting-Host:	144.134.181.221
X-Trace:	newsfeeds.bigpond.com 1054258304 144.134.181.221 (Fri, 30 May 2003 11:31:44 EST)
NNTP-Posting-Date:	Fri, 30 May 2003 11:31:44 EST
Organization:	Telstra BigPond Internet Services (http://www.bigpond.com)
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

I guess I'm probably reporting this to the wrong place.

I know that this is a very small complaint, but uclock() is still out by 
1 in 65536.

     outportb(0x43, 0x34);
     outportb(0x40, 0xff);
     outportb(0x40, 0xff);

I think this should really be:

     outportb(0x43, 0x34);
     outportb(0x40, 0x00);
     outportb(0x40, 0x00);

I guess you could say it's more a tiny inconvenience than a bug.

- Raw text -