Short: Patch Os 3.9 BB2 RAM-Handler to show right size Author: thor@math.tu-berlin.de (Thomas Richter) Uploader: thor math tu-berlin de (Thomas Richter) Type: util/boot Version: 2.01 Requires: Os 3.9 BB2, Ram-Handler 44.23 Architecture: m68k-amigaos This file patches the RAM disk to show the real size occupied - its no longer 100% full. ____________________________________________________________________________ Changes made in 2.00: Completely new and different implementation for the Os 3.9 RAM-Handler, PatchRAM is now a permanent patch for RAM that comes in the form of a patch-file. Changes made in 2.00.2: Added a new release of LoadModule. Changes made in 2.00.3: Added a new release of LoadModule (again) Changes made in 2.01 Included a new release of LoadModule. Created a new patch for the BB2 RAM-Handler ____________________________________________________________________________ The THOR-Software Licence This License applies to the computer programs known as "PatchRAM". The "Program", below, refers to such program. The programs and files in this distribution are freely distributable under the restrictions stated below, but are also Copyright (c) Thomas Richter. Distribution of the Program by a commercial organization without written permission from the author to any third party is prohibited if any payment is made in connection with such distribution, whether directly (as in payment for a copy of the Program) or indirectly (as in payment for some service related to the Program, or payment for some product or service that includes a copy of the Program "without charge"; these are only examples, and not an exhaustive enumeration of prohibited activities). However, the following methods of distribution involving payment shall not in and of themselves be a violation of this restriction: (i) Posting the Program on a public access information storage and retrieval service for which a fee is received for retrieving information (such as an on-line service), provided that the fee is not content-dependent (i.e., the fee would be the same for retrieving the same volume of information consisting of random data). (ii) Distributing the Program on a CD-ROM, provided that the files containing the Program are reproduced entirely and verbatim on such CD-ROM, and provided further that all information on such CD-ROM be redistributable for non-commercial purposes without charge. Everything in this distribution must be kept together, in original and unmodified form. Limitations. THE PROGRAM IS PROVIDED TO YOU "AS IS," WITHOUT WARRANTY. THERE IS NO WARRANTY FOR THE PROGRAM, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. IF YOU DO NOT ACCEPT THIS LICENCE, YOU MUST DELETE ALL FILES CONTAINED IN THIS ARCHIVE. _____________________________________________________________________________ Installation: The installation of PatchRAM is a bit more trickier than it used to be because it is a permanent patch and replaces the code within the RAM handler directly. 0) Unpack the archive to wherever you want. Open a shell and change the current directory to where the archive was unpacket. 1) Extraction of the RAM-Handler: This step requires the Os 3.9 "AmigaOs ROM Update" file and the "ExtractModule" program in this distribution. Now enter on the command line: version "DEVS:AmigaOs ROM Update" 2) The output of this command should be "44.57" or the patch cannot be applied. 3) Enter the following command on the command line: ExtractModule from "Devs:AmigaOS ROM Update" module 17 to ram:Ram-Handler 4) This command will place the RAM-Handler within the ROM-Updates file to RAM:Ram-Handler. Now apply the patch to this file by entering the following command: spatch -oram:Ram-Handler.new -pRam-Handler.pch RAM:Ram-Handler 5) This command will generate the new RAM-Handler. Copy it now to "L:" by entering the following command: copy ram:Ram-Handler.new to L:Ram-Handler 6) You have now two alternatives how to make use of the new Ram-Handler. As it is no longer part of the ROM-Updates file, it has to enter the system in a different way. Alternative I) is to use the "LoadModule" command, alternative II) is to mount it manually. Alternative I): This will make the new RAM-Handler reset-resident in much the same way as SetPatch did. 7) Copy the LoadModule command from this archive to C: copy LoadModule to C: 8) Edit the startup-sequence with an editor of your choice. In the following, let's assume the default system editor, "Ed": Ed S:Startup-Sequence 9) Locate the "SetPatch" command within the startup-sequence, place the cursor on the "S" of "SetPatch" and press . This will insert a new blank line ON TOP of SetPatch. Move the cursor upwards into this blank line and enter the following command: LoadModule L:Ram-Handler NOREBOOT 10) You may also load additional modules here, i.e. the Os 3.9 icon.library or the Os 3.9 workbench.library. Just give their full paths as arguments to the LoadModule command. *NOTE THAT IT IS IMPORTANT THAT LOADMODULE IS RUN BEFORE SETPATCH*. With these modifications, the command line could look like this: LoadModule L:Ram-Handler LIBS:icon.library LIBS:workbench.library NOREBOOT The advantage of "LoadModule" is that the ROM modules loaded by this command can be protected from getting overwritten by means of the "MuProtectModules" program of the same author (not included in this archive). 11) Locate the "SetPatch" command within the startup-sequence. Move the cursor behind "SetPatch", and add the command line option "SKIPROMMODULES ram-handler" to the command. The setpatch command line should then read approximately as follows: SetPatch SKIPROMMODULES ram-handler >NIL: If you already have to skip parts of the update, as for example the scsi.device, the line should rather look like this: SetPatch SKIPROMMODULES scsi.device,ram-handler >NIL: 12) Save the changes of the startup-sequence back. For "Ed", press first , then , then . 13) To make the changes active, a reboot is *NOT* enough. You should turn off the machine, wait for half a minute, and reboot. This will flush the RAM resident parts of the ROM-Updates mechanism. Alternative II): Mounting the RAM-Handler by hand in a non-reset-resident way. 7) Copy the the files "RAM" and "RAM.info" to DEVS:DosDrivers: copy RAM RAM.info to DEVS:DosDrivers 8) Edit the Startup-Sequence with an editor of your choice. For the following, let's assume you use the system editor "Ed": ed S:Startup-Sequence 9) Locate the "SetPatch" command within the startup-sequence. Move the cursor behind "SetPatch", and add the command line option "SKIPROMMODULES ram-handler" to the command. The setpatch command line should then read approximately as follows: SetPatch SKIPROMMODULES ram-handler >NIL: If you already have to skip parts of the update, as for example the scsi.device, the line should rather look like this: SetPatch SKIPROMMODULES scsi.device,ram-handler >NIL: 10) Press and insert the following commands *BELOW* SetPatch, one in a line; note that it is important that these commands are run *AFTER* SetPatch (different from alternative I): Assign RAM: DisMount Assign ENV: ENVARC: Mount DEVS:DosDrivers/RAM Assign ENV: Remove 11) To save the changes back when using "Ed", press , then , then . This step depends on the editor you use, though. _____________________________________________________________________________ For more information concerning "LoadModule", check "LoadModule.lha" on Aminet. _____________________________________________________________________________ April 2002, Thomas