.LM 8;RM 72;CE 3 FUNNELWEB Vn 4.40 DISKREVIEW ---------------------------- .FI (1) INTRODUCTION ~~~ ~~~~~~~~~~~~ DISKREVIEW (program files DR/DS or as DR40/DR41) integrates with the FUNNELWEB Vn 4.40 system an extensive set of disk snd file utilities. It features an enhanced Directory function like that in the FUNNELWEB Editors. In addition it provides all file marking functions of the FUNNELWEB QD, most disk manager functions needed in normal usage, a sector editor with string search over individual files, an alternative interface to the FUNNELWEB main menu, and complete access to the FUNNELWEB file loader system from the cursor bar in the directory display. In addition an Extended Basic program loader handles both Program and I/V254 formats. The View function supports full bi-directional scrolling within a circular buffer of 8 Kbyte size, and printing out from the buffer of the Viewed file. The program is fully compatible with 80-track disks using the Myarc FDC with appropriate DSR ROM, or Myarc HFDC (but this device appears to have serious bugs in its 80-track file copy DSR routines). Every effort has been made to keep the program insensitive to the various incompatibilities of the Geneve 9640 with the 99/4a. This file is continued in FWDOC/DR41. (2) LOADING ------------ It is installed permanently as Option #8 on the FUNNELWEB E/A Central Menu screen as DISKREVIEW, filename DR, with an Option 1 (Text-Mode TI-Wr) load path forcing C1 load to refresh the TI-Writer control character patterns. DR can be loaded as an Option #2 (GPL) file if desired from another Central Menu or User List entry. It calls on FUNNELWEB internal routines which means it will crash if you load it from E/A 5. Screen colors are set up as for entry to the Editors from the FUNNELWEB main menu. See FWDOC/LOAD for discussion of initial auto-loading options. (3) PRINT FUNCTIONS ------------------- All print functions use as default the FUNNELWEB print device as installed or edited for use by the Editor PF function in the main program. No provision is made in the program for explicit control sequences to be sent for setting up the printer, but these are easily handled by using separate short files containing the necessary codes and printing these from View before and/or after printing other files or directories. All or marked parts of Display files of any record length may be printed, with original record lengths preserved. As the print device name can be edited to be a disk file this gives a limited file copy function for the whole or selected parts of Display files to a target device with general pathname. (4) DIRECTORY ------------- When DISKREVIEW first runs it shows a screen with information block, command reminders, and window for alternative menus or directory paging. A plain pop-out window in the lower center of the screen is used for user input, progress reports, and error messages. All low-level disk accesses, other than the Myarc FDC direct formatting, use standard DSR sector access or other DSR subprograms which require a unit number entered in the form DSKx., with the character "x" being in the range 1-9. If your choice can't be found then the error trapping will tell you. When q disk directory is read, program file checking is done automatically. The disk/file information block shows the usual disk and drive details. The block of filenames shows certain filenames of recognized types which may be altered by marking. .LM+3;RM-3 WF :- the current FUNNELWEB workfile DV/80 or DF/80 display file as would come up for Editor LF/SF etc. OF :- the current FUNNELWEB DF/80 object filename as appears as default for the file loading options. PF :- the current FUNNELWEB assembly program file name as appears for program filename default. .LM-3;RM+3 On entry to DISKREVIEW the current filenames are read and displayed, and on exit the names showing are installed as defaults for FUNNELWEB. (5) KEY COMMAND FUNCTIONS ------------------------- When DR first loads the left side key advice panel shows a number of alternatives. This screen is also reached by or from the directory screen ( is either or throughout DR). All key entries are automatically converted to upper case except where lower case might be needed as in ASCII search string entry. .LM+3;RM-3 <1-9> keys. The directory is read from the disk in the indicated drive and displayed in the right side box. After the directory has been read in, DR will flash up a "Check programs" message and continue accessing the disk to check details of any program files. (Break) terminates the process. The entries written up in the file box are not erased immediately, but are otherwise ignored by the program. <0> key. As in FUNNELWEB this cycles the screen color choices. Also available on other directory screens. key. This brings up a menu of disk oriented functions in the right box. See FWDOC/DR41 for more details. key. The current FUNNELWEB Central Menu entries are presented in two blocks. Selection is by reversible marker with using . key. Returns to FUNNELWEB from any screen where it is active, or Switch to the Disk Utility screen unless a valid directory is present to be resumed. or keys. Returns to valid directory display if present. .LM-3;RM+3 A variety of key functions is available after the directory has been read into memory, and a reminder of these is given in the column down the left hand side of the screen. Some keys function only after a file has been read into the View buffer. Individual file oriented disk manager functions are executed from this directory display, and others after tagging a set of files. Delete works only on tagged files as an extra layer of caution. Entry to the sector editor is also from this screen, as many of its functions are file related. .LM+3;RM-3 key. The usual REDO key does just that and re-reads the directory from the same drive. key. Returns to the initial selection screen. , keys. These provide the from error conditions, or to go back to an existing directory from the drive selection screen. and keys. These move the cursor marker up and down the directory, paging it as necessary. and keys. or pages the directory display towards higher numbered pages, and or pages back towards the start of the directory. key. This checks the type of file currently marked by the cursor. The filename will appear as qppropriate in one or more of the block of filenames in the lower right block. key. ldfile restores the various marked filenames to those in force when DISKREVIEW was invoked. and keys. ag the file under the cursor bar, to leave a visible marker in the center column. Use to tag all files, The total size of tagged files is indicated as sectors allocated at the bottom of the file-size column. and keys. ntag the file under cursor. Untag all files with . key. Several ctions on ll tagged files are available from a new command set which appears in the key advice block. Details are in the next section. key. unProgram sends the marked filename to the appropriate FUNNELWEB loader or to a internal XB loader. Details are discussed more fully in a later section. key Allows the file under the cursor to be renamed. Edit the name as presented and . The directory will be re-read to verify the change. key. Allows copying of any single file at a time from the directory drive to another drive or to the same disk under another name. The target drive number and target file name are edited and on the disk number is checked in the range [1..9]. Disk swapping in a single drive is prompted if drive number and filename of the target file are the same as for the source file. Copy uses the disk DSR direct file input and output subprograms which must be supported by the disk or RAMdisk DSR to TI specifications. Copy buffer size is 46 sectors. key. Allows viewing of ALL file types of any record length to the screen. The first page of the display is presented and it then halts for further instructions. See View/Print for more details. key. Similar effect to except that the display continues in line scrolling until a further key is pressed. key. Inspect and edit sectors. See FWDOC/DR41 for details.

