Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!clyde.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!noose.ecn.purdue.edu!samsung!usc!hacgate!ashtate!dbase!tomr
From: tomr@dbase.A-T.COM (Tom Rombouts)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Wait States
Message-ID: <1991Feb7.200218.7125@dbase.A-T.COM>
Date: 7 Feb 91 20:02:18 GMT
References: <1991Jan31.231754.5843@cs.mcgill.ca>
Reply-To: tomr@dbase.UUCP (Tom Rombouts)
Organization: Ashton-Tate
Lines: 15

In article <1991Jan31.231754.5843@cs.mcgill.ca> storm@cs.mcgill.ca (Marc WANDSCHNEIDER) writes:
>
>     Could somebody with an urge to type please tell me what a Wait state is?
>I have a vagues idea, but would like to learn about what they are, and how
>they relate to RAM speeds, and how caches help override them....

The best discussion I have seen of wait states and other "cycle eaters"
is in Abrash's "The Zen of Assembly Language."  .ASM seems to becoming
a lost art in this day and age of code generators and OOPS, but
Abrash's book is among the best there is for MS-DOS.
(The book is part of a three book series on assembly lang by
 Scott-Foresman publishers.  (A quasi-guess, my copy is at home)


Tom Rombouts  Torrance 'Tater  tomr@ashtate.A-T.com