home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cbmvax!rutgers!utcsri!skule.ecf!torn!nott!cunews!freenet.carleton.ca!Freenet.carleton.ca!aa302
- From: aa302@Freenet.carleton.ca (Russell McOrmond)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: New hardware reference guide?
- Message-ID: <1992Nov13.211221.1609@freenet.carleton.ca>
- Date: 13 Nov 92 21:12:21 GMT
- References: <1dosbvINNa4n@uwm.edu> <1992Nov4.134857.24783@sth.frontec.se> <BxGvwE.4op@visix.com>
- Sender: news@freenet.carleton.ca (News Administrator)
- Reply-To: aa302@Freenet.carleton.ca (Russell McOrmond)
- Organization: Carleton University, Ottawa, Ontario, Canada
- Lines: 32
-
-
- In a previous article, bloc1469@ee.ee.uwm.edu (Gregory R. Block) says:
-
- >In article <BxGvwE.4op@visix.com> brett@visix.com writes:
- >>Please! Hitting the hardware != POORLY Written Software
-
- >Fortunately, it does as of 3.0. And frankly, I'd rather see DIG than
- >the newest version of Frogger, 'kay? ;)
-
- There are always going to be legitimate reasons for hitting the hardware as
- there will likely always be conditions where CBM doesn't provide the right
- functionality in their O.S. that is required for certain applications. I
- know you are a Welmat user and by your definition Welmat is
- a poorly written package because it has to hit the hardware in order
- to get control over the DTR line on the internal serial port. It would
- be seconds for CBM to fix this blatantly obvious bug that they were informed
- of quite some number of years ago, but so far they have not.
-
- I myself don't know much about the reasons why other hardware is hit, but
- from this simple example I bet there are legitimate reasons for getting
- around bugs in the O.S.
-
-
- --
- Russell McOrmond, Ottawa Ontario, Canada | Standard Disclaimer applies.
- Freenet: aa302@freenet.carleton.ca (Faster) | Current WELMAT 'keeper of
- Home: rwm@Atronx.OCUnix.On.Ca, 1:163/109 | sources.
-