Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!sdcsvax!ucbvax!hplabs!pyramid!voder!wlbr!pete
From: pete@wlbr.EATON.COM (Pete Lyall)
Newsgroups: comp.sys.m6809
Subject: Re: OS9 Level II device drivers
Message-ID: <1127@wlbr.EATON.COM>
Date: Mon, 14-Sep-87 18:37:16 EDT
Article-I.D.: wlbr.1127
Posted: Mon Sep 14 18:37:16 1987
Date-Received: Wed, 16-Sep-87 02:34:45 EDT
References: <58@abvax.icd.ab.com>
Reply-To: pete@wlbr.UUCP (0000-Pete Lyall)
Organization: Eaton IMS, Westlake Village, CA
Lines: 30
Keywords: OS9 Level II device driver

In article <58@abvax.icd.ab.com> harmon@abvax.icd.ab.com (Larry Harmon) writes:
>
>	I am now using the same hardware with my CoCo 3 Level II system, but
>have been unable to use the old drivers.  When I try to load them I get a
>"System RAM full" error.  What does it all mean?  Do drivers need to be linked
>into the bootfile?  Should my driver be using the attach system call? What
>are the differences between level 1 and level II drivers?
>

What it all means is as follows:

a) System RAM full - question: have you modified the extended address
byte in the device descriptor from $FF to $07?? This is required on
the COCO III level II system.

b) re: loading device drivers & descriptors vice 'bootfiling' them..
you *should* do the latter, as each load of a driver (or other system
entity) will consume 8K of system RAM. Since there's only a total of
64K of system RAM, using it up in 8K increments can make it go
quickly. Don't forget that system RAM is also used for all buffers,
process descriptors, path descriptors, system data structures, etc.

c) Implicit attaches are done when the device(s) is/are initialized.


-- 
                                                   Pete Lyall

Usenet:     {trwrb, scgvaxd, ihnp4, voder, vortex}!wlbr!pete
Compuserve: 76703,4230 (OS9 Sysop) OS9 (home): (805)-985-0632 (24hr./1200 baud)