DisKey 2.1 - preliminary documenation 1.1 Legalese This entire document is (c) 1991 by Thomas Baetzler. You are granted the non-exclusive right to print one (1) copy of this text for your personal use. You may copy this file only as part of the DisKey distribution, under the rules that the author of DisKey, Angela Schmidt, imposes. The author of this manual does not guarantee for the correctness of informations contained in this manual. While much time has been spent on proof reading, I would just be surprised if there wasn't some kind of mistake somewhere. The author also disclaims any liability which could arise from improper use of DisKey. Whatever you do with DisKey is just your own risk. If you think this is paraniod: This is just to protect my rights. While I expect to gain nothing for all my troubles, except maybe an ARexx port in one of the next releases of DisKey, this is my insurance against anybody who wants to make money with this by reprinting it as instruction set in a computer magazine. This happened to Angela Schmidt with the German instructions to DisKey 1.2, which were reprinted without permission in the magazine "Amiga Praxis". If you want to contact me, please feel free to do so: Thomas Baetzler 2:247/7501.5 (Fidonet) Schlossbergstr. 4 tom@armchair.ka.sub.org (UUCP, est. Jun-91) 7570 Baden-Baden While I do not charge you for reading this, it would be nice to hear from you: Comments on style and language are always welcome, as much as postcards from your hometown, or a book or magazines you don't need any longer. Especially printed matter is really appreciated, since you have to pay 2 to 5 times of the cover value, if you manage to get anything at all. 1.2 Notes on DisKey Version 2.1 of DisKey is Shareware. If you're unfamiliar with this concept: You may use this program free of charge to try it out, whether it fills your needs or not. If after a sufficient long trial period you find that you want to continue use DisKey, please be so fair and pay up your debt to Angela. Your support will ensure that Angela continues to improve this project. Authors of Shareware products who wish to use DisKey could alternatively send Angela a registrated copy of their product, in turn they will receive their registrated copy of DisKey. As an alternative to the Shareware DisKey, there's DisKey professional: It offers all of the functionality of the original DisKey, and additionally it supports access to all sector oriented exec-devices like your hard disk, the recoverable ramdisk RAD:, and many more. DisKey professional comes even with two new devices/handlers, which will let you edit files and the RAm part of your computer's memory. 1.2.1 What is DisKey? DisKey is a sector oriented disk monitor. The stress on 'sector' implies that it wasn't written to patch files, but to make changes to a disk's structure. The name implies the history: Angela wrote DisKey, because she had time and time again problems with errors on her disks, and the disk validator only referred to the condition of key so-and-so. As the disk doctor proved quite unreliable, and disksalv (Thanks, Dave!) was still in the making, Angela decided to tackle the problem herself: First of all she needed a tool to examine and change the structures on disk. This is how DisKey was born. 2.0 Getting to know DisKey It may well take you a long time to tackle all the features in DisKey: Just like with a Transformer (tm), there's 'more than meets the eye'. However, there's no need to know everything, it just makes life a bit easier, if you're using DisKey all the time. 2.1 The Layout After starting DisKey, you will see the Main screen: On top is the menu bar. Just below, there is the hexadecimal display area, in which the currently loaded sector is displayed as hexadecimal numbers. Every four bytes are grouped together as a longword, so that we end up with eight columns of 16 longwords. Order is from left to right, and then down, so that the leftmost two digits of the first line of the first column are the first byte of the current sector, while the byte just below ist the 33th. byte. Below the hexadecimal display, there is the Iconify-Gadget to the left, while the rest of that line is devoted to the information exchange. Per default this small window displays some calculations based on your current cursor position in the hex display. If the dis.library is installed in libs:, you can switch the display mode to disassembly and back by clicking once in this line. Below that, there's three boxes: The left- and rightmost form the ASCII display of the current sector. You should imagine the leftmost box as sitting on top of the rightmost box, so that you get 16 lines of 16 characters. This display maps a byte value to the corrresponging character of the active font, so that it also displays 'unprintable' characters, unlike the AmigaDOS 'Type' command in 'HEX' mode. In between these, there's the command selection box. The general idea behind this is to provide a versatile user interface: You can invoke most commands with either shortcuts bound to the left or right Amiga key, or select them from the menu, or select them by clicking the appropriate line in the command selection box. The command selection box has three menus to display: Hitting the right mouse button while the cursor is not in the top row of the screen will switch to the next menu. Below the left ASCII-display box, there's two boxes for sector selection. Each value can be modified by clicking on the '+' and '-', or by clicking on the numbers, and entering a value manually. But pay attention: While one of those input fields is active, DisKey accepts no other commands. Be sure to leave an input field by hitting Return! And this leaves just one thing for description: The message box. In this Area, DisKey displays any kind of information it thinks you'd like to know, like type of the current sector, or return code from the last action. If you can't understand what DisKey is telling you, check whether the Menu Language is set to English: Find the menu DisKey.prefs, and select "Sprache", subitem "English". 2.2 Editing a sector As you have noticed, DisKey displays the current sector in two ways: As hex digits, and as ASCII characters. You can change the contents of the sector from both displays, although only one of them is active at any given moment: You can tell by the color of the border. If it doesn't match the colors of the other boxes on the screen, it's activated. You can switch the active display by clicking into the deactivated display: DisKey will then place the cursor of the display under the mouse pointer. (Well, it isn't really a mouse, it's rather your cute pink-ish 'Nessie' pointer, which reminds you that DisKey is active at the moment, and that everything you type is going to be sent to DisKey for evalution. It's rather useful if DisKey runs in it's own screen, and you've just switched screens to another application: A perfectly harmless shortcut in your application might be misinterpreted by DisKey. The best case is when you just realize that things don't work the way they're supposed to.) The hex display accepts only hexadecimal numbers as input, which must be composed of the digits 0..9 and the characters a..f. Each number consists of two digits. Both are highlighted when the cursor is moved on them. Entering the first digit will change the high nibble of the number you're currently editing. If you only want to cahnge this, you could then use the cursor keys to move to the next number you want to change. If you only want to change the low nibble, you still have to copy the high nibble. In the ASCII display, you can enter any character you like: Even dead keys are supported, so that you can enter things like 'à' as a combination of '`' and 'a'. The cursor keys work as one might expect: Left and right move you to the preceding or following byte of data. When you are at the beginning or the end of a sector, moving beyond that border will place you at the end or the beginning, respectively. Moving up and down will scroll you through the columns of data, without necessarily jumping to the logically next or previous byte. When used in conjunction with the Control key, the cursor keys will act differently: CTRL-up will set the cursor at the beginning of the sector, and CTRL-down will set it at the end. CTRL-Left and right will place it at the beginning or the end of the current line. The ALT key adds an Undo-feature: While moving into an sector with any combination of ALT and the cursor keys, the former contents will be restored. You can tell when a value is modified by it's color: It then matches the color of the box borders. When you write a sector back successfully, the changed bytes are displayed in the background color. You can undo these aswell, until you write the sector again, or read in a new sector. 2.3 The integrated disassembler To use this feature, you need to have the dis.library in the libs: drawer of your workbench disk. You activate the disassembler by clicking into the information exchange window. It will then display the value of the word below the cursor interpreted as MC 680x0 mnemonic. Sadly, there's no assembler included, so you can't enter mnemonics directly. As there is no secure method to estimate where a 680x0 instruction begins, the DisKey disassembler tries not to be smart about this. If you're sure that you've one instruction right, SHIFT-ALT-right will move the cursor to the beginning of the next instruction. In the reverse direction you might encounter some problems. 2.4 The safety catch In the standard configuration, DisKeey is set up so that it will not do potentially dangerous things without first checking back with the user. Selecting an option like 'Write block' or 'Format kwik' will usually bring forth an requester asking you whether you want to go ahead or not. If you select 'OK', you're on your own. A way to override this is to hold down either mouse button or hotkeys: After some seconds, DisKey decides you're sure of what you're doing, and goes ahead without further prompting. But there are people among us who think that they know what they're doing: If you don't feel like having a stupid application waring you of possible dangers, you might aswell deselect the "safety catch" in "DisKey.prefs". This disables all fail-safes and turns DisKey in the "You wanted it, now you've got it' kind of disk monitor. This might please the masochistic Un*x user who just loves the feeling of katharsis when just another valuable data disk goies down the drain, but for the average user, I recommend to keep the safety catch on. I even recommend the additional safety of only letting DisKey loose on backup copies of valuable disks: While fixing a mashed root block with DisKey is certainly faster than running DiskSalv when you know what you're doing, you're asking for trouble if you're doing this on the master disk. Make a mistake, and nobody can tell whether DiskSaly will be able to fix the additional damage you might have caused. 2.5 Virus check Whenever you change a disk in the currently active drive, DisKey checks the disk's bootblock for viri and other abnormalities. If it detects anything out of the normal, it will display the bootblock instead of the rootblock, and print out a warning message in the status display. Currently, DisKey knows the following viri: Byte Bandit Plus VIRUS Byte Bandit VIRUS Warhawk VIRUS Bamiga Sector one VIRUS Micro Master Virus LSD VIRUS SCA-VIRUS SCA-Mutation DASA (Byte Warrior) VIRUS Paramount VIRUS Byte Warrior Mutation North Star II VIRUS System Z VIRUS V3.0 System Z VIRUS V4.0 System Z VIRUS V5.0 System Z VIRUS V5.4 (PVL-VIRUS) GADAFFI VIRUS North Star I VIRUS DiskDoctors VIRUS Revenge VIRUS 1.2 Pentagon VIRUS Time Bomb VIRUS 1.0 Lamer-Exterminator VIRUS GYROS-VIRUS Obelisk-VIRUS VKill V1.0 VIRUS WAFT-VIRUS MCA (Class Abraham) VIRUS H.C.S VIRUS Butonic VIRUS The virus check is really simple, since DisKey has to work without a large brain file. While the virus check is far from fool proof, it is still quite useful, especially if you're working with someone else's disks. As the test only checks two or there longwords of the code, it might aswell happen that a completely inncocent bootblock gets out signed as dangerous. If you're in doubt, please use a dedicated virus checker like ZeroVirus to verify the warning. However, it is quite smart about the Lamer Exterminator, since it reads the bootblock twice: First try is with normal TD_READ. The lamer exterminator patches this call to put up a standard bootblock instead of his own code. So you can have a second try by having "Raw Read" selected in "DisKey.prefs": DisKey then re-reads the bootblock using TD_RAWREAD, and if the result differs from the first try, your system is propably currently infected by a lamer exterminator virus, and you'll be notified of this condition. Sadly, RAWREAD has a bug in some older revisions of the OS: You might continously get the warning 'TD_READ<>RAWREAD' without having an infected system. In this case, the safe check fails for you. Sorry, pal. Since there is a fairly large number of custom bootblocks around, DisKey also checks for these. They are not displayed as nonstandard boot code. Observe Bootblock Neuhaus Bootblock Sigma Virusterminator Bootblock AVIREX-Bootblock CCS-Bootblock Chip-Bootblock Blizzard Protector MEMCTRL-Bootblock Starfire2-Bootblock Bootcopy-Bootblock XCopy Bootblock Tristar Viruskiller V1.1 Viruskiller Professionel V2.0 Aside from this, there's a number of bootblocks of which DisKey doesn't know whether they're dangerous or not. In the meantime, you'll be notified of their presence just as they were viri: ASS VIRUS Bootblock Virus Destructor Bootblock SQC Bootblock Hotline Bootblock Overscan Bootblock MGF Bootblock Memory_I Bootblock Memory_II Bootblock Pentagon Bootblock-Loader Phaselock Bootblock Playfield Bootblock Protected Bootblock StealMem Bootblock Virus Alert I Bootblock Virus Alert II Bootblock PVL Protector 2.6 The status window DisKey tries always to provide you with all the information it can get. Under certain circumstances, and especially with the Fast Filesystem, this is not always possible. As a default, you'll see '????' if DisKey isn't sure. Disk types: - DOS : Old Filing System - FFS : Fast Filing System - KICK : A1000 Kickstart Disk Block status: - USED \ Depending on BAM - FREE / - KICK : There's no BAM on a Kickstart disk. Block type: - ROOT : Rootblock - BOOT : Bootblock - BAM : Block Allocation Map - BEXT : Extended Block Allocation Table. FFS only. - DATA : Data block. OFS only. - HEADER : File Header Block - DIR : User Directory Block - FILE-LIST : File-List-Block - KICK : Same as above. 2.7 The sector selection box - DRV : Corresponds to the entries in the menu 'DEVICE'. 0 is the first device in that list, usually DF0:. - BLK : Absolute sector number, measured in offset to the first block on the media. - TRK : Absolute track number. Don't confuse this with: - CYL : Cylinder number. Depending on the type of media, a cylinder has one or more tracks. With 3 1/2" disks, each cylinder has two tracks. - SEC : Physical sector number on track. - HEAD : Number of head. As mentioned above, you can enter any value you like after clicking on the name of the value, not on the value itself. Each of the gadgets can be put in decimal or hexadecimal mode: If you want to enter a hexadecimal value, precede your entry by typing a '$'. The value will then be displayed in the color of the borders. To switch to decimal notation, enter a '!'. 3.0 Operating DisKey This section will provide you with a quick overview of the different functions of DisKey. Please note that DisKey distinguishes between left and right Amiga keys! So the shortcut description 'LAmiga-N' spells out as 'Press the Key n while also pressing the Left Amiga qualifier key'. 3.1 The Project menu 3.1.1 Read Block -l Reads the sector specified in the sector selection boxes. The difference between BLK and SEC there is that BLK is the absolute sector number measuread as a offset to the first sector on that device, while SEC is the number of the sector on the currently active track. As the new block is always read in whenever you cahnge the settings in the selection box, you'll propably only need this to re-read a sector. 3.1.2 Write Block -w Writes the current sector back to disk. If the action was completed successfully, DisKey will change the color of the highlighted changes to the sector. Until you read or write a block again, you can still undo these changes. 3.1.3 Print Block -d Prints the selected block like 'TYPE HEX' would print a file. You can specify a redirection file by selecting 'Printer Output' in 'DisKey.prefs'. 3.1.4 Open Capture -a Opens a capture file on the RAM:disk or any other path you choose to specify in 'DisKey.prefs'. To generate unique filenames for multiple writes, DisKey appends a number to the name you specified. The capture is quite useful for salvaging data from damaged disks. 3.1.5 Close Capture -z Closes the capture file. This happens automagically (Hi, Bill Hawes B^) whenever you open a new capture, or when you leave DisKey. 3.1.6 Whole blk -> Cap -y Writes the complete current sector to the currently opened capture file. Especially useful for bootblocks and the like, where every byte counts. 3.1.7 Data only -> Cap -x If the current sector was identified as data block, the data contained in that block minus any filing-system information is written to the capture. 3.1.8 Salvage -> Cap Writes the current OFS data block and all subsequently connected sectors to the capture. If selected in an fileheader block, DisKey will try to salvage each block to a capture file: If errors occur during this operation, the fragments will be put in several capture files. 3.1.9 Cap -> Whole blk -Y Inserts the contents of a file in the sector editor. Use 'write block' to write the changed sector back to disk. Specify 1 as offset. 3.1.10 Cap -> Data only -X Depending on FFS or OFS, 512 or 488 bytes are copied to the sector editor. In OFS data blocks, existing pointers will not be changed. 3.1.11 About DisKey -I This will display some information on the disk and the version of DisKey you're currently using. 3.1.12 Get Info on block -i Interprets the longword in the hex display below the cursor as sector offset. If it is a valid sector number, information on this sector will be displayed. If selected from the menu, it will subsequentially let you select a longword which should be interpreted as pointer. 3.1.13 Quit DisKey -e Leaves DisKey, closes open capture files, and frees any inhibited drive. 3.2 The Block Sel menu 3.2.1 Jump to Block -s Reads the sector which is specified by the longword that is just below the cursor in the hex display. Same rules as with 'Block info' [3.1.12] 3.2.2 Read Rootblock -r Reads the root block of the currently active device. 3.2.3 Read Bootblock -b Reads the boot block of the currently active device. 3.2.4 Read BAM -a Reads the bitmap block of the currently active device. 3.2.5 Read Next Block -f Reads starting from an Fileheader the next sector. In OFS, this can also be used to jump from one block to the next, since they are linked. In FFS, this is just now not possible. 3.2.6 Read Previous Block -v Only with OFS: Jumps to the previous block. Since this depends on the fileheader, he has to be present for this feature to work. 3.2.7 Read List Block -l Jumps starting from a fileheader to the subsequent list blocks, if there are any. 3.2.8 Header Block -h Jumps back to the fileheader, if you're currently in a list or data block: under FFS, this works only in list blocks. 3.2.9 Parent-Block -p Jumps up one level in the directory hierarchy of the disk: In fileheader blocks, this will read in the directory block, and in directory blocks it will read the parent directory, or the root block, depending on your position in the hierarchy. 3.2.10 Undo Read/Jump Will jump back to the block you've read in before you executed the jump/read. 3.3 The Extras Menu 3.3.1 Memorize Block -m Copies the current sector to an internal buffer for subsequent use. 3.3.2 Recall Block -h Recalls a previously memorized block, and writes it to the edit window. Use memorize and Recall to copy sectors! 3.3.3 Calc Checksums -s DisKey calculates the checksum for the current sector, depending on it's type. In block 512 of a kickstart disk, this will calculate a KickChecksum. 3.3.4 Search for -S Opens a search window, where you can specify what you want to search. To continue a search, just click longer on the item in the select box, or keep -S depressed, like you were overriding the safety catch. Clicking into the search window will abandon a search in progress. The search supports also some special condition code, which must be entered in ASCII search mode in the following order: \ObjectType\Specification\Object where ObjectType can be: - Header: Search for file- or directory headers. - Parent: Search for corresponding file- or directory blocks. - Data: Search for data blocks only. OFS only. - List: Search for list blocks only. and Specification either - Name: The object is a file- or directory name. - Key: The object is entered as a hexadecimal sector offset. Examples \parent\name\DisKey ... searches for all files that are connected to a directory called 'DisKey'. \parent\key\370 ... searches all files and directories just below the root level of the directory hierarchy. ($370=880; root block on disks) \header\name\DMouse ... searches for all fileheaders of files that are named 'DMouse'. \header ... searches for all headers. 3.3.5 Format -f Opens the Format window, where you can specifiy a start and an end track. The sectors on the tracks to be formatted will be filled with #$00. Due to the limitations of DOS, DisKey can not check whether the format was successul. This is the reason for 'CheckDisk'. 3.3.6 Reformat -r Opens the Reformat window, where you can select the number of trials, and starting and end track. Reformat first tries to read a track. After that, the track is formatted and written back to the disk. If an error occurs while reading, DisKey tries to use Rawread to read each sector by itself. Due to the limitations of DOS (*), a Reformat may fail totally, so that you should only do it on backups of your corrupted disks. (*) A track might look perfectly normal and readable. And yet there is the chance that a media failure lurks somewhere in the gap between last an first sector of the track. This means that DOS can successfully read a track, but on writing back, the chance is high that the data is written over the bad zone, which results in an error. Copying your disks with TurboBackup (c) Martin Kopp & Steffen Stempel insures you effectively against this risk, since it also checks the gaps when copying a disk. 3.3.7 Disassembler -w Opens the disassembler window. The whole contents of the current sector are displayed as MC 680x0 mnemonics. Using the items of the menu "Defaults", you can change the format of the listing. As long as the full-block disassembler is running, you may not issue commands to DisKey. This needs both the Req.Library and the Dis.library. 3.3.8 -F Fills the current sector in the edit screen with a byte or a pattern ofyour choice. 3.3.9 Fileheader -f Lets you enter a filename of the fileheader to which you want to jump. 3.3.10 Format Quick -i Writes new Root-, Boot- and Bitmap blocks to the currently active disk, effectively ereasing the data contained therein. Corresponds to the 'Format Quick' command of AmigaDOS. With this option you can install previously formatted disks. 3.3.11 Checkdisk -p Checks disks for errors. You may specify start- and endtracks to limit the search. 3.3.12 Mark as Free -j Marks the current sector as 'Free' in the BAM: This means he can be overwritten and deleted by DOS. 3.3.13 Mark as Used -u This marks the current block as 'Used' in the BAM; it will not be overwritten by DOS. But pay attention: Whenever DOS validates this disk, all blocks marked as 'used' which do not belong to a file will be freed again. 3.4 The Devices menu This lets you select on which device you want to work. The shareware version shows you a list of possible devices, but lets you only work with the disk drives. Selecting a harddisk will effectively call up an requestor which tells you that this is only possible if you use DisKey professional. 3.5 The About menu You figure it out yourself. The information contained below "Translated By" is no longer correct, since I've left the University of Karlsruhe in the meantime. The bitnet- and Internet adresses are therefore no longer valid. My fidonet number has also changed: It's now 2:241/7501.5. If luck is with me, you can get me in a few weeks' time (about Jun-91) as tom@armchair.ka.sub.org on UUCP. The physical address hasn't changed. Send Disk-Change (Kein Shortcut) Sendet ein Diskchange an das gerade aktive Device. 3.6 The DisKey.prefs menu This lets you change some of the defaults of DisKey. The different options will be discussed in 4.1.n. 3.7 The Tools menu 3.7.1 New Devicelist This creates a new internal devicelist for DisKey. Useful if you have first started DisKey, and then mounted a new device. Using this function will make the newly mounted device accessible to DisKey. 3.7.2 Send Diskchange Sends a diskchange to the currently used device. Necessary for some changes to take place. 3.8 Additional shortcuts In addition to the sector selector, DisKey offers also another method to cahnge the current sector: The combination --b will load the next physical block, while --b will load the previous physical block. -b will act just as if you had clicked on the 'BLK' gadget. It works just the same for tracks ...-t, drives ...-d, heads ...-h, sectors ...-s and cylinders ...-c. Be sure to press the qualifier keys before you select the character key: If you do it the other way round, DisKey might misinterpret your command. - will switch you to hex edit mode, while - will put you in ASCI edit mode. 4.0 The DisKey preferences file During startup, DisKey tries to read its defaults from the file DisKey.prefs, which must be located in either ther current or the S: directory. If you start DisKey from a CLI, you may also give the path and name of the configuration file to use as an argument. Each valid entry starts with a keyword which must start in the first row. The Keyword is followed by an '=', and after that the value. The settings marked with an (*) can be changed from the 'DisKey.prefs' menu. 4.1.1 BAMChange = [TRUE|FALSE] (*) If set TRUE, AmigaDOS will be notified of every change in the BAM. Useful only if you have not inhibited the device you're working on. In this case, it keeps DOS from writing over sectors which you've just allocated. 4.1.2 BASE = [0|1] (*) Sets the base of the offsets to be used. 4.1.3 COLOR = Lets you define your custom colors for DisKey. n is in the range of 0 to 3. The rgb value is a three digit hex number. To set the background color to black, use the DisKey.prefs entry "COLOR0=000". 4.1.4 CURSORDELAY = Sets the delay in n/50 th seconds, before the currently pressed key is repeated. May be in the range of 0 to 99, while none of the extreme values makes any sense. 4.1.5 CURSORSPEED = Waits n/50th of a second between cursor movements. 4.1.6 DC.W = [TRUE|FALSE] Sets the disassembler display mode to use the dc.w notation for undecodeable data. 4.1.7 DRIVE = [|] Selects the device which should be used during startup. 4.1.8 EDMODE = [ASCII|HEX] Sets the editor mode in which DisKey is set after startup. 4.1.9 ICONX= Sets the X position of DisKey's Iconify Icon. 4.1.10 ICONY= Sets the Y position of DisKey's Iconify Icon. 4.1.11 INHIBIT = [TRUE|FALSE] (*) If true, DisKey inhibits the drive it is currently working on. This prevents DOS from stumbling over your feet. As long as a drive is inhibited, you cannot write from another task to it. Useful if you want to resurrect a disk that has been damaged so badly, that it crashes the machine whenever you insert it. 4.1.12 KEY = Lets you define a new set of hotkeys for the menu n. You have to define all hotkeys of a certain menue in one go. You do this by entering a two character combination for each hotkey, starting with the definition of the first entry in the menu. The first character is either 'R', 'L' or 'C' and denotes whether you should press the Right or the Left Amiga key, or even CTRL-Left-Amiga Key as qualifier to execute the hotkey. The second character is the hotkey that should be used. Please remember that the second character is case-sensitive! 4.1.13 SAFETYCATCH = [TRUE|FALSE] (*) This toggles the safety catch. Leave it on for your own good. 4.1.14 LACE = [TRUE|FALSE] Switches the Interlace mode, as required with NTSC machines. 4.1.15 LANGUAGE = [DEUTSCH|ENGLISH] Selects the default language. 4.1.16 OFFSET = [HEX|DEC] Selects the mode in which offsets are displayed within the disassembler. 4.1.17 PRINTFILE = # (*) Defines a device or file to which all printer output is sent. 4.1.18 PRINTINFO = [TRUE|FALSE] (*) Decides wheter you want a header to go with your printout. 4.1.19 RAWREAD = [TRUE|FALSE] (*) Enables the use of RAWREAD for checking the bootblock, or reading defective tracks. Leave this false if you know that Rawread doesn't work with your setup. 4.1.20 REQUESTER = [TRUE|FALSE] Enables the use of the requester for user interaction. To use this feature, you'll have to install Bruce Dawson's Req.library. 4.1.21 RETTEN = # (*) Defines the current path to be used for the capture files. 4.1.22 SCREEN = [Workbench|Custom] Defines the screen on which DisKey is opened. Running DisKey on the workbenh conservers memory, but also covers up the complete workbench. On a NTSC machine, you might not be able to run DisKey in WB mode, if your workbench isn't in interlace mode. 4.1.23 SETPREFS = [TRUE|FALSE] Fixes an incompatibility to MachII: If you're using MachII, make sure that SetPrefs=False. 4.1.24 SHOWNULL = [TRUE|FALSE] (*) When true, DisKey checks after each diskchange for known viri. 4.2 The defaults BAMCHANGE = TRUE BASE = 1 COLOR0 = 339 COLOR1 = 0FF COLOR2 = 000 COLOR3 = C71 CURSORDELAY = 15 CURSORSPEED = 2 DC.W=TRUE DRIVE = 0 EDMODE = ASCII ICONX=50 ICONY=50 INHIBIT = FALSE KEY1=RlRwRdLaLzLyLxLrLYLXRIRiRe KEY2=CsCrCbCaCfCvClChCpCe KEY3=RmRhRsRSRfRrLwLFLfLiLpLjLu KEY4=R0R1R2R3R4R5R6R7R8R9L0L1L2L3L4L5L6L7L8L9 KINDERSICHERUNG = TRUE LACE = FALSE PRINTINFO = TRUE PRINTFILE = PRT:# RAWREAD = FALSE RETTEN = RAM:# SCREEN = CUSTOM SETPREFS = TRUE SHOWNULL = TRUE 5.0 Greetings / Thanks / Kudos - A sincere 'thank you Ma'm' to Angela, who just gives her best to keep her brainchild up to date. - The author sends a 'Howdy, boys' to all Internet Relay Chatters out there: You all know this is the final frontier of telecommunication, where men are still men, and not only stickers. B^) In particular, the greetings are to those who meet regularly in the Amiga! channel: Top, Stefanb, ZZAcht, Mlelstev, Pythagoras, Franky, and many more. See you there! - Many thanks to the guys at Commodore-Amiga: You've really made it worthwile! - 'Bill' Hawes: ARexx and WShell are just great! Keep it up! - With love to my girlfriend Jutta, who did part of the proof reading, and who sustained me in the hours of need.