From: nowhere@never.at   
      
   On 23/03/2023 23:27, muta...@gmail.com wrote:   
      
   > You have an existing PC, right?   
      
   yes I post from a windoze_10 here.   
      
   > So ignore the CD that came with the new PC.   
   > On your old PC create a FAT-formatted USB stick,   
   > or Joliet CD.   
      
   all my older PCs died already, format options on my current one don't   
   imply old style FAT32, only NTFS and EXFAT.   
      
   > With the bootx64.ef on it.   
      
   I see that it would need to have all my disk-functions already in this   
   boot.efi. My installer have to create partitions and format these before   
   the OS can be copied to it.   
   So I'd had to enter my whole start image (512MB) into this PE.   
      
   > And then boot from CD or USB stick (you may need to go   
   > into the BIOS settings to choose to allow booting from   
   > those devices).   
      
   >> So it would need me to buy a win11-DVD which I wont ever do.   
   >> any suggestion ? I'd need a boot able formatting tool first.   
      
   > What do you currently use?   
   win 10 on MSI Ryzen5. cannot boot from USB.   
      
   > If you want to use someone else's OS that is capable of   
   > formatting a disk and also capable of booting on UEFI,   
   > and it can't be Windows, and it can't be Linux, I am not   
   > familiar with that market. FreeBSD? PDOS/386 only   
   > works with a BIOS system currently. PDOS-generic will   
   > do UEFI but it is still proof-of-concept. It will basically   
   > reuse the existing code though, so it shouldn't be a   
   > big deal. The big deal is me trying to get it to do   
   > unusual things like running 32-bit code in 64-bit mode   
   > before taking it out of POC.   
      
   >> Next demand would be a tool which can create folders.   
      
   > That tool is normally called an OS, but there are some   
   > tools called "mtools", and a fairly recent public domain   
   > version too, that do that to a disk image.   
   >   
   > On PDOS/386 I can make that disk image an actual   
   > raw disk, which is what I use for formatting.   
   >   
   > The tools are included on the PDOS/386 image.   
   >   
   > They're written in C90 so you can run them on any other   
   > system you can find (after recompilation).   
      
   I can't re/compile any C-source. there is no C on any of my machines.   
      
   >> And then such a tool must be able to copy my OS-boot-image   
   >> into a bootx64.efi perhaps at a certain offset dunno yet how   
   >> .efi files were organized (I may find some info on the net)   
   >> but the hex-dumps below show that you created M$ PE-files.   
      
   > Yes, there is no choice. You need to create a PE executable.   
      
   > It's just a normal PE executable, with the sole exception that   
   > the subsystem number is set to 10. So that's one byte that   
   > needs to change (plus the checksum, as that byte is included).   
      
   > The linker will do this for you.   
      
   there is no linker on my PC.   
   I have several options to create almost empty PE with   
   RosASM, FASM, NASM, but they aren't 64-bit ?   
      
   > It's unclear to me what restrictions you are introducing,   
   > or why, but I know of two linkers that produce 64-bit   
   > PE files, both running under Windows, and neither   
   > supplied with any version of PDOS. But if you just   
   > want a single binary with 100k of "ret" or "nop" or x'00',   
   > I can provide that for you.   
      
   Thanks, once I figure the difference I might be able to modify.   
      
   >> one more problem: my OS-images incl. boot-part are just a bunch of   
   >> consecutive sectors (can be seen and stored as .bin files)   
   >> no header, no redirection, very own checksum algo.   
      
   > That can be embedded in the PE file. It's just code.   
      
   > But you would need to take care of relocation yourself   
   > if you are just zapping bytes instead of using a linker.   
      
   There are no relocation needs in my code.   
   ...   
   > That above code is entered (from UEFI) via a call.   
      
   > There will be 2 parameters (in registers, not on the   
   > stack - that's the Microsoft 64-bit calling convention).   
      
   OK fine, tell me more :)   
   where can I find a list of available UEFI functions ?   
   what I found on the net was just small talk w/o sense.   
      
   >> [...]there is no assembler :) and rare ever will be.   
   > You want to enter machine code, right?   
      
   yes, I stored my OS image (512MB) on USB and on CD.   
      
   > So all I did was make space for testing purposes.   
   OK.   
   > I used serial port as an example. I am guessing you   
   > can send a single byte to the serial port in that   
   > amount of space.   
   there might not be any serial port an new machines.   
   __   
   wolfgang   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)