Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!ames!necntc!frog!rms From: rms@frog.UUCP Newsgroups: comp.sys.m6809 Subject: Re: OS9 load command Message-ID: <1941@frog.UUCP> Date: Wed, 18-Nov-87 15:43:00 EST Article-I.D.: frog.1941 Posted: Wed Nov 18 15:43:00 1987 Date-Received: Sat, 21-Nov-87 11:42:51 EST References: <1987Nov16.142303.4540@gpu.utcs.toronto.edu> Organization: Superfrog Heaven [ CRDS, Framingham MA ] Lines: 30 Summary: Error #207 on some load commands In article <1987Nov16.142303.4540@gpu.utcs.toronto.edu>, ac@gpu.utcs.toronto.edu (Mark Acfield) writes: > OS9 level II command also allows this syntax but if you specify to many > modules you will get a 207 error. > The OS9 Level II load command attempts to load all of the files specified on the line into the same page of memory. If all of the modules will not fit in a page, the error #207 results. Perhaps, the load command could be more clever and load into multiple pages when necessary. However, that may not be what the user had in mind. It may be necessary for certain modules to occupy the same page for various reasons. This feature of load has a good point. For instance, OS9 Level II has problems if you load a device driver and an associated device descriptor into separate pages of memory. However, if you load them into the same page of memory, the system will work fine (almost) up to a point. As far as I can figure, this works for device drivers once, and only a single driver/descriptor pair can be accessed in this way. This is fine for debugging a driver. With the current state of load, one should calculate the size of the text sections of the modules desired and use a separate load line for each group that has a total text size less than 8K. Your point about a multiple module set of commands is well taken. Maybe someone will come up with such a set of commands. Bob Santy