delorie.com/archives/browse.cgi   search  
Mail Archives: opendos/1997/02/01/15:48:29

To: opendos AT mail DOT tacoma DOT net
Subject: Re: [opendos] A more ordered fixlist
Message-ID: <19970201.123136.4847.4.chambersb@juno.com>
References: <Pine DOT LNX DOT 3 DOT 95 DOT 970201093351 DOT 4180A-100000 AT capslock DOT com>
From: chambersb AT juno DOT com (Benjamin D Chambers)
Date: Sat, 01 Feb 1997 15:29:54 EST
Sender: owner-opendos AT mail DOT tacoma DOT net

On Sat, 1 Feb 1997 09:36:40 -0500 (EST) mharris AT blackwidow DOT saultc DOT on DOT ca
writes:
>> One of the first things I will do is Direct screen writes, 
>regardless of
>> portability.  Who gives a s***, I want it fast on my PC... ;-)
>
>RIGHT ON!!!!  Thats the good olefashioned PC user attitude I like to
>hear!!!  I HATE programs that do screen output like this:
>
>write("C:\>");
>
>then write() calls superprint() which calls DOS which has been
>intercepted by ANSI.SYS, then the BIOS, then... ...zzzzzz...
>
>4DOS does direct writes (depending on how you set it up).
Question:
OpenDOS is for x86 processors, right?
THEN WHO THE HELL NEEDS IT TO BE PORTABLE?????????
You're not going to break things by inserting a little ASM code - it's
not like it'll run on the Mac anyways :) :) :)
And who's going to be running the command.com from Linux???  Go ahead and
make things fast!

...Chambers

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019