Post Reply 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
2019-09-06, 20:05
Post: #3
This turned out to be much simpler than it seemed. The downloaded file appeared not as a RAMdisk (hence, no new fs device) but as just a file in the default volume.
My mistake was thinking that because this was a disk image file, that an INITRD would create a UEFI disk. Nope... just a file.

UEFI FileIo was able to access the file by name. Since what I was looking for was it's address in physical memory, but it was stored as a file, it was just a matter of reading the file size, allocating memory for it, and reading the file into the allocated memory. Pass the address and size through to the booting OS and it was able to mount the disk image as a RAMdisk. Problem solved.
Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
INITRD Basics - GMN - 2019-07-18, 15:52
RE: INITRD Basics - NiKiZe - 2019-07-19, 06:12
RE: INITRD Basics - GMN - 2019-09-06 20:05

User(s) browsing this thread: 1 Guest(s)