From: thefadden@gmail.com   
      
   On Wednesday, November 2, 2022 at 7:09:31 PM UTC-7, gid...@sasktel.net wrote:   
   > I was taking Antoine's comment of T1/SB/01 as the location of the VTOC   
   within DOS. Unless that was a typing error and was supposed to be T11/SB/01,   
   in which case it has a different meaning.    
      
   T1/S11 holds the code loaded into $ac00-acff.  It starts with the tail end of   
   a function that initializes some file manager stuff, including the VTOC   
   location (the byte at +$01 in holds the track number).  The value would not be   
   useful if the disk weren'   
   t bootable.  There are likely some disks with a relocated VTOC that would   
   benefit from looking there, though you'd want to test the code around that   
   location to see if it looked like DOS before putting too much faith in what   
   you find.   
      
   For DOS 3.2, it would be T2/S1.  Custom DOSs often just made a few in-place   
   edits, so standard routines tended to stay in the standard places.   
      
   If you wanted to include this in the strategy, it might be best applied as a   
   fallback if T17/S0 doesn't look like a VTOC, and you were about to write the   
   disk off as "unrecognized".   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)