You can always stop the program during loading (e.g. GetModuleHandle/GetCommandLine/LoadLibrary etc.) then search memory for "Demo" string, next put breakpoint on read memory access (BPM) on that string, then trace-back the program to see what fragment is responsible for calling this function, etc...
Uff.... I'm only dreaming, since I don't have this app and time to crack it....

Regards.