CompuServe Messages

Kevin, Thanks for the good words, I'll respond to Larry's last threads on this message too. First, I realize fully what is required in terms of using system calls vis-a-vis the multi-tasking kernal routines. What I was referring to in terms of "byte level access" and "port" access were meant to refer to the "insides" of any of the specific device drivers. I started programming, and got my CS degree, on an Amdahl mainframe, so I definitely grasp the idea of multi-user and multi-tasking OS's. But to limit the OS by not providing info on peripherals (like the A2090)t( is very restrictive on C='s part{. (I,ve got some garbage on the line…bear with me) In terms of my capabilities as an ASM proficient programmer, I use C whenever possible and have been using Unix and C systems since C was B! However, you don't write a device driver in C or any other HLL unless you care not about speed, and my references to bytes and ports were valid in that context{. Who, at C=, can say that they have written a device driver (or customixzed(sixc) one), without resorting to port access and byte level communication to the device? If any one has examples to the contrary, please post for my continuing education, Thanks, Griffith