Home/ Questions/Q 561013
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T12:24:19+00:00

I’d like to simulate a file without writing it on disk. I have a

  • 0

I’d like to simulate a file without writing it on disk. I have a file at the end of my executable and I would like to give its path to a dll. Of course since it doesn’t have a real path, I have to fake it.

I first tried using named pipes under Windows to do it. That would allow for a path like \\.\pipe\mymemoryfile but I can’t make it works, and I’m not sure the dll would support a path like this.

Second, I found CreateFileMapping and GetMappedFileName. Can they be used to simulate a file in a fragment of another ? I’m not sure this is what this API does.

What I’m trying to do seems similar to boxedapp. Any ideas about how they do it ? I suppose it’s something like API interception (Like Detour ), but that would be a lot of work. Is there another way to do it ?

Why ? I’m interested in this specific solution because I’d like to hide the data and for the benefit of distributing only one file but also for geeky reasons of making it works that way 😉
I agree that copying data to a temporary file would work and be a much easier solution.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You can store the data in an NTFS stream. That way you can get a real path pointing to your data that you can give to your dll in the form of

    x:\myfile.exe:mystreamname

    This works precisely like a normal file, however it only works if the file system used is NTFS. This is standard under Windows nowadays, but is of course not an option if you want to support older systems or would like to be able to run this from a usb-stick or similar. Note that any streams present in a file will be lost if the file is sent as an attachment in mail or simply copied from a NTFS partition to a FAT32 partition.

    I’d say that the most compatible way would be to write your data to an actual file, but you can of course do it one way on NTFS systems and another on FAT systems. I do recommend against it because of the added complexity. The appropriate way would be to distribute your files separately of course, but since you’ve indicated that you don’t want this, you should in that case write it to a temporary file and give the dll the path to that file. Make sure you write the temporary file to the users’ temp directory (you can find the path using GetTempPath in C/C++).

    Your other option would be to write a filesystem filter driver, but that is a road that I strongly advise against. That sort of defeats the purpose of using a single file as well…

    Also, in case you want only a single file for distribution, how about using a zip file or an installer?

    • 0