Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!hplabs!hp-pcd!uoregon!smith From: smith@uoregon.UUCP (Dale Smith) Newsgroups: comp.sys.dec Subject: Re: Is anyone out there running Venix 1.0 on a Pro 350? Message-ID: <161@uoregon.UUCP> Date: Thu, 28-May-87 17:22:41 EDT Article-I.D.: uoregon.161 Posted: Thu May 28 17:22:41 1987 Date-Received: Sat, 30-May-87 09:54:51 EDT References: <725@sask.UUCP> <731@sask.UUCP> Reply-To: smith@drizzle.UUCP (Dale Smith) Distribution: world Organization: University of Oregon, Computer Science, Eugene OR Lines: 31 I am submitting this for a friend of mine who doesn't have news access. Please reply directly to him ( ..tektronix!uoregon!oregon2!uoneuro!brumbley or ...hp-pcd!uoregon!oregon2!uoneuro!brumbley). From: Subject: message for UNIX UUCP NEWS facility I have a memory management problem using Fortran 77 under RSX-11M on an LSI-11/73. I am using a memory-resident RMS library (taking up two APR's). Two of my overlays also use a virtual array (declared in the root segment and taking up another APR) and one of those overlays also uses a device common for data acquisition (using up another APR; 4KW of address space to access a dozen device registers!). That leaves four APR's (16KW) for the main task window. The Fortran support routines take about 10KW, leaving me 6KW for my code in a 256KW machine! I have squeezed the data acquisition routines into this space, but other overlays need more code space and don't need the device common; most don't need the virtual array either. The data acquisition overlay doesn't need the RMS routines. Can I use memory management executive calls to dynamically change the task window size and reassign APR's? How do I tell the Task Builder to use the same virtual address range (same APR) for the high 4KW of the task window and for the device common? Likewise, I want to use one APR for the second-highest 4KW of the task window and for the mapped array area (virtual array). I want the task to start up with the full task region size allocated, but mapped with the smaller task window, and the "shared" APR's set to the device common and mapped array area, respectively. Then I can save that mapping context and re-assign those APR's to extend the task window and back again as needed. Is there a way to do this? Or a way to swap between the RMS library region and the device common "region"? Any suggestions for other solutions would be greatly appreciated, as well.