I can't be any help on the turning the code into an executable (whatever) part, (EDIT: See bottom for a tiny (crappy) idea..) but if u have dbc 1.13, check the command line and...
IF IT CONTAINS:
/p [number] - You should show a preview window of your screensaver. [number] indicates a hWnd or hDC or something of the little box inside the screen picture inside the screensaver config. box (inside the Display control panel). Probably best to just pop up a small window discreetly in a corner somewhere that runs the screensaver and quits after a few seconds. (Make a screensaver, place it in /windows/system32 with a .scr and make it say something like: "Print command line$()" or whatever the command is. I haven't got the 1.13 manual at hand.
/c [number] - Tells you to show a configuration window for your screen saver. The [number] is useless, but I'm guessing it's something kinda like in Visual Basic when ur using the Windows API stuff and its asking for a hWnd for a dialog, which it then (seemingly) completely ignores... weird. Just show a dialog.
/s OR /S - You should start the screensaver. If it's /s then it's either time to run the screensaver, or 'Preview' has been pressed in the Screensaver tab inside the Display control panel. If it's /S then the screensaver has been found in Explorer or whatever, and the 'Test' command activated (by default the command that occurs when a .scr file is double-clicked), although you don't really need to know that.
<NOTHING AT ALL> - !!!IMPORTANT!!! Your screen saver file has been found in Explorer or whatever, right-clicked, and 'Configure' clicked. Just show the Config. dialog again.
*OR*
Someone found your screen saver file and ran it. Only it wasn't a screen saver file, it was a .exe
(Note: If your screen saver file has been right-clicked and 'Install' chosen, your screen saver file will be copied into /Windows/system32, the Display control panel opened, and your screensaver will be selected (your scr will be started with /p [number] b'cuz the user is seeing the 'panel, so its preview time, innit? Apart from that, your program doesn't get any say in this AT ALL).
Your screensaver should be a .scr file. No action, apart from either copying into /Windows/system32 (or /Winnt/system32 win2000/NT users - i haven't forgotten about you

) or right-clicking the file and choosing 'Install' is needed to populate your screensaver into the box in the Disp. panel at the screensaver tab.
It will appear as the filename w/o extension, so My Super Screensaver.scr will come up as My Super Screensaver.
(Note: This was found out by experimentation with an app, renamed to a .scr, that just showed a message telling you what command line had been passed to it. BTW, the number is 6 or 7 digits long, and is a random number belonging to some part of the Disp. control panel).
Well..... That's all I know. Enjoy.
(P.s. how about with ur screensaver maker, it consists of two programs; the first one is the 'studio' that makes a file with commands in it, and the second one is the 'player' that takes the file and runs it. That way when they press 'make screensaver' they get the 'player' (renamed to a .scr) and the file, and those two files are put in a setup program. (Can't type more. Fingers aching).
[img src=http://blanky.pt-web.net/ddd.gif] >::p