Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!rutgers!iuvax!bsu-cs!dhesi From: dhesi@bsu-cs.UUCP (Rahul Dhesi) Newsgroups: comp.sys.tandy Subject: Re: Ldos vs. NeWDOS Message-ID: <1123@bsu-cs.UUCP> Date: Wed, 31-Dec-69 18:59:59 EDT Article-I.D.: bsu-cs.1123 Posted: Wed Dec 31 18:59:59 1969 Date-Received: Fri, 11-Sep-87 03:41:59 EDT References: <52@nancy.UUCP> <18@umn-d-ub.D.UMN.EDU> <7863@shemp.UCLA.EDU> <19@umn-d-ub.D.UMN.EDU> <94@stb.UUCP> <24@umn-d-ub.D.UMN.EDU> <132@stb.UUCP> Reply-To: dhesi@bsu-cs.UUCP (Rahul Dhesi) Organization: CS Dept, Ball St U, Muncie, Indiana Lines: 27 Keywords: Dos War In article <24@umn-d-ub.D.UMN.EDU> rhealey@ub.d.umn.edu (Rob Healey) writes: Ah, but the point of minidos is: Any dos command, except copy, format, and append, load into the sys file overlay area, so a program can load at 5200H (or X'5200') and still use dos. (You can copy files with 'mdcopy'). 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. Constrast this with MSDOS. At load time, the MSDOS loader performs relocation of EXE format files, so the code can be loaded anywhere. This is how operating systems should be designed. Even stupid old CP/M would let you build an operating system that loaded into the top of memory, no matter how much memory you had, so applications software and the operating system did not conflict unless you were actually short of memory. Minidos solves a problem that should not exist in the first place. It's been nearly 10 years since TRSDOS was first marketed. It's a shame they still haven't managed to fix its problems. It's time to upgrade to a different oeprating system. -- Rahul Dhesi UUCP: !{iuvax,pur-ee,uunet}!bsu-cs!dhesi