Gerry, 09 Aug you wrote to Darin Mcbride:
 GD> I've never used volatile on any direct screen I/O.  Perhaps
 GD> that's because under single-tasking DOS that's not a problem.  
It would be a problem if your compiler optimized better, all screen output 
could be removed, since you didn't tell the compiler that is was volatile. 
volatile can also mean that other processes are influenced by the values your 
program puts there, just as it can mean that other processes may influence 
your program by putting values there. ;-)
Bye,
 Erik 
---
---------------