Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/5/84; site wlcrjs.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!wlcrjs!marc From: marc@wlcrjs.UUCP (Marc Lavine) Newsgroups: net.micro.pc Subject: Re: Dos Startup modification Message-ID: <555@wlcrjs.UUCP> Date: Sun, 10-Feb-85 22:20:22 EST Article-I.D.: wlcrjs.555 Posted: Sun Feb 10 22:20:22 1985 Date-Received: Mon, 11-Feb-85 06:28:08 EST References: <11841@gatech.UUCP> <307@psivax.UUCP> Reply-To: marc@wlcrjs.UUCP (Marc Lavine) Distribution: net Organization: chi-net, Public Access UN*X, Chicago IL Lines: 24 In article <307@psivax.UUCP> al@psivax.UUCP (Al Schwartz) writes: > >In article <11841@gatech.UUCP> klute@gatech.UUCP (Gregory Kenley) writes: >>A while back I remember reading an article in either PC or PC-Tech regarding >>modifying DOS on startup to skip the memory test. Al suggests a way to get around the problem, but says: >This will only work with DOS versions less than 2.0. In DOS 2.0 they added >a memory management scheme that allocates memory when >booted to correspond to the switch settings. Any attempt to allocate more >than the switch settings were set to will cause the memory allocate >algorithm to fail. It is still possible to chnage the amount of memory that DOS 2.0 thinks is available, but you must know about how DOS's memory management works. An article (no doubt the one Gregory was looking for) describing how DOS manages memory and providing the listing of an assembly program to solve the memory changing problem is in the August, 1984 issue of PC Tech Journal. It starts on page 43. -- Marc Lavine uucp: ...ihnp4!wlcrjs!marc MCI Mail: MLavine