Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!ames!elroy!mahendo!jplgodo!wlbr!pete From: pete@wlbr.UUCP Newsgroups: comp.sys.m6809 Subject: Re: RMA assembler usage Message-ID: <1152@wlbr.EATON.COM> Date: Mon, 7-Dec-87 13:32:24 EST Article-I.D.: wlbr.1152 Posted: Mon Dec 7 13:32:24 1987 Date-Received: Sat, 12-Dec-87 16:28:50 EST References: <131@abvax.UUCP> Reply-To: pete@wlbr.UUCP (0000-Pete Lyall) Organization: Eaton IMS, Westlake Village, CA Lines: 33 Keywords: RMA device descriptor In article <131@abvax.UUCP> harmon@abvax.UUCP (Larry Harmon) writes: > > I finally got a copy of the OS9 development system > > Another problem I encountered was the lack of an rbfdef.a file and >missing definitions in the os9defs.a file. Converting the level 1 rbfdefs >file to an rbfdefs.a file was simple. Plainly, they screwed up. What happened was that the RBF and SCF defs were left off of the Development disk. It's somewhat murky yet as to who dropped the ball (Tandy/Microware), but Microware has made good. They have posted versions in their new Forum on Compuserve (GO MSC). I will get copies of the SCF and RBFDEFS and post them here. I think that they are still in the old (not *.a) format, but as you discovered, that's no big deal. >How does one find the data area assigned to a device driver? >... Does a better method exist? > There are a couple of new system state debuggers out. One is called ERINA or SERINA. Believe that Jim Omura can expound on this product. It will allow you to do exactly what you're trying to do.. view system memory. The basic trick they use (I think) is to use a pseudo-device driver that acts sort of like a full system ramdisk. This way, any byte in the system can be read or written. Powerful, but dangerous. -- Pete Lyall (OS9 Users Group V.P.) Eaton Corporation (818)-706-5693 Compuserve: 76703,4230 (OS9 Sysop) OS9 (home): (805)-985-0632 (24hr./1200 baud) Usenet: {trwrb,scgvaxd,ihnp4,voder,vortex}!wlbr!pete or pete@wlbr.eaton.com