Hello, Thanks for the response. Yes I know you were talking about embedding resources at build-time. That is why I asked for run-time. The reason for this, if the user removes the images at the path or user wants to redistribute the screen saver. Then user would need to relocate the images as well. So in short I want everything in a single exe(scr) file. Yes, resourcewriter creates a satellite dll. This has better results as compared to loading images at run-time.That is, the actions of user deleting the images does not affect the screen saver. However, relocating the screen saver on another machine would still require to move this dll as well. Thanks.
"C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, it blows away your whole leg." - Bjarne Stroustrup