key.

rintDirectory causes the current directory to be printed out to the FUNNELWEB print device (as transferred to the Editor as Editor PF device). The print device name may be edited but is used only within DISKREVIEW. The device is opened in APPEND mode. .LM-3;RM+3 (6) TAGGED FILE OPERATIONS -------------------------- Several file operations are performed on the selection of files tagged in the previous screen. .LM+3;RM-3 key. opies all tagged files to another drive under their existing names. A list of up to eight drive numbers may be specified, and each tagged file is copied to the listed drives in turn. To stop the copy process hold down BREAK which is checked after each file is completely copied. Single drive copying is not supported under file tagging, only for single file copies with . If for any reason a file is left incompletely copied, its directory entry should be deleted from the target disk. keys. nProtect or

rotect on all tagged files. The directory is re-read so that the result can be verified. key. eletes previously tagged unprotected files from the disk. You are asked if verification is needed for each file and if "Y" the tagged filenames are presented one by one for deletion. The directory is re-read after all tagged files are deleted or taken. A bloop will sound if the delete fails, which should remind you to check disk or file protection. If you delete the wrong file, IMMEDIATELY use the file recovery procedure from the Disk Utility menu. key. The DSKU disk manager program by the late John Birdwell allowed annotation of individual files, but in a way not recognized by DSR operations. These notes are destroyed by the normal file by file copy process. If otes is pressed the tagged files are examined for DSKU type annotations and these are transferred to the files of the same names on the target disk. No provision is made for entering or editing these directly. See DSKU Notes at the end of FWDOC/DR41 for technical details and how to use the sector editor to create these. keys. These page the directory to allow checking of what has been tagged. keys. These force the display back to the normal directory commands before scrolling the cursor. .LM-3;RM+3 (7) PROGRAM LOADERS ------------------- The Run Program option gives access to the FUNNELWEB loading system directly from the directory display. As far as it can DISKREVIEW checks the type of program file before selecting the appropriate loader and then offers sub-choices corresponding to the various FUNNELWEB Loaders screen choices. Once the load decision is taken for the assembly load path you are back in the FUNNELWEB environment. .LM+3;RM-3 o Object files Any DF/80 file presented is assumed to be an E/A object file. An object file may be a file normally loadable by FUNNELWEB, a special file that uses the Low-Loader option to load in low memory over the usual E/A utilities, or finally an auto-starting file that does not need to return to the loader. Any other DF files are ignored. o Text Files If a DV/80 file is selected the loader gives a warning message, and if you elect to continue treats it as a FUNNELWEB Script file for loading and linking one or more (up to 15) object files. All other DV files are ignored. o Extended Basic programs If the initial check of program file headers has determined that the marked file is a program with a Basic/XB compatible file header, or else an IV/254 file is selected, then DISKREVIEW checks if a TI XB module is present and uses an interrupt driven loader to start XB and load the nominated file. Because absolute GROM addresses are used this may not work with other variants of XB (not available here for testing purposes) Reports are that Triton Super-XB works fine, but most definitely not Myarc XBII. For these you will just have to do it by hand or else use the XB User List in FUNNELWEB LOAD which should work with all known XB variations, as it is invoked as a program statement from within a running XB program. o Program files If the program file has been identified as E/A compatible it will be passed to the FUNNELWEB Loaders with choices presented as for Options 1-3, of which 2 GPL is the normal selection, corresponding to E/A 5. See FWDOC/EASM for details. If the program file is not a recognised E/A type a warning is given. Files of this kind that are executable as assembly program files usually load into cartridge RAM, or else are extra long files prepared with FWSAVE. .LM-3;RM+3 (8) VIEW/PRINT FILES -------------------- The View file function presents Display or Internal files, of any fixed or variable record length, on the screen as an ASCII character display. This may not be very relevant or readable for Internal files where bytes are usually in an internal machine representation (many Display files, usually Dis/Fix 128, may also be found to contain other than the normally readable ASCII characters), and the sector display will be more useful for these. Program files are written to the screen in lines showing 8 bytes at a time, both as ASCII characters and as hexadecimal bytes grouped as 4 words, but the size of program file fully displayable is limited to about 46 sectors. The file display in 40 cols may be scrolled by line or page, either by single key or auto-repeat in either direction. Once a record has been read in from disk it is stored to a buffer in low-mem and subsequent access to that record is from the buffer. If a file exceeds the buffer limit of 8K the display halts for user input. If is pressed the display returns to record #1, but any other key causes it to go into circular mode where early records are progressively erased to make room for later ones. This is indicated by CIRC appearing followed by the new starting record number. Only one file is accepted into the buffer at any time. Once a file has been read into the buffer all or selectable part of the buffer contents may be printed to the FUNNELWEB print device in Append mode after editing of its current default name. The display is updated in units of a file record which may occupy up to 7 display lines. For program files the unit is a line displaying 8 bytes. Trailing blanks are ignored. The status line keeps track of the numbers of the first and last records visible on screen at any time. The second number will vary rapidly during scrolling. After EoF the number of the last record read from disk is also indicated. The next set of keys controls the View of the file active in the View screen. The print option is available for whatever part of a file is in the buffer. .LM+3;RM-3 and keys. Pressing causes the display to scroll one record towards the end of the file, getting it from low-mem buffer or from disk as needed. sets up a continuous line scroll to the end of the file. and keys. Pressing causes the display to scroll one record towards the start of the file, getting records from low-mem buffer. starts a continuous scroll back to the start of the document. keys. Scroll the display one page towards the end of the file. keys. Pressing causes the display to scroll continuously one page at a time towards the end of the file, getting records from VDP buffer or disk as needed. This is a bit faster than line auto-scroll since less screen updating needs to be done. and keys. Scroll or start auto-scroll of one page back towards the start of the file. . The space bar temporarily suspends auto-scrolling while held down, or if not auto-scrolling it causes the last manual scroll operation to be repeated. . To cancel auto-scroll hit just about any key not given a special function. If you have the display stopped just where you want it with the space bar, press another key before releasing the space bar. key. Moves the display to the start of the file. key. Moves the display to the finish of the file. keys. At any stage each of these sets a marker at the line at the top of the screen. They are all initialized to the start of the file when a new file is read from disk. Marker 5 is always set to the last record in buffer as it is read in from disk until it is specifically reassigned. In Circular mode markers are set to the start of the file in buffer as they are overtaken. <1-5> keys. At any stage these keys return the display to the previously defined marker. .LM-3;RM+3 When a file has been partially or completely read into a buffer, a new command key becomes available for use, for print. .LM+3;RM-3 key. The current file is printed out from the record at marker #1 to the last record before marker #5. This allows parts of a file to be printed out as specified by editing the print device name which may be a disk file or complete pathname . .LM-3;RM+3 .LM 8;RM 72;CE 7 FUNNELWEB Vn 4.40 DISKREVIEW ---------------------------- Part 2 - Disk snd Sector Utilities ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .FI (1) DISK UTILITIES ------------------ The Disk Utilities menu is reached from the entry screen by pressing (or also if no valid directory is present). The menu appears in the box normally devoted to the directory display. Keys and or drive the scroll bar up or down with wraparound and selection is by the key. The ones provided have been found useful here, and there is room for a few more suggestions. .LM+3;RM-3 o FORMAT DISK -------------- FORMAT first requests the number of the drive in which a disk is to be formatted. Cautionary reminders are issued as a checkpoint, as formatting has irreversible destructive effects once started. Then you are prompted for the number of sides (S or D), the density (S,D, or Q for 80-tk drives). may be used at any time to back out. Your disk controller and drives of course must be capable of the options chosen. Before formatting is started you are asked if validation is desired after formatting is complete. It is normal and good practice to do this quick but not thorough validation of the newly formatted disk (by reading all sectors). The sector allocation bitmap will be updated to mark the bad sectors, but disks are now cheap enough that it is false economy to use a disk that formats with faulty sectors. Normally the disk controller DSR subprogram is used to format the disk. Myarc floppy disk controllers with the original 40-Track DSR ROM will format 16 sectors per track this way in double density. DISKREVIEW does NOT allow for this and always writes a disk header showing the normal 18 sectors per track. See the final section on User Defined Flags for details. Myarc FDCs with 80-Tk ROMs appear to default to 18 sector format. o VALIDATE DISK --------------- This function is invoked either directly from the Disk Utilities menu or else as a follow-on from Format Disk. It attempts to read all sectors on the disk, from #0 up to the maximum indicated in the disk header (Volume Information Block). The information window shows a running decimal count of the sector being read, the last bad sector encountered if any, and the number of bad sectors if any. The (Break) key is checked before each new sector is accessed, and if pressed it terminates the process, If there are bad sectors you are asked if these should be marked as used in the VIB bitmap. Normally a disk showing bad sectors should be treated with great suspicion. Save the files on it as desired or possible and reformat it to check whether the errors are permanent. Even if it seems good then, it should be put aside for a while and then re-validated. More sophisticated programs such as DISKHACKER can give more detailed diagnostics. o RENAME DISK ------------- This one is so simple it hardly needs description. On selection of drive #, the current diskname is shown and also presented as default for the new name. o SWEEP DISK ------------ This removes all directory references to files on the disk and rewrites the disk headers to look like a freshly initialized disk. The files are not physically erased, and if despite the checkpoint a ghastly error is made, then immediately use the file recovery procedure. The bitmap is just rewritten without reference to the rest of the disk, so the disk should be re-Validated if there is any suspicion of its condition. When the drive # is entered the disk volume name is read and shown with cautionary messages. If you you will be returned to the Disk Utilities menu after the necessary disk activity. o RECOVER FILE -------------- File recovery after Delete or Sweep Disk is possible if no subsequent write operations have been made to the disk. Bring up the Directory of the disk before entering this option. The filename to be recovered is requested. After entry the current directory is checked to see if it is already present, and then a search of currently unused sectors is made to find the name. If and when this is found the file cluster map is checked first for possible corruption against the disk bitmap before restoring the file. It may be that a file descriptor record left over from previous sweepings or deletes is located and processed. To guard against this each recovered file should be checked out before proceeding to the next, and deleted again if found to be corrupted. o MYARC RAMdisk Utilities ------------------------- The CALL PART initializing and CALL EMDK drive number setting utilities are supported by means of DSR subprogram access. The only absolute address used is for reading the current EMDK for display, and nothing is written to the RD other than by the CALLs. No range checking is currently done on the number entered for EMDK. No screen editing provisions are currently made to get other than CALL PART(400,80), but enough room has been left in the program that any CALL PART may be installed with the sector editor. Fairware contributors may write for details of how to go about it. o HORIZON RAMdisk Utilities --------------------------- The DN and AO/AF subprograms are supported in the form prescribed in the Horizon/OPA Vn 8.14 ROS docs. Disk number change is in the form CALL DN.o.n where "o" is the existing old disk number and "n" is the intended new number. No explicit range or checking is currently done on the entries. CALL AO.x or AF.x turn auto-booting on or off respectively. The ".x" extension is optional if only the first HRD is to be switched. o QUEST RAMdisk AON/F --------------------- The AON and AOF CALLs are provided for the HV99 Quest 512 RAMdisk. .LM-3;RM+3 (2) SECTOR and SEARCH UTILITIES ------------------------------- The Sector Utilities are invoked by nspect Sector from the Directory screen. Selection from the menu that appears in the message window is either by number or the first letter of the corresponding entry. Editing by absolute sector or offset into a file is supported. String search is either by file offset or absolute sector, for either ASCII or HEX byte strings. A wild character or wild byte may be set in the search string. Auto string replace is not supported. .LM+3;RM-3 <1/S> keys. Lead directly to the sector editor which appears on the sector display screen, <2/F> keys. Enable a string search in the file currently marked by the cursor in the directory, and string entry follows. <3/D> keys. String search is now by absolute sector number. See the later String Seardh section in this file. keys. Force the display back to the normal directory commands before scrolling the cursor. .LM-3;RM+3 o SECTOR EDIT ------------- On selection of Sector Edit a new screen appears, with a menu of 5 choices appearing in the box at upper right. The current file under the cursor is written up as a reminder. Select by number or initial letter of the option name. .LM+3;RM-3 <1/F> keys. Present for editing the File Descriptor Record for the current file under the cursor. Absolute mode is set. <2/O> keys. Set up editing of the sectors within the current file. The desired offset is entered as a 3 digit hex number starting from zero for the first sector. The maximum offset is shown for guidance. When a sector is displayed in file offset mode both the file offset and absolute sector are indicated. <3/A> keys. The absolute sector number is then entered in 3 digit hex form before the sector is read. .LM-3;RM+3 The chosen sector is presented in ASCII or hexadecimal form in 16 lines of 16 bytes in the upper box. Toggle between these with the and (or ) keys. A short reminder for the editing keys is given in the lower left block, and these follow J. Birdwell's DSKU in the interests of standardization. The accelerating auto-repeating flashing cursor appears either in the Hex or the ASCII display modes depending on the entry path. When an entry is altered in either display the corresponding change is marked by reverse video. The HEX display accepts only hex digits for editing. A running count of cursor position in hex is displayed, along with the byte under the cursor. .LM+3;RM-3 and keys. Drive the cursor up or down a line with wrap-around. and keys. Drive the cursor along a line with wrap-around at sector start and end. key. Forces the cursor and entry into ASCII mode. keys. Force the cursor and entry into HEX mode. The cursor will start at the most significant nybble of the current byte. key. When a sector is read in a spare copy is made. This restores the riginal version to undo editing changes. key. akes the currently displayed abd edited sector over as the reserve copy. key. ecalls the reserve sector copy to the edit windows. The keys make it possible to transfer sectors from one place to another. key. Moves to the ext sector. In absolute mode this is numerically the next. In file offset mode this is the next sector in the file and may skip about over the disk in absolute sector equivalent if the file is fractured (indicated by the asterisk in the directory display). key. Moves ack a sector on the disk or in the current file. key. rites the sector back to disk at the current sector number on the current disk, after first asking for confirmation. Remember - careless use can destroy your files. .LM-3;RM+3 STRING SEARCH ------------- When a string search option is selected a choice is presented for ASCII or Hex string entry. Each entry mode allows specification of a wild card. For ASCII entry this has "?" as the original default, and for HEX search this is byte >00. When the wild-card is entered all occurrences pf the previous wild-card in the search string are changed to the new value. The string is 8 characters or bytes long, and if you do not use the full length, leave the trailing part as the wild-card. Trailing wild-cards are eliminated from the search to speed it up. The function of a wild-card character in a string search is to flag a character or byte of the string to be ignored in making comparisons in the search so that as long as the other bytes match that one in the sector can be anything. In disk search (absolute) mode the start sector for the search is requested. The search may be terminated at any time by pressing BREAK. File search shows both file offset and absolute sector numbers as the search proceeds. The HEX search mode allows the search to be forced to even word boundaries. This cuts down on the number of falss alarms when looking for instruction opcodes or word data in E/A programs. When a match is found in a sector the display switches to the sector edit screen with all occurrences of the matching string highlighted in reverse video. .LM+3;RM-3 <1/C> key. Return to directory screen and ontinue search. <2/E> key. Transfer to dit mode in either ASCII or HEX and absolute or file offset mode as appropriate. The cursor appears at the first occurrence of the search string. Editing then proceeds as normal. <3/Q> key. Just uit the search. .LM-3;RM+3 After going to dit during string search returns to a further selection. .LM+3;RM-3 <1/C> key. Continues search at sector after the one last found before going to dit, either by file or absolute. <2/R> key. Restarts the search from the start, with the existing string as default. <3/A> key. Abandon the string search function. .LM-3;RM+3 User Defined Flag Patch Notes ----------------------------- Several flag or parameter settings are included just after the start of the DR file following the 3 word file header and the initial B @@>xxxx instruction. By byte offset these are .LM+3;RM-3 >0A -- If you are using a Myarc FDC with 40-Tk DSR ROM, you MUST indicate its presence by setting this word to >FFFF, and >0000 otherwise. >FFFF here will flag Format to use a special direct access 18 sector per track routine for DD formatting. >0C -- If you have a TI or CorComp or equivalent disk controller set this to >FFFF to bypass some extra disk activity needed by controllers (mostly Myarc) that need to read the VIB of the current disk for correct sector addressing. The universal value is >0000 for distribution purposes. >0E -- Reserved for future use. >10 -- GROM entry address for XB loader, >6372 for TI XB Vn 110. >12 -- GROM address GPL stack entry for interrupt loader, normally >63D3. >14 -- GROM address for interrupt loader re-entry, normally >6495. .LM-3;RM+3 80-Track Notes -------------- Files copied to an 80-track disk with over 1600 sectors (usually 2880) will occupy more space than they would on a DSDD or smaller disk. This is because 2 sectors are allocated at a time. A file will appear as either 1 or 2 sectors longer than on DSDD or smaller disks. One sector of these is due to 2 sectors being allocated for the File Descriptor Record, one of which just goes to waste. If the body of the file has an odd number of sectors then the last one will be allocated 2 sectors. As an example 33 sector EA SAVEd program files chew up 34 sectors on DSQD disks and 34 sector files go to 36 sectors. All 80-track disks are indicated as QD even if single density along the track. The ambiguity is resolved by looking at the disk size. DISKREVIEW catalogs 80-track disks according to sector allocations, with file lengths shown being those allocated, and not just those occupied by the file. Copies to normal disks will occupy 1 or 2 sectors less space each. All file copies are done using the DSR Direct File Input/Output subprograms to TI specifications. This is not screamingly fast but sector allocation and de-allocation is entirely handled by the disk controller DSRs. No attempts are made by DISKREVIEW to second guess the controller DSRs. The Myarc FDC with 80-track EPROM was used for development and appears reliable at the DSR level. Reports indicate that the Myarc HFDC is NOT RELIABLE at DSR level for file copy operations with 80-track floppies. Use instead the particular version of the Myarc DM tuned for your HFDC. The Editor SD, or QD show file sizes as their DSDD sizes even on 80-track disks if you need a quick check (sectors used and available numbers are correct however). I am not sure at the moment which is the more useful approach, given that 80-Tk disks are not a common medium of exchange. Please let me know your preference. Bug Note -------- A serious bug has surfaced in the use of DR for one hardware configuration here for which no cure is yet apparent. It has 2 Horizon 192K Ramdisks with ROS Vn 8.14. DISKREVIEW uses the officially defined DSR sub-program access for all functions for which they are provided. Failed DSR sub-program access other than sector access as used for directory reading, such as attempted file copy to a write protected disk, causes subsequent sector access to be captured by the other RDs in the system, and sensible results are obtained only for that RD directory. No harm is done to the other drives, as they no longer are even accessed at DSR subprogram level. Once this has occurred the best solution is to reboot the machine. Return to Funnelweb is not sufficient. The condition does not affect file level access. If a fix is found before an update of ROS 8.1x solves the problem, it will be implemented. DSKU Notes ---------- Many disk libraries use the file annotations created by the DSKUtilities program (by the late John Birdwell). These may now be transferred to the copied files by otes key from the Tagged Files menu. Creation or editing of these will require use of the sector editor. The File Descriptor Record (FDR) of each file on a disk contains the file name, various details of the file, and the map of the sectors occupied by the file in the form of 3 byte groups starting at byte >1A, each describing a contiguous cluster of sectors. Up to 76 such clusters of one or more sectors are possible, but in practice files are rarely found with anywhere near this many fractures. DSKU stores a file comment as ASCII text at the end of this area. This is not a standard TI DSR feature and is not supported by any known DSR. The DSRs navigate the file contents by following the cluster data blocks until a null is found, so if DSR function is to be unimpaired, the clusters must terminate before the comment is reached. If you are not comfortable with sector editing, use DSKU to enter comments and ignore what follows here. To enter or edit the annotation for a file, go to nspect Sectors and select <1> to display the FDR. The comment is entered in the 35 bytes from >DC to >FE leaving the last byte null. If the 3 bytes from >D9 - >DB are not null, DO NOT alter anything or the file will be corrupted. The desired ASCII text may be entered in these 35 bytes, and the sector then written back to disk. In transferring notes DISKREVIEW checks the previous cluster (>D9->DA), and if it is not null on both source and target files, ignores the file. jul / 26 / 1991 Funnelweb Farm