Short: Restores Workbench 3.1 protection bits Author: deadbeat73@hotmail.com (Timo Rönkkö) Uploader: deadbeat73 hotmail com (Timo Rönkkö) Type: util/boot Requires: Backup copy of Workbench 3.1 disks Architecture: m68k-amigaos Okay, the story is age old, and you've probably heard it before. Somebody screwed up, and the correct protection bits aren't present on the Workbench 3.1 distribution. Most trouble is probably caused by the lack of pure-bits. There exists a previous effort, but it's only good for restoring pure-bits. This little AmigaDOS-script restores not only the pure-bits, but sets ALL the protection bits the way they should be! BEFORE GETTING STARTED, REMEMBER THIS: ALWAYS WORK ON BACKUP COPIES, NEVER ON YOUR ORIGINAL WORKBENCH DISKS! Got the backup copies ready? Good. You may go to a shell prompt now and type "execute FixWB31.bat". You'll be requested to insert the following disks, in this order (and by these volume-names): Workbench3.1: Extras3.1: Fonts3.1: Install3.1: Locale3.1: Storage3.1: Both the FONTS and LOCALE disks will be requested by a different name, in order to prevent unwanted changes to your hard drive's contents. If you're using a multi-function commodity such as MultiCX with the ASSIGNWEDGE feature (MCP and MagicCX should have it too), you can use it to assign Fonts3.1: and Locale3.1: to df0: (or whatever drive you are using) when requested. Otherwise, you'll have to use Workbench's "Execute Command..." function (or alternatively, another shell) to assign manually, when requested, like this: Execute a File====================================|#= | | | Enter Command and its Arguments: | | ------------------------------------------| |Command: | assign Fonts3.1: df0: || | ------------------------------------------| |------ --------| || Ok | |Cancel|| ----------------------------------------------------- Advanced users, who don't wish to re-install Workbench, may easily modify the script to do changes on their system partition instead of Workbench disks simply by using search & replace. Even though many things can't go wrong in a simple AmigaDOS- script, standard disclaimer applies: it's your own risk, and the author of the script (and this readme) can't be held liable for anything.