constantly checking the special sync lengths described above. Even 
      the slightest mismatch from the norm will halt the program load. 
      Thus, if your DISK DRIVE speed is slightly off from 300 RPM, you 
      may experience difficulties in loading some RapidLok formatted 
      programs.
      
      If you examine the directory sectors of track 18 on a RapidLok 
      disk with a track and sector editor, you will notice that after 
      each file name is a sequence of two or three bytes. RapidLok DOS 
      actually uses these bytes much in the way Commodore DOS does the 
      track and sector pointer! The actual beginning track and sector 
      number and program length are embedded (encoded) in these bytes.
      
      Little is known about the RapidLok master-key on track 36. The 
      routine that RapidLok uses to decode it can be copied, but actually 
      writing out the key has not yet been done!
      
      On recent RapidLok versions (5 and 6 to be specific), they use 
      TRACK to TRACK alignment. What this means is that if you were on 
      track 19 and you had just read sector 0, if you were to 
      immediately skip the drive-head to track 20 and read the first 
      information you encountered, you would be reading the data for 
      sector 0 of track 20! This is a very simple explanation. Sometimes 
      track-to-track alignment can be done with a "skew". i.e. track 19, 
      sector 0 matches track 20, sector 6, which in turn matches track 
      21, sector 12. The skew is 6.
      
      RapidLok DOS uses a combination of blank sectors ($55) and full 
      sectors ($6B) on one track. This track must be perfectly aligned 
      with the track before it. When DOS finishes reading the last sector 
      of the first track, it bumps the drive-head to the half and half 
      track. If the track-to-track alignment is correct, it will 
      encounter a full RapidLok sector, and will continue to load. If the 
      alignment is incorrect, even off by one sector!, the drive will 
      encounter an empty sector ($55) and the loader will then commit 
      suicide within your drive! So even if a person could exactly 
      duplicate two RapidLok tracks, he would also have to get the timing 
      within his format routine exact enough to align the tracks 
      correctly.
      
      An example RapidLok Protected track:
      
      SYNC LENGTH      BYTES             DESCRIPTION
      -------------------------------------------------------------------
      $0029   52 55 35 29 4B 74 DC B5    track 1,0 reference header
      $003C   75 93 59 25 D6 ED 7A 00    sector 0 header 
      $0005   6B BB C9 24 BA FF 35 DF    sector 0 data block
      $0005   75 92 59 25 D6 ED 6E 00    sector 1 header
      $0005   6B DE 59 24 96 7B ED F7    sector 1 data block
      .....   .......................    .................
      .....   .......................    .................
      
            K.J. REVEALED TRILOGY    PAGE [90]     (C)1990 K.J.P.B.

<<previous page - next page>>