From cnmelber@cip.informatik.uni-erlangen.de Tue Jun  1 04:08:46 1993
Received: from faui45.informatik.uni-erlangen.de ([131.188.34.45]) by toadflax.cs.ucdavis.edu (4.1/UCD.CS.2.3)
	id AA19376; Tue, 1 Jun 93 04:08:37 PDT
Received: from faui01.informatik.uni-erlangen.de by uni-erlangen.de with SMTP;
	id AA28056 (5.65c-5/7.3t-FAU); Tue, 1 Jun 1993 13:08:28 +0200
Received: from faui00c.informatik.uni-erlangen.de by cip.informatik.uni-erlangen.de with SMTP;
	id AA07365 (5.65c-5/7.3m-FAU); Tue, 1 Jun 1993 13:08:26 +0200
From: "Carsten Melberg (CIP 91)" <cnmelber@cip.informatik.uni-erlangen.de>
Message-Id: <199306011108.AA07365@faui01.informatik.uni-erlangen.de>
Subject: MemBlocker Version 1.1
To: announce@cs.ucdavis.edu
Date: Tue, 1 Jun 1993 13:08:21 +0200 (MET DST)
X-Mailer: ELM [version 2.4 PL21]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 2403      
Status: R


NAME
  MemBlocker Version 1.1

INTRODUCTION
  MemBlocker blocks memory. You are able to allocate memory blocks of a
  specified size and release them later. This may be done from Workbench or
  CLI, Kick 37.175 (OS2.04) or greater is needed anyway.

WHY BLOCK MEMORY?
  Blocking memory is usefull for all those with different types of FAST-RAM,
  this is 32-bit and 16-bit ram. Many owners of accelerator cards and some
  other expansion memory have both of these types in their system. When you
  boot your system, the software or hardware of the accelerator assign the
  32-bit ram to the highest memory-priority. So nearly all of this 'fastest'
  ram is used before the 16-bit ram is touched. When there is no more 32-bit
  ram left you suddenly see a significant slowdown after starting a program in
  16-bit ram. So one would like to save as much as possible of the 32-bit ram
  for those programs that need 'fastest' memory.
  One the other hand, there are many programs that don't need 'fastest' ram.
  Comodities, other utilities, diskcaches, buffers and more. Many of these are
  started in the startup-sequence, user-startup or wbstartup-drawer. This is
  where MemBlocker comes in: You block your precious 'fastest' 32-bit ram
  before launching those applications and release it afterwards. So the
  applications are forced to use the slower 16-bit ram.
  But be careful what programs you force into slower ram: devices, handlers,
  simply everything where speed is needed should get 'fastest' ram.
  Another usage might be to shrink your availible memory for test purposes.

DISTRIBUTION
 MemBlocker may be freely distributed, as long as no charge is made other
 than to cover time and copying costs. The package must be distributed as
 the original archive. If you want to include MemBlocker as part of a 
 commercial package, contact the author listed below. Fred Fish is 
 specifically given permission to include MemBlocker in his fine disk 
 library. It is also allowed to put MemBlocker on free accessible BBS's
 or Internet sites.

AUTHOR
  Carsten Melberg
  Karlsbader Str. 3
  D-8520 Erlangen    (D-91058 Erlangen from 1. July '93)
  Germany

  cnmelber@cip.informatik.uni-erlangen.de

HISTORY
 Version 1.00-1.02 internal releases
 Version 1.1 first public release


WHERE TO FIND
  on everey aminet site

    e.g. amiga.physik.unizh.ch

      pub/aminet/util/misc/memblocker.lha