@DATABASE "BootX.guide" @AUTHOR "Peter Stuer" @WORDWRAP @FONT topaz.font 8 ## $VER: BootX.guide v1.11 (23.12.92) @WIDTH 80 @HEIGHT 255 @NODE Main "BootX Help" Welcome to the BootX AmigaGuide®. Select any of the following topics and follow the links to other subjects as you please: @{" 1 " LINK About} About BootX @{" 2 " LINK Requirements} System requirements @{" 3 " LINK Author} About the author and the program @{" 4 " LINK Updates} Getting updates @{" 5 " LINK Language} Using BootX in a different language @{" 6 " LINK Complaints} Before you complain... @{" 7 " LINK Acknowledge} Acknowledgments @{" 8 " LINK Gadgets} Gadgets @{" 9 " LINK Menus} Menus @{" 10 " LINK Hints} Hints, tips and tricks @{" 11 " LINK SHI} About Safe Hex International @{" 12 " LINK Addresses} Addresses @{" 13 " LINK Glossary} Glossary @{" 14 " LINK Index} Index @ENDNODE @NODE Help "About AmigaGuide" The Contents gadget will take you back to the last help menu you visited. Click Retrace to go back to the help screen you came from. Browse forward and backward enable you to walk through the help document. @ENDNODE @NODE Gadgets "Gadgets" @TOC Main This page provides you with help about all the @{"gadgets" LINK GlossaryG} that can be found on the BootX screen. @{" 1 " LINK Quit} Quit @{" 2 " LINK ReadBB} Read Bootblock @{" 3 " LINK WriteBB} Write Bootblock @{" 4 " LINK DriveGadgets} The drives cycle gadget @{" 5 " LINK LockDrive} Lock Drive @{" 6 " LINK CheckFilesGad} Check Files @{" 7 " LINK ShowInstallBB} Show installable bootblock @{" 8 " LINK BuiltInName} Built-in bootblock name @{" 9 " LINK Install} Install @ENDNODE @NODE Menus "Menus" @TOC Main Here are all the @{"menus" LINK GlossaryM} BootX provides. @{" 1 " LINK Project} Project @{" 2 " LINK Check} Check @{" 3 " LINK Bootblocks} Bootblocks @{" 4 " LINK ToolBox} ToolBox @{" 5 " LINK BBLib} BBLib @{" 6 " LINK Brain} Brain @{" 7 " LINK Preferences} Preferences @ENDNODE @NODE Project "The Project Menu" @TOC Menus The Project Menu provides access to some of the basic actions during a BootX session. @{" 1 " LINK LoadRecog} Load Recog file @{" 2 " LINK ShowKnown} Show known @{" 3 " LINK PrintKnown} Print known @{" 4 " LINK Iconify} Iconify @{" 5 " LINK BootXHelp} Help @{" 6 " LINK About} About @{" 7 " LINK Quit} Quit @ENDNODE @NODE Check "The Check Menu" @TOC Menus The Check menu concentrates all the possible checks that BootX has to offer. @{" 1 " LINK CheckBlocks} Check blocks @{" 2 " LINK CheckMemory} Check memory @{" 3 " LINK CheckVectors} Check vectors @{" 4 " LINK ResetVectors} Reset vectors @{" 5 " LINK CheckFiles} Check files @{" 6 " LINK ShowReport} Show report @{" 7 " LINK SaveReport} Save report @{" 8 " LINK PrintReport} Print report @{" 9 " LINK CheckDisk} Check disk @ENDNODE @NODE ToolBox "The ToolBox Menu" @TOC Menus In this menu you will find some utilities that might come in handy during your work. @{" 1 " LINK FilterUtility} Filter @ENDNODE @NODE FilterUtility "Filter Utility" @TOC ToolBox The Filter utility allows you to create a filter of path names which BootX will ignore during a file check. The paths that are part of a filter typically contain only data files like documents, modules, IFF drawings, include files or other binary files. Programmers might want to put their Include and Fd directories in the filter. The Fonts directory is another good candidate. Make sure you have checked the Filter checkbox in the Check Files preference requester or the Filter will not be used during a file check. Don't forget to save your preferences after you have created or modified a filter. BootX stores the names of the paths to be filtered in the BootX.prefs file. NOTE The filter can be a mixed blessing. It will speed up file checks since entire directories will be skipped. However if you add a path to the filter that contains executables and one of the executables is infected by a virus it will not be found. Be carefull. @{" 1 " LINK FilterNew} New @{" 2 " LINK FilterAdd} Add @{" 3 " LINK FilterEdit} Edit @{" 4 " LINK FilterRemove} Remove @{" 5 " LINK FilterOK} OK @ENDNODE @NODE FilterNew "The Filter Utility New gadget" @TOC FilterUtility Click this gadget to start a new filter. @ENDNODE @NODE FilterAdd "The Filter Utility Add gadget" @TOC FilterUtility When you click on the Add gadget BootX will present you with a directory requester. Walk through your directory tree until you are in the directory you wish to filter. Select OK when done. The newly selected path will show up in the Filter listview. If you have selected an entry from the Filter listview it will be used as starting point of your tree travels. @ENDNODE @NODE FilterEdit "The Filter Utility Edit gadget" @TOC FilterUtility This gadget can only be selected when you have clicked on one of the Filter listview entries. BootX will present you with a directory requester with the selected entry as starting point of your tree walk. This allows you to edit existing path filters. @ENDNODE @NODE FilterRemove "The Filter Utility Remove gadget" @TOC FilterUtility After you have selected an entry from the Filter listview, the Remove gadget will become enabled. Click on it to remove the current selected filter entry. @ENDNODE @NODE FilterOK "The Filter Utility OK gadget" @TOC FilterUtility Select the OK gadget to finish editing the path filter. @ENDNODE @NODE Bootblocks "The Bootblocks Menu" @TOC Menus Select one of the following subjects concerning the Bootblocks menu: @{" 1 " LINK LoadSave} Load/Save @{" 2 " LINK Learn} Learn @{" 3 " LINK ShowAgain} Show again @ENDNODE @NODE BBLib "The BBLib Menu" @TOC Menus When BootX is started it will look for a ${"file" LINK GlossaryF} called @{"BootX.BBLib" LINK GlossaryB}. This @{"Bootblock library" LINK GlossaryB} contains custom @{"bootblocks" LINK GlossaryB} that you can use instead of the standard @{"OldFileSystem" LINK GlossaryO} or @{"FastFileSystem" LINK GlossaryF} bootblocks. With the Bootblock library system you can create several different libraries that contain your collection games, demo or utility bootblocks. The libraries are much easier to maintain than several single files. If one of your autobooting game or demo @{"disks" LINK GlossaryD} get infected by a @{"bootvirus" LINK GlossaryB}, you can always use the copy you saved in your library to restore the disk. You can install any bootblock in the library by selecting it using the 'Show installable bootblock' gadget and then @{"clicking" LINK GlossaryC} on the 'Install' gadget. @{" 1 " LINK BBLibNew} New @{" 2 " LINK BBLibLoad} Load @{" 3 " LINK BBLibSave} Save @{" 4 " LINK BBLibShow} Show @{" 5 " LINK BBLibMerge} Merge @{" 6 " LINK BBLibAdd} Add bootblock @{" 7 " LINK BBLibDelete} Delete bootblock @{" 8 " LINK BBLibRename} Rename bootblock @ENDNODE @NODE Brain "The Brain Menu" @TOC Menus At startup time BootX looks for a file called @{"BootX.Brain" LINK GlossaryB}. This Brainfile contains all the bootblocks you have taught BootX using the Bootblock/Learn @{"menu item" LINK GlossaryM}. This Brainfile complements the knowledge base of BootX by letting BootX recognize any new bootblock that are not yet recognized by the @{"BootX.Recog" LINK GlossaryR} file. NOTE If you find new bootblocks that BootX does not yet recognize please send them to me so that I can update the Recog file. BootX will always give precedence to the conclusion of the Recog file when it tries to recognize a bootblock. @{" 1 " LINK BrainNew} New @{" 2 " LINK BrainLoad} Load @{" 3 " LINK BrainSave} Save @{" 4 " LINK BrainShow} Show @{" 5 " LINK BrainMerge} Merge @{" 6 " LINK BrainDelete} Delete Brain cell @{" 7 " LINK BrainRename} Rename Brain cell @ENDNODE @NODE Preferences "The Preferences Menu" @TOC Menus Want to change your preferences ? Look here for help: @{" 1 " LINK PrefEdit} Edit @{" 2 " LINK PrefLoadSave} Load @{" 3 " LINK PrefLoadSave} Save @ENDNODE @NODE Hints "Hints, tips and tricks" @TOC Main Here are some hints and tips on how to use BootX... @{" 1 " LINK HowToKill} How to kill disk-validator viruses @{" 2 " LINK LowMemory} Using BootX with little memory @{" 3 " LINK BBCopy} Copying bootblocks with one drive @ENDNODE @NODE About "About BootX" @TOC Main BootX is a powerful viruskiller for the Commodore-Amiga computer. It is fast (written completely in @{"assembler" LINK GlossaryA}) and tries to be as user friendly as possible. This program is freeware, this means that you can copy it freely as long as you don't ask any more money for it than a nominal fee for copying. If you want to distribute this program you should keep this document with it. This program cannot be used for commercial purposes without written permission from the author. Special permission is hereby granted to include BootX in Public-Domain collections such as Fred Fish's Amiga Library. BootX software and documentation are © 1989, 1990, 1991, 1992 by Peter Stuer. All rights reserved. @ENDNODE @NODE Requirements "System requirements" @TOC Main BootX should run on any Amiga system with at least @{"512K" LINK GlossaryK} @{"RAM" LINK GlossaryR} and one disk drive. BootX requires @{"KickStart" LINK GlossaryK} v2.04 or higher to run. If BootX is run with @{"Workbench" LINK GlossaryW} v2.1 or higher it will use the @{"locale.library" LINK GlossaryL} to become language independent. Special care has been taken in the program design to make the program work with 68020, 68030 and 68040 @{"processors", LINK GlossaryP} without sacrificing 68000 compatibility. Should you have any trouble running BootX on your machine, please write to me with the full specifications of your machine, that is KickStart version, model, expansion boards etc... BootX also requires the @{"ReqTools.library" LINK GlossaryR} v38 or higher. ReqTools is copyrighted 1992 by Nico François. If you want to save and load files that have been @{"crunched" LINK GlossaryC} with PowerPacker you will also need the @{"PowerPacker.library" LINK GlossaryP} v35 or higher. PowerPacker is copyrighted 1992 by Nico François. To decrunch Library Imploded files during a file check you'll need the Explode.library v6.0 or higher. To use the help feature BootX requires the AmigaGuide.library to display the BootX.guide. This library comes with WorkBench 3.0. @ENDNODE @NODE Author "About the author and the program" @TOC Main Since so many people keep asking me about it... I graduated in June 1991 as a programmer-analyst. BootX was created because at the time (April 1989) I did not trust the available viruskillers. In those days only the SCA and the Byte Bandit @{"bootviruses" LINK GlossaryB} where a threat to our @{"bootblocks" LINK GlossaryB}. If you have suggestions or remarks about this program, or if you find any @{"bugs" LINK GlossaryB}, please let me know. If you find any new viruses or @{"linkviruses" LINK GlossaryL} that BootX does not recognize yet, please send them on a disk to me (@{"my address" LINK Addresses} follows this paragraph). I will return the disk to you with an updated copy of BootX. When sending in @{"bug" LINK GlossaryB} reports, please state exactly under what circumstances the bug occurred, what equipment was used and what happened. If possible also try to give me enough information to reproduce the bug. It is very difficult to find bugs when you don't know exactly what happened. Write to the following address: Peter Stuer Kauwlei 21 B-2550 Kontich Belgium - Europe Fido: 2:292/603.7 @ENDNODE @NODE Updates "Getting updates" @TOC Main If you send me a 3½" disk and a letter to get the most recent version of BootX, please don't forget to include enough stamps or money to send your disk back. BootX has been generating a lot of mail and most of the times I had to pay the postal fee myself to send the disk back. Remember, BootX itself is a FREEWARE so no money is expected for it (although I won't refuse it, grin...). Every letter with a disk AND money will be answered AS SOON AS POSSIBLE... And please, state your name and address clearly in print because sometimes they are nearly impossible to decipher. I will also try to put the latest available version of BootX on the following BBS (this may change without further notice): Great Balls Of Fire BBS Herman Stevens Lubbeek ADS Regional Coordinator Belgium Tel. +32-(0)16-64.09.12 14400 BPS (N.8.1) v32bis v42bis 24-24 h. Fido Node 2:292/603 NOTE As of version 1.74 of the Recog file and BootX 5.23 a requester will appear when BootX thinks itself is older than 90 days or when the Recog file you are using is older than 60 days. This requester is just to warn you that it may be time to upgrade to a newer version. @ENDNODE @NODE Complaints "Before you complain..." @TOC Main I just want to mention a couple of things here that will only show up if you're snooping around in the system when BootX is running. Some of you seem to be running the Commodore development tool Enforcer all the time. I have gotten some letters about the Enforcer hits BootX causes. The only way I can check your memory and vectors is to do some low memory reads. These will typically show up as an Enforcer READ hit to addresses in the region 0x64 to 0x74. This is normal. You can expect this to happen at various points during program execution and particularly during a vector check. Enforcer WRITE hits are not normal. Please report these ! NOTE If you haven't the faintest idea what I am talking about, don't worry. I should only concern those people who know what Enforcer does and how to use it. BootX also launches a task called 'SnoopDos'. This is done to prevent some old PowerPacker trojan horse to install itself in memory. This task uses no CPU time. It is removed when BootX quits running. Also, this task will only be launched when there isn't yet a task called 'SnoopDos' in the system. This ghost task won't prevent the real SnoopDos (by Eddy Carroll, Freely distributable) from being run or functioning correct. @ENDNODE @NODE Acknowledge "Acknowledgments" @TOC Main · Nico François - For his ReqTools and PowerPacker packages. Also for answering my questions on programming in the new KickStart v2.04 environment and for ßeta testing BootX. · BootX ßeta testers - In no particular order: Nico François (Belgium) Johan Van Houtven (Belgium) Bart Beeckmans (Belgium) Steffen Salzmann (BRD) James Knittle (USA) Erik Løvendahl Sørensen (Denmark) · Lieven Lema (Belgium) - For his translation into French of the BootX locale file. · Patrick Nordvall (Sweden) - For his translation into Swedish of the BootX locale file. · Steffen Salzmann (BRD) - For his translation into German of the BootX locale file. · Mikkel Bille Stegmann (Denmark) - For his translation into Danish of the BootX locale file. · Michele Giorato (Italy) - For his translation into Italian of the BootX locale file. · Tor W. Austerslått (Norway) - For his translation into Norwegian of the BootX locale file. · 'Big A' (my A3000) for assembling BootX fast and safe. BootX has been created using the Macro68 Assembler, WShell 2.0 and CygnusEd Professional on an Amiga A3000 25/100 with 6MB memory. The BootX documentation was formatted with my Roff clone ARoff. The @{"assembler" LINK GlossaryA} source code occupies more than 742.400 bytes and consists of more than 34.500 lines. @ENDNODE @NODE Quit "Quit" @TOC Gadgets When you @{"click" LINK GlossaryC} on the first @{"gadget" LINK GlossaryG} on the left side of the screen, BootX quits running. Before BootX quits it will check to see if you have made any changes to the @{"BBLib file" LINK GlossaryB} or to the @{"Brain file" LINK GlossaryB}. If so, it will ask you first if you want to save the changes you have made. NOTE Watch out that you don't leave any infected disks in your drives when you quit BootX ! Especially disks that are infected with @{"disk-validator" LINK GlossaryD} viruses. @ENDNODE @NODE ReadBB "Read Bootblock" @TOC Gadgets This gadget explicitly instructs BootX to read the @{"bootblock" LINK GlossaryB} from the current selected drive into the buffer. Normally BootX detects when a new disk is inserted and automatically reads its bootblock. But some old 5¼ drives don't support this automatic diskchange. This gadget can also be used to read the bootblock after another program has modified the bootblock. You will also need to use this gadget when you have turned of the auto-diskchange detection or when you have locked a drive (see @{"Lock Drive" LINK LockDrive}. When BootX detects a virus in the bootblock it just read, a requester will be brought up asking you if you would like to kill the virus. If you answer positively by clicking on the Yes gadget, BootX will try to @{"install" LINK Install} the bootblock current selected from the Bootblock library. @ENDNODE @NODE WriteBB "Write Bootblock" @TOC Gadgets Here you instruct BootX to write the bootblock currently in the buffer to the selected drive. BootX maintains a buffer that holds the last read bootblock. This buffer is also visible in the large display window in @{"semi-ASCII" LINK GlossaryA} form (more about this later). The buffer allows you to read a bootblock from one disk and then copy it to another. @ENDNODE @NODE DriveGadgets "The drive cycle gadget" @TOC Gadgets You can connect up to 4 disk drives to the Amiga. BootX checks how many drives are connected to the Amiga and installs their @{"device" LINK GlossaryD} names in the list of this @{"cycle gadget" LINK GlossaryC}. Only the drives that are connected to the Amiga and are turned on (in case of external drives) will be reported by this gadget. To select a particular drive keep clicking on the gadget until its device name is shown. @ENDNODE @NODE LockDrive "Lock Drive" @TOC Gadgets Normally when you insert a disk in the disk-drive, the Amiga tries to see if the checksum of the disk is OK. When it is not, the Amiga tries to validate it. Pre-2.0 KickStarts needed to load and execute a program called Disk-Validator from the L @{"directory" LINK GlossaryD} to check and/or repair the checksum. When a disk-drive is 'locked', BootX will prevent @{"AmigaDOS" LINK GlossaryA} from validating your disk. This also means that Disk-Validator viruses have no chance of getting in. You can insert and remove disks as many times as you like. Also the automatic diskchange detect will be temporarily disabled. @ENDNODE @NODE CheckFilesGad "Check Files" @TOC Gadgets This gadget is a short-cut for the @{"Check files" LINK CheckFiles} menu item. @ENDNODE @NODE ShowInstallBB "Show installable bootblocks" @TOC Gadgets When you click on this gadget, BootX will display the contents of the current loaded @{"bootblock library" LINK GlossaryB}. You simply click on the name of the bootblock to select it as current bootblock. Either @{"double-click" LINK GlossaryD} on the name or click and select OK. This action only selects the bootblock ! It is not immediately written to the current disk nor is it put in the bootblock buffer. You can see the name of the current selected bootblock in the small window next to the gadget. If you do not want to make a change select the Cancel gadget of the @{"requester" LINK GlossaryR}. NOTE BootX already knows 2 bootblocks even when no bootblock library has been loaded. They are the standard AmigaDOS 2.0 bootblocks for @{"OldFileSystem" LINK GlossaryO} and @{"FastFileSystem" LINK GlossaryF} disks. Their names have a little dot completely to the right. @ENDNODE @NODE BuiltInName "Built-in bootblock name" @TOC Gadgets This window shows the name of the selected @{"bootblock" LINK GlossaryB}. @ENDNODE @NODE Install "Install" @TOC Gadgets Here you can write the selected bootblock to the bootsectors of the disk in the current drive. At startup BootX looks for a file called "BootX.BBLib" in the directory from which BootX started. It contains several alternative bootblocks. It is possible to load another bootblock library using the @{"Load" LINK BBLibLoad} menu item of the "BBLib" menu. @ENDNODE @NODE LoadRecog "Load Recog file" @TOC Project As of BootX v4.30 all the recognition information BootX needs to identify a virus or a bootblock is contained in a file called BootX.Recog. With this menu item you can load different BootX.Recog files than the one BootX loads at started called "BootX.Recog". NOTE The BootX.Recog files are coded and protected by a checksum to prevent anyone from modifying the information it contains with a file editor. Always try to get the latest version of the BootX.Recog file to get maximum protection. You can find out the version of a BootX.Recog file in several ways: 1. After BootX has successfully loaded a Recog file it will display the version and the release date of the file. 2. The BootX version and the Recog file version are always shown in the title bar of the screen. 3. Select the About menu item. The text will show the version and the release date of the Recog file and how many bootblocks, bootviruses and fileviruses it knows. NOTE These numbers may vary from the number reported by the "Show known xxx" menu items. The numbers reported here are the number of recog blocks that BootX can use to identify a virus. The "Show known xxx" menu items only report all the different names that BootX uses, f.e. BootX can recognize several different mutants of the same virus but the name will only show up once in the "Show known bootviruses" list. 3. Use the @{"AmigaDOS" LINK GlossaryA} v2.x version command: 1> version BootX.Recog @ENDNODE @NODE ShowKnown "Show known" @TOC Project This submenu allows you to view the contents of the current loaded Recog file. Use the submenu items Bootblocks, Bootviruses or Fileviruses to view the list you want. BootX will then pop up a list requester. Use the scroll gadgets or the scroll bar to move through the list. The window title of the requester will tell you how many entries are being shown. NOTE The selection 'Show known fileviruses' also shows the linkviruses and trojan horses that BootX knows. Click on the window's @{"close gadget" LINK GlossaryC} to remove the requester. @ENDNODE @NODE PrintKnown "Print known" @TOC Project Here you can request BootX to print the contents of the current loaded Recog file to your printer. NOTE If you have to wait a long time (about 10 seconds) and nothing happens, please check that your printer is turned on and if so that it is on-line. BootX will not be able to report an error until the @{"default" LINK GlossaryD} time-out period is passed (usually 30 seconds) or until the user put the printer on-line. @ENDNODE @NODE Iconify "Iconify" @TOC Project Selecting Iconify causes BootX to close its screen and release as much memory as possible. BootX will then try to find its @{"icon" LINK GlossaryI} in the @{"drawer" LINK GlossaryD} from which it started and use it to create an @{"AppIcon" LINK GlossaryA} on the Workbench. For more information about AppIcons I refer to the Amiga User Interface Style Guide. There are two ways to wake up BootX. You press the BootX hot key combination (default Ctrl Left-Alt B) or you wake BootX up via its AppIcon. The hot key combination can be changed via the menu item @{"Preferences/Edit" LINK PrefEdit}. When iconified BootX waits for two kinds of events. If you double-click on the icon BootX reopens its screen and returns to the state as it was before you iconified it with all the information and preferences intact. Another way to wake up BootX is to select or shift-select one or more disk or drawer icons and drop them on the BootX AppIcon. BootX will then wake up and present its @{"Check Files" LINK CheckFiles} Preference requester. Set your preferences and when you click on the Check Files gadget BootX will present you with the @{"path" LINK GlossaryP} requester. BootX will have inserted the @{"volume name" LINK GlossaryV} or the drawer name in the string gadget. You only have to click on OK or press return to start the file check with that path. If you drop a file icon on the AppIcon BootX will use that path of that file as its starting point for the file check. This way you can drop the icons you have 'left out' using the Leave Out menu item of the Workbench Icon menu on the BootX AppIcon. At present BootX uses no @{"CPU" LINK GlossaryC} time at all when it is in its iconified state. No checking of memory or of newly inserted disks is done. There is no need to continuously keep checking every disk that is inserted. Just check them once to make sure they are virus-free. NOTE If BootX can't find its icon it will use the default tool icon instead. You can create your own default tool icon using the Workbench 2.0 Icon Editor and save it using the 'Save As Default Icon' menu item. AppIcons are always positioned dynamically on the Workbench screen, that is, whereever there is room. You can not snapshot an AppIcon in a fixed place. @ENDNODE @NODE BootXHelp "Help" @TOC Project As of BootX v5.00, the AmigaGuide library is used to implement the help system. At the time of writing this library has only been distributed by Commodore to registered developers. In the mean time I might write a simply emulation for those users who do not have AmigaGuide yet. @ENDNODE @NODE About "About" @TOC Project Here you can find out some details about BootX, among them the version number, the Recog file version, the author of the language translation and my address. Always try to get the latest version available to have optimum virus protection. @ENDNODE @NODE Quit "Quit" @TOC Project Guess what this one does... @ENDNODE @NODE CheckBlocks "Check blocks" @TOC Check Some of the current viruses and possibly some to come alter or damage the blocks on the surface of your disks. When you ask BootX to check the blocks of the current drive it will scan the complete surface of the disk that is currently in the drive, looking for damaged or infected blocks. When BootX encounters an infected block it will tell you together with the name of the virus that infected that block. Most of the time the information that was in an infected block is lost but in some cases the block can be repaired and the information restored. Currently BootX can repair blocks that are infected by the Saddam disk-validator virus and by the Curse Of Little Sven virus. It will tell you when it finds blocks infected by the Lamer Exterminator virus. To use the block check simply select the menu item. Make sure there is no disk in the current drive. BootX will then lock the drive and ask you to insert the disk you wish to check. During the scan you'll get a progress report. You can leave your disk write-protected. BootX will then issue a warning and it will scan the disk without making any modifications. NOTE Be sure you insert your disk only after BootX asks for it. This is necessary security and to make sure BootX has a chance to recognize if your disk is a 880K or 1760K high-density disk. @ENDNODE @NODE CheckMemory "Check memory" @TOC Check BootX checks the memory at strategic times during its actions. With this memory action you can force BootX to recheck the memory. When it finds a virus you will be alert with an Amiga DisplayAlert and BootX will try to kill the virus in memory. It is possible that the Amiga crashes after BootX has found a virus. BootX will try to restore any changed information but sometimes this is not possible. Therefore the safest solution has been chosen of completely clearing the virus memory. @ENDNODE @NODE CheckVectors "Check vectors" @TOC Check The flexibility of the Amiga operating system lies in the fact the programmers have so many options of altering the way the Amiga does specific things. Regrettably virus programmers also know this and use various @{"vectors" LINK GlossaryV}, as the entry points are called, to add the virus code to the operating system. BootX can identify and kill virus if it knows it. But new viruses are being programmed every day. The vector check scans all the places in the Amiga memory that are the most likely candidates for virus attacks. During this scan it generate a vector check report. In this report is a lot of technical information. After the scan BootX displays the report in the main window. You can skip through the pages using the left mouse button. The right mouse button aborts at any time. At the end of the report BootX shows some information about your system. If you need more accurate information use one of the many dedicated tools. When BootX finds a vector which points to abnormal address it will try to identify the program that changed that vector. A lot of programs 'patch' the operating system to fix bugs or to add features. Commodore itself fixes small bugs this way using the SetPatch command. I will try to keep BootX's knowledge base as up to date as possible. A normal vector will be displayed in black with the message 'OK' next to it or the name of the program that changed that vector. If BootX can not decide what code uses the vector it will display the message 'Please check' in white next to the vector. This does not necessarily mean that the vector is used by a virus. Don't panic and contact a more experienced Amiga user (preferably a programmer). In case of doubt, save all your data and @{"cold start" LINK GlossaryC} the Amiga, that is, turn of the power and wait a few seconds before turning it on again. @ENDNODE @NODE ResetVectors "Reset vectors" @TOC Check Here you are given to option to clear the first five vectors that BootX shows in its vector check report. These vectors are used to have foreign code survive a software reset (using the Ctrl - Left Amiga - Right Amiga key combination). This is not a fail safe way to kill a virus. Also if any other software is using these vectors, it will not survive the next reset. Also, some virus defend themselves against such action and will not allow BootX to reset those vectors. @ENDNODE @NODE CheckFiles "Check files" @TOC Check BootX was written in the days that bootviruses were the greatest if not only treat to the Amiga, hence the name BootX. Over the years this has changed. The biggest danger now comes from file and linkviruses. This menu option provides you with the most powerful tool in the Amiga world to fight and kill those viruses. After you select the Check files menu item or click on the Check files gadget BootX will present you with a Check Files Preferences requester. BootX gives you a lot of options to customize your file checks. To remove the requester without checking your files click on the window close gadget or the Cancel gadget. @{" 1 " LINK VirusHandling} Virus handling @{" 2 " LINK RemoveLinkviruses} Remove linkviruses @{" 3 " LINK AutoHandle} Handle viruses automatically @{" 4 " LINK ShowDirs} Show directories/files/checked files @{" 5 " LINK CheckCrunched} Check crunched executables @{" 6 " LINK SkipProtected} Skip read-protected @{" 7 " LINK AutoRemove} Auto-remove read-protection @{" 8 " LINK GenerateReport} Generate report @{" 9 " LINK SilentCheck} Silent check @{" 10 " LINK Filter} Filter @{" 11 " LINK ExamineDirs} Examine directories @{" 12 " LINK CheckingFiles} Checking files @ENDNODE @NODE VirusHandling "Virus handling" @TOC CheckFiles In the top left corner you will find a cycle gadget that gives the following options: Comment, @{"Delete" LINK GlossaryD} and Rename. It lets you decide what BootX should do when it encounters a file virus. The Comment option will let you add a filenote to the infected file telling you the name of the virus. For example "BGS-9 (TTV1) filevirus (detected by BootX)" tells you that this file contains the BGS-9 filevirus and that it was detected by BootX. You can see the filenote using most of the directory utilities of using the AmigaDOS 'List' command in the CLI or the Shell. The Delete option deletes the infected file. The Rename option renames the infected file to a name describing the virus. For example "002.BGS-9 virus" indicates that this file contains the BGS-9 virus and it was the 2nd virus found during this file check. @ENDNODE @NODE RemoveLinkviruses "Remove linkviruses" @TOC CheckFiles When this @{"check box" LINK GlossaryC} is checked, BootX will try to remove a linkvirus from an infected file. If the removal is successful the file can be used again without further danger. Be sure that enough memory is available during a file check as BootX needs to load the infected file completely into memory in order to repair it. Also there has to be enough disk spaces left. When the virus has been removed, you will find two files on your disk. One contains the original infected file. It will have a new name reflecting the kind of linkvirus that is attached to the file in the same way as the @{"Rename" LINK VirusHandling} option. The file will not be @{"executable" LINK GlossaryE} anymore so there is no danger you accidentally infect your memory. The virus code is still intact though so don't panic if another viruskiller reports there still is a virus on your disk. The second file retains the original name and contains the cured program. NOTE Some of the older linkviruses and some of the new badly programmed linkviruses destroy the file in such a way that repair becomes impossible. BootX handles these cases gracefully and will tell you about it. @ENDNODE @NODE AutoHandle "Handle viruses automatically" @TOC CheckFiles Normally BootX works completely interactively and asks the user's permission every step of the way. When you check this option BootX makes all decisions by itself and handles all viruses automatically. This is very handy when you want to check that 400MB hard disk with 15000+ files on it. @ENDNODE @NODE ShowDirs "Show directories/files/checked files" @TOC CheckFiles In the upper right hand corner you will find three options controlling the display during the file check. Check 'Show directories' if you want BootX to tell you when it enters a new directory. Check 'Show files' if you want BootX to show you the file it is currently checking. When this option is on BootX also tries to determine what kind of file it is looking at. Turn it off to reduce the time needed to check a path. Check 'Show checked files' if you want BootX to display only those files that it really is checking. @ENDNODE @NODE CheckCrunched "Check crunched executables" @TOC CheckFiles BootX was the first viruskiller to offer you this powerful feature. When it is checked BootX will try to decrunch all crunched executables in memory and then check the decrunched version of the file for any file- or linkviruses. Currently BootX can decrunch the following crunchers: · all PowerPacker versions · all Imploder versions · TNM Cruncher 1.1 · MegaCruncher The Explode.library v6.0 or higher is required if you wish to decrunch Library Imploded files. If there is a cruncher you would BootX like to be able to decrunch, then send me some files that have been crunched with it together with the name of the cruncher and preferably the cruncher program itself too. I will continue to add new decrunch code in future versions of BootX. NOTE If BootX detects a linkvirus in a crunched file, obviously it can not remove the virus since the file is crunched. BootX will tell you to decrunch the file first and ask you if you would like in the mean time to handle the virus like a file virus, that is, to comment, delete or rename the file (see @{"Virus handling" LINK VirusHandling}). @ENDNODE @NODE SkipProtected "Skip read-protected" @TOC CheckFiles Sometimes you want to protect certain files on your disks from reading by removing the read @{"protection bit" LINK GlossaryP}. When this option is selected, BootX will ignore all read protected files. This can be handy since BootX removes all protection bits from infected files except for the Archive and the Delete bit. NOTE This option is mutually exclusive with the 'Auto-remove read-protection' option @ENDNODE @NODE AutoRemove "Auto-remove read-protection" @TOC CheckFiles AmigaDOS 2.0 recognizes and honors the protection bits of a file. That means that if the read protection is on, programs including the Workbench and the Shell are not allowed to read that file. When BootX encounters such a file it will ask you if you want to remove the read protection of that file. If you answer Yes BootX preserves all other protection bits and removes the read protection. The file will then be rechecked. If you wish to restore the read protection afterwards, use the AmigaDOS command Protect like this: 1> protect -r which will give the file its read protection back. NOTE This option is mutually exclusive with the 'Skip read protected' option. @ENDNODE @NODE GenerateReport "Generate report" @TOC CheckFiles Use this check box to turn on the BootX reporting feature. When checked BootX will generate a file check report containing all the information that was shown during the file check. Use this option when doing an unattended file check of large hard disks. The report will serve as a transcript of what happened during the file check. @ENDNODE @NODE SilentCheck "Silent check" @TOC CheckFiles When performing a file check in the background there is no need for BootX continuously displaying all the files it checks. This setting allows you to turn off this display while you can still have BootX make a file check report. @ENDNODE @NODE Filter "Filter" @TOC CheckFiles To enable the @{"path filter" LINK FilterUtility}, check this checkbox gadget. @ENDNODE @NODE ExamineDirs "Examine directories" @TOC CheckFiles This cycle gadget allows you to decide how BootX handles directories. 'All' is the most general option and will have BootX enter all directories it encounters as many levels deep as required. 'Interactively' will have BootX ask you permission to check a directory every time it encounters one. Check this option if you want to make a quick scan of the first level of a directory for example the @{"root" LINK GlossaryR} of a hard disk. 'None' will cause BootX to skip any directory it finds. @ENDNODE @NODE CheckingFiles "Checking files" @TOC CheckFiles You can start the file check by clicking on the 'OK' gadget. BootX will pop up a path requester. This is kind of a stripped down version of a file requester allowing you to comfortably navigate your hard disk while looking for the path you wish to check. The current path will always be displayed in the string gadget. You can enter a path manually or you can use the parent and directory buttons to look for the path. Enter an empty string in the string gadget or click on Cancel to call off the file check. For more information on how to use the path requester I refer to the ReqTools documentation. Double-click on a directory entry or select the OK gadget to begin the file check. During the file check you can press the right mouse button to pause the file check. Press the left mouse button to stop the file check. After the file check BootX will report how many directories, files and crunched files it found. It will also tell you how many files were checked and how many viruses were found. If you asked BootX to generate a file check report you will be given to option to look at it, print it, save it or ignore it. More information about the print and save options can be found in the following sections. Viewing the file check report is the same as viewing a vector check report: click the left mouse button the show the next page, press the right mouse button to abort the viewing. @ENDNODE @NODE ShowReport "Show report" @TOC Check As mentioned in the section about @{"Check files" LINK CheckFiles} BootX is able to generate a file check report while it's looking for viruses. This menu item allows take another look at the last generated file check report. @ENDNODE @NODE SaveReport "Save report" @TOC Check You can also save the last generated file check report to disk for further reference. After you select this option BootX pops up the ReqTools file requester (more information about this requester can be found in the ReqTools documentation). As a default it suggests the filename "LVCReport.doc" but you are free to use any name you like. The file check report is saved as a normal @{"ASCII" LINK GlossaryA} text file with some standard @{"ANSI" LINK GlossaryA} codes to enhance the output. Most recent document viewers such as PPMore can handle these ANSI codes. @ENDNODE @NODE PrintReport "Print report" @TOC Check You can print the last generated file check report from within BootX using this menu item. NOTE If you have to wait a long time (about 10 seconds) and nothing happens, please check that your printer is turned on and if so that it is on-line. BootX will not be able to report an error until the default time-out period is passed (usually 30 seconds) or until the user put the printer on-line. @ENDNODE @NODE CheckDisk "Check disk" @TOC Check When you select this menu item, BootX will put up a requester that allows you to specify which actions BootX should perform when performing a complete disk check. · Check bootblock: checks the bootblock · Check blocks : checks all the disk blocks · Check files : checks all the files All these actions will be performed on the disk in the current drive. Select OK to begin with the disk check. Click on the window close gadget to cancel the disk check. @ENDNODE @NODE LoadSave "Load/Save" @TOC Bootblocks BootX can save the bootblock in the buffer as a file to any drive. 'Save' can be used to save the bootblocks of games, mega demos and other programs to a separate data disk. In case of a virus attack or a bad disk you can load the previously saved bootblock back in the buffer and write it back to the original disk. 'Load' will only allow you to load a file that contains a valid bootblock. It checks if it is an OldFileSystem or FastFileSystem bootblock and then recalculates the checksum of the bootblock. When the bootblock checksum is wrong, BootX will ask you if you want to repair it. If you select Yes, BootX repairs the bootblock checksum of the loaded copy. If the loading was successful BootX will try to identify the bootblock. If the file you loaded did not contain a valid bootblock, BootX will tell you. @ENDNODE @NODE Learn "Learn" @TOC Bootblocks This menu item is turned on when BootX does not recognize the bootblock in its buffer. The bootblock can either be read from disk (using the Read Bootblock gadget) or be loaded using the Bootblocks/Load menu item. If you want to teach an unrecognized bootblock to BootX use this menu item. BootX will pop up a list requester showing the contents of the current Brain file. Simply enter the name for the unknown bootblock in the string gadget under the list. If the name you entered already exists BootX will ask you if you'd like to use the name anyway. This practise is not encouraged. Try to make your names unique. It'll help you identify a bootblock much easier later on. After BootX has learned the bootblock it will display its name in the message window in white. This way you know that it is the Brain file that recognized the bootblock and not the Recog file. NOTE Only the Brain file can be updated by a user. The Recog files will be periodically released by me. The Recog file always takes precedence over the Brain file. That is, if you teach BootX a bootblock as "New Name" and some time later it is identified as "Some new virus" you know that I have added the bootblock to the Recog file. Please send me any bootblock that BootX does not recognize yet. This way the Recog file will always be up to date. @ENDNODE @NODE ShowAgain "Show again" @TOC Bootblocks Use this menu item to refresh the display after it has been erased or been used by some other BootX function. @ENDNODE @NODE BBLibNew "New" @TOC BBLib When you select the BBLib/New menu item the current Bootblock library in memory (if any) will be cleared so that you can started a new one. NOTE BootX always adds four built-in bootblocks when you start a new BootBlock library. These bootblock are the standard OldFileSystem and the standard FastFileSystem bootblock (normal and international version) as they would be installed by the Install command from the C directory. These two bootblocks will not be saved with your Bootblock library. You can tell which bootblocks are built-in by the little dot that appears in the bootblock list. More bootblocks will be added when the need arises. @ENDNODE @NODE BBLibLoad "Load" @TOC BBLib With the Load menu item you can load any Bootblock library. You could for instance have a separate bootblock library for game, demo or utility bootblocks. @ENDNODE @NODE BBLibSave "Save" @TOC BBLib The Save menu item allows you to save the current Bootblock library. This menu item will only be turned on when the Bootblock library was actually changed. @ENDNODE @NODE BBLibShow "Show" @TOC BBLib You can take a look at the contents of the current Bootblock library by selecting the BBLib/Show menu item. BootX will pop up a list requester showing you the names of the bootblocks. @ENDNODE @NODE BBLibMerge "Merge" @TOC BBLib You can share your Bootblock libraries with your friends. The Merge menu item allows you to merge the contents of a Bootblock library with the one in memory. BootX will scan the complete library, ignoring duplicates and adding any new bootblock not yet found in memory. @ENDNODE @NODE BBLibAdd "Add bootblock" @TOC BBLib Use this menu item to add the bootblock currently in the bootblock buffer to the Bootblock library. BootX will pop up a list requester with a string gadget. Enter the name of the bootblock in the string gadget and click on OK (or press return). BootX checks to see if that name already exists and if it does it will ask you if you really want to add the bootblock. @ENDNODE @NODE BBLibDelete "Delete bootblock" @TOC BBLib You can use this menu item to delete a bootblock from the Bootblock library. NOTE You can not delete a built-in bootblock. BootX will warn you if you try to do so. @ENDNODE @NODE BBLibRename "Rename bootblock" @TOC BBLib You can use this menu item to rename a bootblock in the Bootblock library. Select the one you'd like to rename by clicking on its name and then clicking on the OK gadget (or by double clicking the name) BootX will then ask you to enter the new name of the bootblock. NOTE You can not rename a built-in bootblock. BootX will warn you if you try to do so. @ENDNODE @NODE BrainNew "New" @TOC Brain When you select the Brain/New menu item the current Brainfile in memory (if any) will be cleared so that you can started a new one. @ENDNODE @NODE BrainLoad "Load" @TOC Brain With the Load menu item you can load any Brainfile. @ENDNODE @NODE BrainSave "Save" @TOC Brain The Save menu item allows you to save the current Brainfile. This menu item will only be turned on when the Brainfile has been changed during the run of the program. @ENDNODE @NODE BrainShow "Show" @TOC Brain You can take a look at the contents of the current Brainfile by selecting the Brain/Show menu item. BootX will pop up a list requester showing you the names of the bootblocks BootX recognizes in addition to the Recog file. @ENDNODE @NODE BrainMerge "Merge" @TOC Brain You can share your Brainfiles with your friends. The Merge menu item allows you to merge the contents of a Brainfile with the one in memory. BootX will scan the complete Brainfile, ignoring duplicates and adding any new bootblock not yet found in memory. @ENDNODE @NODE BrainDelete "Delete Brain cell" @TOC Brain You can use this menu item to delete a bootblock from the current Brainfile. @ENDNODE @NODE BrainRename "Rename Brain cell" @TOC Brain You can use this menu item to rename a bootblock in the current Brainfile. Select the one you'd like to rename by clicking on its name and then clicking on the OK gadget (or by double-clicking the name) BootX will then ask you to enter the new name of the bootblock. @NODE PrefEdit "Edit..." @TOC Preferences Use Preferences/Edit to change some settings of BootX. As of version 5.10 all your settings are being kept in a file called 'BootX.prefs' which can be found in the directory 'BootX' of device ENV: and ENVARC:. The file is a plain ASCII file which can be read using any text reader or modified using any text editor. Be carefull though because the parsing routines are not very smart and presume a couple of things. It is better to change your settings using BootX and to save them. @{" 1 " LINK VirusAlarm} Virus alarm @{" 2 " LINK VirusAlarm} Save icons @{" 3 " LINK DetectDiskChange} Detect diskchange @{" 4 " LINK CheckDV} Check disk-validator @{" 5 " LINK Crunch} Crunch @{" 6 " LINK StartIconified} Iconify at startup @{" 7 " LINK StartMemCheck} Check memory at startup @{" 8 " LINK StartVecCheck} Check vectors at startup @{" 9 " LINK Pause} Pause after page @{" 10 " LINK Wrap} Wrap words @{" 11 " LINK SetDisplayMode} Display Mode @{" 12 " LINK SetPalette} Palette @ENDNODE @NODE VirusAlarm "Virus alarm" @TOC PrefEdit BootX can grab your attention when it finds a virus by using one of the following three possibilities: (1) None: BootX will remain silent when it finds a virus. (2) System beep: BootX will DisplayBeep the BootX screen. If you have installed a sample using the Sound preferences editor this is what you'll hear. Otherwise the colors of the BootX screen will be flashed. (3) Play sample: BootX will play the sample found in the file BootX.Alarm. This file is loaded at startup time (when found). The file must use the @{"IFF 8SVX" LINK GlossaryI} file format. Most if not all sample creating programs support this file format. @ENDNODE @NODE SaveIcons "Save icons" @TOC PrefEdit Check this settings if you'd like BootX to create an icon for any of the files it saves. @ENDNODE @NODE DetectDiskChange "Detect diskchange" @TOC PrefEdit If this option is turned on, BootX will know when you insert a disk in any of the available disk drives. That drive will be made current and BootX will try to read the bootblock of the disk you just inserted. To make BootX read a bootblock of a disk when this settings is turned off, make the drive current that contains the disk you'd like to check and click on the Read Bootblock gadget. @ENDNODE @NODE CheckDV "Check disk-validator" @TOC PrefEdit The disk-validator used to be a part of AmigaDOS 1.2/1.3 that could be found as a file called Disk-Validator in the L drawer of a boot disk. There are some viruses that make use of the feature to infect your computer and disks. The disk-validator would be loaded automatically when AmigaDOS detected a non validated disk. The disk-validator would then be put to work to repair the disk. When this option is turned on BootX will check if such a file exists on your disk after it has tested the bootblock. BootX will check if it has been infected before a possible virus gets a chance to get in your system. BootX does this by not using AmigaDOS but directly manipulating the disk. To have the most benefit of this feature, also use the Lock Drive gadget. Read also @{"How to kill disk-validator viruses..." LINK HowToKill}. NOTE KickStart 2.0 does not need the disk-validator anymore since the repair code has been built in. This also means that Amigas running KickStart 2.0 or later can not be infected by inserting a disk that contains one of those 'disk-validator viruses'. @ENDNODE @NODE Crunch "Crunch" @TOC PrefEdit BootX crunch the Bootblock library and the Brain file before saving them. It uses the powerpacker.library (© Nico François) to crunch the files. The 'Never' setting will never crunch any files. The 'Ask' setting will cause BootX to ask you every time you save the Bootblock library or the Brain file if you'd like BootX to crunch them. The 'Always' setting will ask no questions and will always crunch before saving. NOTE Sometimes BootX will not be able to crunch your files. BootX will typically report this as a buffer overflow. This is because your data files have to much entropy. This is neither a bug in BootX nor a bug in the powerpacker.library. In this case you will have to turn off crunching and save the file uncrunched. @ENDNODE @NODE StartIconified "Iconify at startup" @TOC PrefEdit When this setting is on (checked) BootX will start running in an iconified state. See @{"Iconify" LINK Iconify} for more details. @ENDNODE @NODE StartMemCheck "Check memory at startup" @TOC PrefEdit If this setting is checked BootX will check the memory of the Amiga for viruses every time it gets started or after it returns from an iconified state. It is a good idea to have this setting turned on. You can always force BootX to recheck your memory using the Check/Check memory menu item. @ENDNODE @NODE StartVecCheck "Check vectors at startup" @TOC PrefEdit This option works the same as the 'Check memory at startup' option. Turn it on if you'd like BootX perform a complete vector check every time you start BootX. NOTE In order to let you read any error message that are shown at startup time (for example if something goes wrong when trying to load the Recog file) BootX will look at your settings right before starting the vector check. If you have turned on the @{"Pause after page" LINK Pause} setting, BootX will ask you to click the left mouse button before it shows you the vector check report. @ENDNODE @NODE Pause "Pause after page" @TOC PrefEdit Turning this setting on causes BootX to pause the screen output every time a full screen page has been shown. See also the note in @{"Check vectors at startup" LINK StartVecCheck}. @ENDNODE @NODE Wrap "Wrap words" @TOC PrefEdit Sometimes the output of BootX is longer than will fit in the window. With this option you control wether BootX cuts off the output or wraps the remaining part on the next line. @ENDNODE @NODE SetDisplayMode "Display Mode" @TOC PrefEdit BootX can use any screen mode that the Monitors database offers to you. If you click this gadget BootX will put up the ReqTools display requester allowing you to choose which screen mode will be used. If you select a new display mode your choice will become active immediately. @ENDNODE @NODE SetPalette "Palette" @TOC PrefEdit Clicking this gadget makes BootX put up the ReqTools palette requester. You can use it to customize the BootX screen colors. @ENDNODE @NODE PrefLoadSave "Load/Save" @TOC Preferences Use these menu items to load or save the current settings from or to the BootX.prefs file. After a succesfull load BootX will close and reopen its screen even if you did not change the display settings. @ENDNODE @NODE HowToKill "How to kill disk-validator viruses..." @TOC Hints First make sure that your memory is clear of any virus. You can do this by turning of your Amiga for a few seconds and then booting from a NON-INFECTED disk. Always make sure all the disks you insert are WRITE-PROTECTED unless it contains a disk-validator virus you want to kill. Start BootX and lock the current drive by clicking on the Lock gadget next to the drives cycle gadget. This prevents AmigaDOS and the Workbench from accessing the disks you are about to insert. Insert the infected disk into the current drive and click on the Read gadget. BootX now reads the bootblock and checks the file called 'disk-validator'. This file can be found in the L drawer of the disk. If BootX does not check the disk-validator, make sure that the 'Check Disk-Validator' check box is checked in the Preferences requester. When BootX finds a disk-validator virus, it will ask you if it should kill the virus. If you select Yes, BootX destroys the complete virus code and makes a harmless executable program of it that does nothing than set the dos error code to -1. Next you are given the advice to repair the disk using the 'Check blocks' menu item. As a last step you need to copy an UNINFECTED disk-validator file into the L drawer of the repaired disk. This step could not be automated because the Disk-Validator file is copyrighted by Commodore Amiga. @ENDNODE @NODE LowMemory "Using BootX with little memory" @TOC Hints BootX has become quite a large program over the years and together with its support files it can occupy over 200K of RAM. Don't generate a file check report when checking your hard disk. The file check report for hard disks with 5000+ files can grow easily larger than 200K. Clear the Brain and BBLib files using the 'BBLib New' and 'Brain New' menu items respectively. Delete or rename the file 'BootX.Alarm'. It contains the sample BootX uses to alert the user if it finds a virus. Use the System Beep option of the Preference requester instead. Use the lowest possible screen mode the Display Mode requester has to offer. Specify the screen dimension as low as possible. @ENDNODE @NODE BBCopy "Copying bootblocks with one drive" @TOC Hints Turn off the Detect Diskchange setting in the Preference requester. Insert your disk in the disk drive. Click on the Read Bootblock gadget. The bootblock will now be read into the BootX buffer and will be shown in the main window. Remove the disk from your disk drive and insert the disk you want the bootblock copied to. Click on the Write Bootblock gadget. BootX will now write its buffer to the newly inserted disk. @ENDNODE @NODE SHI "About Safe Hex International" @TOC Main Our motto: "Safe Hex..." BootX can be kept up to date thanks to the energy and work put into a global anti-virus information bank called Safe Hex International (SHI) founded by Erik Løvendahl Sørensen from Denmark. This group has over 250 international members now, among them some of the programmers of well-known anti-virus programs like Steve Tibbet and Jonathan Potter. Among the activities of this group are: - Spreading information to anti-virus programmers as fast as possible. - Trying to get names and proof against virus programmers and giving the information to the justice department of his/her country to press charges. - Writing articles in over 8 popular magazines to inform new Amiga users about viruses and how to protect themselves. - Collecting viruses and virus information as well as the programs to kill the viruses. - Helping people to get their money back if it has been lost due to virus infection. - Releasing the newest and best viruskillers found. - We have set up over 20 Regional Virus Centers worldwide. These virus centers provide free help against viruses through a hotline and they translate the newest viruskillers and their documentation in their local language. Also the organization is prepared to pay $ 1000 US for the name and the address of a virus programmer. All information will be delt with confidentially and will be handed over to the proper authorities of the virus programmer's country. Data crimes are punished severely most of the time with up to 5 years imprisonment. All this is volunteer work. If you want some more information about this organization or you want to sponsor our work, contact Erik at the following address: SHI Safe Hex International Erik Løvendahl Sørensen Snaphanevej 10 4720 Præstø Denmark - Europe Phone: 00 45 55 99 25 12 Fax : 00 45 55 99 34 98 Fido : (Soon) @ENDNODE @NODE Addresses "Addresses" @TOC Main Peter Stuer Kauwlei 21 B-2550 Kontich Belgium - Europe Fido : 2:292/603.7 Great Balls Of Fire BBS Herman Stevens Lubbeek ADS Regional Coordinator Belgium Phone: +32-(0)16-64.09.12 14400 BPS (N.8.1) v32bis v42bis 24-24 h. Fido : 2:292/603 SHI Safe Hex International Erik Løvendahl Sørensen Snaphanevej 10 4720 Præstø Denmark - Europe Phone: 00 45 55 99 25 12 Fax : 00 45 55 99 34 98 Fido : (Soon) @ENDNODE @NODE Language "Using BootX in a different language" @TOC Main If you are using @{"Workbench" LINK GlossaryW} v2.1 BootX will try to open the @{"locale.library" LINK GlossaryL} to make use of its language support. If BootX finds a catalog in the language currently used in the system BootX will use it. Normally you set your preferred language using the Locale preference editor of the Workbench. If BootX finds a @{"tooltype" LINK GlossaryT} in its icon called LANGUAGE it will use this language to override the system language. For example if you run your Workbench in English but you want to use BootX in Dutch then add the following tooltype to the BootX icon: LANGUAGE=nederlands NOTE Make sure BootX can find the appropriate language catalog either in the directory 'Locale:Catalogs/' or in the directory 'Catalog/' from which BootX started. @ENDNODE @NODE Glossary "Glossary" @TOC Main Glossary The glossary will help inexperienced users understand some of the more technical terms found in this document. @{" A " LINK GlossaryA} @{" B " LINK GlossaryB} @{" C " LINK GlossaryC} @{" D " LINK GlossaryD} @{" E " LINK GlossaryE} @{" F " LINK GlossaryF} @{" G " LINK GlossaryG} @{" H " LINK GlossaryH} @{" I " LINK GlossaryI} @{" J " LINK GlossaryZ} @{" K " LINK GlossaryK} @{" L " LINK GlossaryL} @{" M " LINK GlossaryM} @{" N " LINK GlossaryZ} @{" O " LINK GlossaryO} @{" P " LINK GlossaryP} @{" Q " LINK GlossaryZ} @{" R " LINK GlossaryR} @{" S " LINK GlossaryS} @{" T " LINK GlossaryT} @{" U " LINK GlossaryZ} @{" V " LINK GlossaryV} @{" W " LINK GlossaryW} @{" X " LINK GlossaryZ} @{" Y " LINK GlossaryZ} @{" Z " LINK GlossaryZ} @ENDNODE @NODE GlossaryA "Glossary Part A" @TOC Glossary A AmigaDOS The disk operating system (DOS) used by Amiga computers. ANSI American National Standards Institute. A set of codes to perform special functions like printing text in bold. appicon An icon on the Workbench that allows the user to pass arguments to an application. BootX puts an AppIcon on the Workbench when you select the Project/Iconify menu item. application gadget A graphics image that appears within a program which can be manipulated with the mouse to perform a certain function. ASCII American Standard Code for Information Interchange. The code set that the Amiga uses to represent letter and figures. assembler A programming language attributes A series of flags stored with every file. Attributes indicate file type and control the file operations (read, write, delete, etc.) Also @{"protection bits" LINK GlossaryP}. @ENDNODE @NODE GlossaryB "Glossary Part B" @TOC Glossary B BBLib See 'bootblock library'. boot The startup process for a computer. It comes from the expression "pulling yourself up by the bootstraps." bootblock Part of a disk or hard disk that is read first by the Amiga to initialize or recognize the disk. Usually contains a small program (disks) or parameters (hard disk). bootblock library A custom file of BootX that contain several bootblocks that the user can install on his disks. bootvirus Virus that hides in the bootblock of a disk. Only gets activated when you boot from the infected disk. Brain file Supplementary recognition information that the user has taught BootX using the Bootblocks/Learn menu item. bug A mistake in a program @ENDNODE @NODE GlossaryC "Glossary Part C" @TOC Glossary C check box A gadget used to let a user turn an option on or off. When a check mark appears in the box, the selection is considered to be "on." Chip RAM The area of RAM accessible to the Amiga's custom chip set used for graphics and sound data. Also called graphics memory. CLI (Command Line Interface) A means of communicating with the Amiga by issuing commands from the keyboard. click To press and release a mouse button close gadget A system gadget used to close windows. It appears in the upper left corner of the window. cold reboot To reset the Amiga by turning the power off, waiting 20 seconds, and then turning it on again. CPU Central Processing Unit. The micro processor that executes the instruction that make up a program. The Amiga either has a MC68000, MC68020, MC68030 or MC68040 CPU. Crunch Transforming data in such a way that the result uses less memory or disk space. BootX optionally uses the PowerPacker library to crunch or decrunch the data it uses. current drive The drive that will be used by default for any BootX operation unless the user specifies another. cycle gadget An application gadget that allows the user to select one of several options. One option is displayed at a time and, as the gadget is selected, the other options become visible. The displayed option is the selected option. @ENDNODE @NODE GlossaryD "Glossary Part D" @TOC Glossary D default Initial setting, what will be used if nothing else is supplied. delete To erase or discard a file, buffer, or other stored item. device A physical mechanism, such as a disk drive, used as a source or destination for information directory A subdivision in a computer's filing system. Directories are represented on the Workbench as drawer icons. disk A medium for storage of computer data. disk-validator An extension of the pre-2.0 AmigaDOS. It was loaded from disk whenever the user inserted a bad or corrupted disk. The disk-validator tried to repair the disk. double-click To press and release the mouse's @{"selection button" LINK GlossaryS} twice. drawer See 'directory' drive name The name assigned to a floppy disk drive or hard disk such as Work:, WB2.x: or DF0:. It is the same as the device name. @ENDNODE @NODE GlossaryE "Glossary Part E" @TOC Glossary E executable A type of file that contains program instructions that the Amiga can use the execute a program. Executables are the prime target for linkviruses. @ENDNODE @NODE GlossaryF "Glossary Part F" @TOC Glossary F FastFileSystem (FFS) An enhanced Amiga file system usable with both floppy and hard disks. A @{"volume" LINK GlossaryV} is formatted as either FFS or OldFileSystem (OFS). The advantages of FFS are increased storage capacity and faster access of files. Fast RAM General memory used by programs and data, as opposed to @{"Chip RAM" LINK GlossaryC}. file A collection of data filename The name by which a program or a data file is known to the Amiga when you want to access it on disk or hard disk. FPU Floating Point Unit. Special purpose micro processor to speed up calculations using real numbers. The FPU's available for the Amiga are called MC68881 and MC68882. @ENDNODE @NODE GlossaryG "Glossary Part G" @TOC Glossary G gadget Any graphics image that can be found in a window or on a screen that can be manipulated with the mouse to perform a certain function. graphics memory See @{"Chip RAM" LINK GlossaryC} GUI Graphical User Interface @ENDNODE @NODE GlossaryH "Glossary Part H" @TOC Glossary H hot key A special key or key combination that triggers a certain action. BootX uses a hot key to uniconify or to bring its screen to the front. @ENDNODE @NODE GlossaryI "Glossary Part I" @TOC Glossary I icon An image appearing on the screen to represent a disk, drawer, project or tool. Icons can be moved and selected with the mouse to allow you to work with the items they represent. IFF 8SVX A file format following the Interchange File Format (IFF) specifications. It's purpose is to allow easy interchange of 8 bit sound samples. @ENDNODE @NODE GlossaryK "Glossary Part K" @TOC Glossary K K Kilobyte. 1024 bytes. KickStart Software that is read from disk and used to boot the Amiga. Also refers to the portion of the OS that is in ROM. BootX requires at least version 2.04 of the KickStart. @ENDNODE @NODE GlossaryL "Glossary Part L" @TOC Glossary L Locale.library A library available with Workbench 2.1 that allows programmers to write language independent programs. library A related set of functions that can be shared by various programs. BootX uses for example the PowerPacker.library to load and save crunched data. linkvirus A virus that spreads itself by linking its own code to other programs. When you run an infected program the virus hides itself in memory before allowing the program to execute. There it waits to infect other programs. @ENDNODE @NODE GlossaryM "Glossary Part M" @TOC Glossary M MB Megabyte. 1,048,576 bytes MMU Memory Management Unit. Special purpose micro processor that can efficiently control the memory of the Amiga. The MMU available for the Amiga is the MC68851. menu A list of on-screen options, displayed by using the menu button, from which users can choose commands that control a program. menu button The right mouse button menu item An option that appears in a menu @ENDNODE @NODE GlossaryO "Glossary Part O" @TOC Glossary O OldFileSystem (OFS) The file system used by pre-2.0 AmigaDOS. @ENDNODE @NODE GlossaryP "Glossary Part P" @TOC Glossary P path The series of device, directory and @{"subdirectory" LINK GlossaryS} names that defines the location of a file. PowerPacker.library A shared library written by Nico François. It allows BootX to read and write crunched files using the PowerPacker crunching algorithm. processor See @{"CPU" LINK GlossaryC} protection bits See @{"attributes" LINK GlossaryA} @ENDNODE @NODE GlossaryR "Glossary Part R" @TOC Glossary R RAM Random Access Memory. Part of the Amiga's internal memory that can be used for data storage and is directly accessible by the CPU. Data in RAM is lost when the Amiga is rebooted or powered off. read only If a disk status or a file @{"attribute" LINK GlossaryA} is Read Only, the user can only look at the contents of the disk or the file without modifying it. reboot To reset the Amiga by pressing the keys Ctrl, Left-Amiga and Right-Amiga simultaneously. Also called a warm boot. Recog file The file that contains all the information that BootX needs to recognize and kill boot- and linkviruses. ReqTools.library A shared library written by Nico François. It has special functions to create the several kinds of requesters that BootX uses. requester A window that allows the user to control options, access files or confirm actions. ROM Read Only Memory. root directory The main directory of a volume. All other directories are created in the root. The word comes from the analogy between the structure of the file system and the shape of a tree. @ENDNODE @NODE GlossaryS "Glossary Part S" @TOC Glossary S SCSI Small Computer System Interface. A standard interface protocol for connecting peripherals, usually mass storage devices like hard disks, to computers. selection button The left mouse button. subdirectory A @{"directory" LINK GlossaryD} within another directory @ENDNODE @NODE GlossaryT "Glossary Part T" @TOC Glossary T Tool Types A method for passing arguments from the @{"Workbench" LINK GlossaryW} to a program. BootX uses the tool types to store the user preferences. @ENDNODE @NODE GlossaryV "Glossary Part V" @TOC Glossary V vector A memory address used by the operating system to access parts and functions of the libraries and devices. Most viruses change one or more viruses to modify the behavior of the Amiga. volume A floppy disk or a hard disk partition volume name The name given to a disk or partition @ENDNODE @NODE GlossaryW "Glossary Part W" @TOC Glossary W Workbench The Amiga's icon-based @{"GUI" LINK GlossaryG}. write-enable To allow information to be written onto a disk. write-protect To prevent information from being written onto a disk. @ENDNODE @NODE GlossaryZ "Glossary Error" @TOC Glossary No entries found for this letter. @ENDNODE @NODE Index "Index" @TOC Main A @{" About AmigaGuide " LINK Help} @{" About BootX " LINK About} @{" About menu item " LINK About} @{" About Safe Hex International " LINK SHI} @{" About the author " LINK Author} @{" Acknowledgements " LINK Acknowledge} @{" Add bootblock menu item " LINK BBLibAdd} @{" Addresses " LINK Addresses} @{" Auto-remove read-protection " LINK AutoRemove} B @{" BBLib Menu " LINK BBLib} @{" Brain Menu " LINK Brain} @{" Bootblocks Menu " LINK Bootblocks} @{" Built-in bootblock name " LINK BuiltInName} C @{" Check blocks menu item " LINK CheckBlocks} @{" Check crunched executables " LINK CheckCrunched} @{" Check disk menu item " LINK CheckDisk} @{" Check disk-validator gadget " LINK CheckDV} @{" Check files menu item " LINK CheckFiles} @{" Check files gadget " LINK CheckFilesGad} @{" Check memory at startup gadget " LINK StartMemCheck} @{" Check memory menu item " LINK CheckMemory} @{" Check Menu " LINK Check} @{" Check vectors at startup gadget " LINK StartVecCheck} @{" Check vectors menu item " LINK CheckVectors} @{" Checking files " LINK CheckingFiles} @{" Copying bootblock with 1 drive " LINK BBCopy} @{" Crunch gadget " LINK Crunch} D @{" Delete bootblock menu item " LINK BBLibDelete} @{" Delete Brain cell menu item " LINK BrainDelete} @{" Detect disk change gadget " LINK DetectDiskChange} @{" Display mode gadget " LINK SetDisplayMode} @{" Drive cycle gadget " LINK DriveGadgets} E @{" Edit preferences menu item " LINK PrefEdit} @{" Examine directories " LINK ExamineDirs} F @{" Filter menu item " LINK FilterUtility} G @{" Gadgets " LINK Gadgets} @{" Generate report " LINK GenerateReport} @{" Gettings updates " LINK Updates} H @{" Handle viruses automatically " LINK AutoHandle} @{" Help menu item " LINK BootXHelp} @{" Hints, tips and tricks " LINK Hints} @{" How to kill... " LINK HowToKill} I @{" Iconify at startup gadget " LINK StartIconified} @{" Iconify menu item " LINK Iconify} @{" Install gadget " LINK Install} L @{" Language support " LINK Language} @{" Learn bootblock menu item " LINK Learn} @{" Load BBLib menu item " LINK BBLibLoad} @{" Load Brain menu item " LINK BrainLoad} @{" Load Recog file menu item " LINK LoadRecog} @{" Load/Save bootblock menu item " LINK LoadSave} @{" Load/Save preferences menu item " LINK PrefLoadSave} @{" Lock drive gadget " LINK LockDrive} M @{" Menus " LINK Menus} @{" Merge BBLib menu item " LINK BBLibMerge} @{" Merge Brain menu item " LINK BrainMerge} N @{" New BBLib menu item " LINK BBLibNew} @{" New Brain menu item " LINK BrainNew} P @{" Palette gadget " LINK SetPalette} @{" Pause after page gadget " LINK Pause} @{" Preferences Menu " LINK Preferences} @{" Print known... menu item " LINK PrintKnown} @{" Print report menu item " LINK PrintReport} @{" Project Menu " LINK Project} Q @{" Quit gadget " LINK Quit} @{" Quit menu item " LINK Quit} R @{" Read bootblock gadget " LINK ReadBB} @{" Remove linkviruses gadget " LINK RemoveLinkviruses} @{" Rename bootblock menu item " LINK BBLibRename} @{" Rename Brain cell menu item " LINK BrainRename} @{" Reset vectors menu item " LINK ResetVectors} S @{" Save BBLib menu item " LINK BBLibSave} @{" Save Brain menu item " LINK BrainSave} @{" Save report menu item " LINK SaveReport} @{" Show again menu item " LINK ShowAgain} @{" Show BBLib menu item " LINK BBLibShow} @{" Show Brain menu item " LINK BrainShow} @{" Show dirs/files/checked files " LINK ShowDirs} @{" Save icons gadget " LINK SaveIcons} @{" Show installable BB " LINK ShowInstallBB} @{" Show known... menu item " LINK ShowKnown} @{" Show report menu item " LINK ShowReport} @{" Silent check " LINK SilentCheck} @{" Skip read-protected " LINK SkipProtected} @{" System requirements " LINK Requirements} T @{" ToolBox Menu " LINK ToolBox} U @{" Using BootX with little memory " LINK LowMemory} V @{" Virus alarm gadget " LINK VirusAlarm} @{" Virus handling gadget " LINK VirusHandling} W @{" Wrap words gadget " LINK Wrap} @{" Write bootblock gadget " LINK WriteBB} @ENDNODE