Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!ut-sally!im4u!rutgers!mit-eddie!uw-beaver!tektronix!reed!trost
From: trost@reed.UUCP (Bill Trost)
Newsgroups: comp.sys.tandy
Subject: DOS WARS (Re: Ldos vs. NeWDOS)
Message-ID: <7118@reed.UUCP>
Date: Wed, 9-Sep-87 19:46:03 EDT
Article-I.D.: reed.7118
Posted: Wed Sep  9 19:46:03 1987
Date-Received: Sat, 12-Sep-87 06:26:24 EDT
References: <52@nancy.UUCP> <18@umn-d-ub.D.UMN.EDU>
Reply-To: trost@reed.UUCP (Bill Trost)
Organization: Reed College, Portland OR
Lines: 19
Keywords: Steven Speilberg
Summary: TRSDOS loading is very flexible

In article <1123@bsu-cs.UUCP> dhesi@bsu-cs.UUCP (Rahul Dhesi) writes:
% I used TRSDOS and later LDOS back when I used a TRS-80.  Both have a
% serious design flaw.  They both want programs to load at a specific
% address.  Worse, the original TRSDOS had all the system calls at
% absolute addresses that had to be hard-coded into every program.  This
% is bad software design at its worst.

I think that your understanding of TRSDOS is less than you suspect.
Not only will it allow you to load a program into memory anywhere
above the overlay area, but it will allow you to load different pieces
into different chunks of memory, a process known as scatter loading.
This allows you to some really neat and nifty things, like loading
drivers into high memory or even loading into screen memory instead of
having to draw an opening string.
-- 
...!(ogcvax|tektronix)!reed!trost @ All characters @ My opinions may or
"Ooh ick!" -- Penfold, anonymous  @ are ficticious @ may not represent
assistant of *Dangermouse*, the	  @ unless they    @ those of my employer,
world's Greatest Secret Agent     @ are real.      @ etc, etc.