From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (qmail 18489 invoked from network); 4 Dec 1996 21:15:50 -0000 Received: from connect.reach.net (root@204.50.58.1) by mail2.redhat.com with SMTP; 4 Dec 1996 21:15:50 -0000 Received: from C116.reach.net (C116.reach.net [204.50.58.148]) by connect.reach.net (8.7.5/8.6.9) with SMTP id QAA29857 for ; Wed, 4 Dec 1996 16:15:14 -0500 Date: Wed, 4 Dec 1996 16:15:14 -0500 Message-Id: <199612042115.QAA29857@connect.reach.net> X-Sender: blindnet@connect.reach.net (Unverified) X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: blinux-list@redhat.com From: blindnet@connect.reach.net (Jim Corbett) Subject: Drivers question / statement. List-Id: Hello there, I posted a message yesterday, and wow what responsce. Nany thanks. However I have one point that I would like to argue. That being C . No matter what language you use to develope the source code, the compiling and linking procedures convert the source into machine level instructions, or dam near it. Since C was developed with hardwware in mind, it is more than capable of working at this level. It has the ability to work with BIOS, interrupts, IRQ's and do a hell of a gob as well. I have only been playing with C and C plus plus for one year and I am already able to write programs to manage interrupt conflicts. Equally as well Assembler was developed for the same purpose in mind. Most of the com files that are currently in use were written in Assembler. If the will is there, we need not rely upon companies to provide us with pre written drivers. Its great if they will provide a utility that will allow us to tackle our own drivers, but if its not available we shouldn't sit around on our hands. There is many powerful languages out there ready to be used for such a task. I not saying that I am the greatest programmer, but only with a years experience I am having a ball playing around with this stuff. its challenging to see what I can come up with. Just my opinion, thats all. Never say never. Jim Corbett BLINDNET@reach.net Jim Corbett BLINDNET@reach.net