From: muta...@gmail.com   
      
   On Saturday, October 30, 2021 at 12:25:42 AM UTC+11, JJ wrote:   
      
   Thanks everyone for your comments.   
      
   > Yes. If you want the TOC to be like a file, the BIOS would need to be aware   
   > of the TOC data structure, in order to know the size of the TOC data. Though   
   > IMO, TOC is kind of low level file system that deals with tracks rather than   
   > directory/file. So in a sense, the BIOS needs to be aware of that low level   
   > file system.   
      
   > Yes, assuming what the `fgetc()` does is to read the user data sectors in   
   > non raw mode. Because the ISO file format (i.e. the *.iso) is only for one   
   > track non raw sector data (2048 bytes sector) excluding track pre-gap. It   
   > doesn't contain any TOC. TOC is usually saved as *.cue file.   
      
   Then I would like a single file that is the .cue followed by the .iso.   
      
   So my firmware BIOS will need to know which bit of the   
   TOC data structure to be able to know when to switch   
   command to read data instead of TOC?   
      
   I will also need to write a utility that can separate out a   
   combined file into individual .cue and .iso. It will need the   
   same knowledge as above.   
      
   Thanks. Paul.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)