apple-pascal-1.3-manual

An N response to this prompt returns you to the Filer command level. If yourespond v, the Filer examines the blocks in the specified range andfrequently returns a report something like this:Block 23 may be OKBloc~ 24 may be OKBlock 25 may be OKIn this case the bad blocks are probably fixed. Occasionally, however, thereport may be something like this instead:Block 23 may be OKBlock 24 is badBlock 25 is badFile(s) endangered:THISFILE.TEXT 18 24THATFILE.CODE 25 29Mark bad blocks ? (Files will be removed !) CY/N)In this case the Filer is offering you the option of marking the block( s) itcould not fix. If you respond with v to this question, the Filer first removesall files containing those bad blocks that could not be fixed and thencreates a file on the disk named BAD. BAD exactly covers the bad blocks. Ifthe bad blocks are not contiguous, more than one BAD file will be created.Once this is done, you are advised:&.WarningBad blocks markedand the Filer command line reappears on your screen. On the disk directory,you will find a new entry which saysBAD. !Hl024. BADBlocks in a file marked .BAD will not be used to store any of your files, andwill not be shifted during a Krunch operation. These dangerous areas onyour disk are thus rendered effectively harmless.When you first format or zero a disk, it is a good idea to do a bad-blocks scanso that you can conveniently mark any bad blocks and save yourself a lot oftrouble in the future.A block which has been "fixed" may still contain useless garbage. Themessage MAY BE OK should be translated as "is probably physicallyOK." Examining a block means that the information stored in the block isread into memory, stored again at the same spot, and then read again. Ifboth readings are the same, the block is probably all right physically andis not declared BAD. This says nothing about the information containedin the block.The Filer CommandsIl-69