Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
\$\begingroup\$It's been a long time since I've looked at screen saver criteria, but I don't recall ever seeing a one file limitation. Time was that a screen saver was essentially just a renamed .exe - there were some optional API hooks if you wanted to connect to the standard config menus or something, but as I recall even that was optional. Where did you see the one file limitation that you're referring to?\$\endgroup\$
\$\begingroup\$@pikalek So, the user must install the software. Maybe that's what you are saying? I want that the user must be able to copy the screensaver to another computer.\$\endgroup\$
\$\begingroup\$I'm asking where you encountered the one file limitation because I don't think it is correct. I thought I recalled screen savers that dynamically load & display images slide show style, but I could be wrong. Since it's not easy to prove a negative, I'm asking where you encountered that particular requirement.\$\endgroup\$
\$\begingroup\$There's an almost infinite number of ways to embed data into an executable. At the most basic, you could convert the file to a byte array and define it in the executable itself. The real question is what format you need the data in when the screensaver is running and how to recreate that format from [whatever mechanism you use to store the data]\$\endgroup\$