From: muta...@gmail.com   
      
   On Thursday, March 23, 2023 at 7:25:24 PM UTC+8, wolfgang kern wrote:   
   > On 23/03/2023 10:08, muta...@gmail.com wrote:    
   >    
   > >>> The C library that I use that wraps the UEFI calls is 46k in total    
   > >>> (executable).    
   > >>    
   > >>> I suspect the requirements for UEFI are a modern machine    
   > >>> with much more than 46k of RAM.    
   > >    
   > >> it's unfortunately the other way around:    
   > >> I can't buy any new PC-hardware w/o UEFI on it.    
   >    
   > > I don't understand.    
   > > What's wrong with UEFI?    
   > > What's wrong with 46k as part of a BOOTX64.EFI?   
   > first it's HLL-styled stack abusing bloatware. And I cannot boot my OS    
   > on it nor use my own tools. it needs on INT13 to start.    
   > So what is the UEFI equivalent to INT13 and how can I make it boot my    
   > old stuff from either CD or USB ?   
   > >> I'm interested how and where to start such an attempt,    
   > > You want to know how to write a hello world using UEFI?   
   > No! I like to see what tools are required to format and prepare a new PC    
   > for my needs.    
   > __    
   > wolfgang   
      
   Not on my computer at the moment so can't reply properly.   
      
   You said you just needed your bootloader loaded and then you no longer use the   
   bios, right?   
      
   In that case, the equivalent of int 13h is nothing.   
      
   You just need to name your bootloader bootx64.efi   
      
   Uefi has the bloat in firmware to recognize an entire file system.   
      
   There are some other issues though.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)