SAFE Questions and Answers

Author(s): John Oliger
Publication: Update Magazine
Pub Details: Update October 1987
Date: October 1987
Pages: 25

This column will answer questions of general interest about the Oliger 2068 Disk I/F and JLO SAFE DOS. If you have questions you feel other users of this system would like to see answered, send them to me at: 11601 Whidbey Dr. Cumberland, IN 46229. Because my schedule can at times be simply too demanding to always find the time, I cannot promise to ALWAYS have this column ready for each new issue of Safe Disk Up-date. I will only do the best I can…

-John L. Oliger

What is the latest version of SAFE and what new features does it provide?

The current version of SAFE as of today (8/16/87) is V2.34. The last change to SAFE (V2.33 to V2.34) corrected a minor bug in the FOR /n TO m command. The change from V2.32 to V2.33 also corrected a minor bug. The features it added to SAFE (from V2.2) were: 1)A fast new FOR/NEXT loop structure. 2)The ability to save a SCREEN$ via the NMI pushbutton along with all the previous functions by use of this pushbutton.

What does the different numbers represent when referring to SAFE’s version?

The first number (the “2” in V2.34) says that this is the second major version of SAFE. SAFE V1 only supported a total STATE SAVE like V2’s SAVE /”filename” ABS. The second number (the “3” in V2.34) is updated every time a new fuction, command, or group of functions and commands are added to SAFE. When the RESTORE /”filename” TO “newfname” command was added, SAFE’s version number went from V2.01 to V2.10. The last number in SAFE’s version is incremented any time the code in SAFE has been changed or modified, but no new commands or functions were added. This might be done to fix a bug or to make a portion of the code more efficient. An example of this would be when the FOR /n TO m routine was changed to fix a bug, which changed the version of SAFE from V2.32 to V2.33, and another to make it V2.34.

SAFE gives me occasional toots when LOADing, but the programs LOAD O.K. This seems to happen most often with SCREEN$ files. What does this mean?

Anytime SAFE sounds a short toot, it is reporting to you that an error has occurred, it knows it, and it will try again. SAFE will try 5 times to read a particular cylinder on the disk, and give a short toot after each try if an error occurs. If after 5 trys it still cannot read a particular cylinder, SAFE will start the load or save over from the beginning. It will do this up to 3 times (with 5 single cylinder tries) before it will finally just give up and stop with an error report “T” (Disk I/O Error). If you hear some toots while SAFE is trying to SAVE or LOAD, it is simply a report to you that SAFE IS having trouble. If it finishes without an error report, then it finally was sucessfull…but you have been told it DID have trouble so can make another back-up of important files, etc. Most DOSes will retry when an error occurs, just like SAFE does, but will not let you know it is having any trouble…until it cannot load the file at all!