Gecko/20110303 Thunderbird/3.1.9   
   rogrammer.misc,comp.os.os2.misc   
   UTC)   
   os2.utilities:178 comp.os.os2.programmer.misc:2104 comp.os.os2.misc:3150   
   From: Jonathan de Boyne Pollard    
      
   > If you want to implement the "L" variants of the various filesystem    
   > APIs, you basically have to rewrite FAT32.IFS.   
   >   
      
   That's complete twaddle.  The code that I posted earlier is, if one    
   changes sfi_size/sfi_pointer to sfi_sizel/sfi_pointerl, pretty much all    
   that one has to have.   
      
   > It's not just adding an additional entry point.   
   >   
      
   That's exactly what it is.  Rewriting FAT32.IFS would be necessary for a    
   complete change of implementation strategy or a major change in    
   interface architecture (such as, say, changing to a Windows NT IFS where    
   everything is an IORP), which simply implementing a couple of shims to    
   map a 64-bit integer parameter into a 32-bit integer parameter, keeping    
   the semantics as they stand, is not.   
      
   > The "L" variants are called as 32-bit entry points whereas the old    
   > filesystem APIs are called as 16-bit entry points.   
   >   
      
   The "L" does not denote bitness.  The "32" denotes bitness.  There are    
   16-bit and 32-bit flavours of "L" and non-"L".  I already pointed out    
   that the VirtualBox shared folders IFS implements 3 out of the 4    
   possible combinations.  I even gave you the four function names.  I've    
   also checked and reported the names of the "new" (i.e. 1999, again)    
   64-bit fields of the system file table entry that the "L" entrypoints    
   are expected to manage.   
      
      
   --- Internet Rex 2.31   
    * Origin: virginmedia.com (1:261/20.999)