Bug list for DUMPER-32: Priorities: H - High M - Medium L - Low (or restriction) o (L) DUMPER cannot skip backwards on labeled tapes. I haven't been able to figure out how to get the QIO to access the tape by file number to work. It appears to always access the file at the current position or the next file on the tape. Also, I haven't been able to figure out how to prevent the system from rewinding the tape when it hits the end of the tape. The end result of all this is that positioning to a particular saveset is real awkward if you've passed it - you have to rewind the tape and start over (snore). o (L) This feature would depend on getting the problems mentioned in the last item fixed. It would be nice for DUMPER to have a "mode" where it only positions the tape (i.e., does no listing or restore). o (L) Tapes with bad spots on them are a problem. DUMPER-32 tends to just give up when it hits a real bad spot, it would be nice if it could warn the user and try to skip over the bad spot and continue. Currently you have to find your local tape wizard, copy the bits off the tape to a binary disk file, then grunge over that with DUMPER-32, and that doesn't always work (plus it can use enormous amounts of disk space for large savesets). o (L) This is related to the last problem. Currently there isn't much of a way to keep going after DUMPER dies, it wants to to see a saveset header (or at least a continuation header in the IUPUI version) before it will list or restore ANYTHING. It would be nice to have a way to be able to pick up and start restoring anywhere in the middle of a tape, as soon as a file header record is seen for example. o (L) It would be nice if DUMPER-32 could automagically determine the tape format and blocking factor, etc., like the TOPS-20 DUMPER does. See code in TOPS-20 DUMPER.MAC for how to do this. Basically, it just repeats the read of the first block, in- creasing the physical block size, until it either finds something that works (i.e., no data overrun) or runs out of blocking factors (there is a list in the TOPS-20 DUMPER.MAC source of maximum blocking factors for each density). Once the first block is read you can look at it and make a pretty good guess as to the format (interchange, TOPS-10 BACKUP, or TOPS-20 DUMPER). o (L) DUMPER dies horribly when it tries to restore a file whose version number on the tape is greater than 32767 and for an output spec that wildcards the version number with * (the default). The general problem is that DUMPER dies horribly whenever an ACP file create fails for whatever reason. It should probably issue an error message, skip the file, and go on. o (L) DUMPER doesn't overlap reading tape and computing. This would make DUMPER a lot faster, but implementing it would mean major changes to DUMPER_TAPE_IO. Not now. o (L) Some users are complaining that DUMPER is too verbose (like the warning for each EXE file you try to restore). Might want a /NOWARN qualifier or something to keep them happy. Also, the current EXE is linked /NOTRACE because the original was blurting out a trace after every warning message. Need to track this down - fatal errors should be traced, but not warnings.