OK I think I know where the problem is.
The program is a single thread exe, so that means when I run any calls to say vss or a Windows API that the program has to wait for a response, the program will apear forzen even though it isnt. To avoid this I use other exes from the files folder to work with vss.
SO depending on which OS your on the program will first run
vss_start.exe and then that will run one of the other files such as vss_7_64.exe.
That file is what works with vss, and that is the file (Or which ever one is set in the settings) the program looks for to see if vss is running. So when it says is vss running: no then that means it isnt seeing vss_7_64.exe (If your on Windows 7 64 bit) running.
So the problem may be those exes are crashing. Or vss_start.exe isnt being ran.
It goes in this order.
vss_start.exe (This also creates the vss log file), it opens a command pipe to a cmd.exe window to run the commands to work with the vss exes.
vss_7_64.exe (or one of the others) is ran from the bat file made by vss_start.exe.
Once the vss snap is created vss_pause.exe is ran. This does nothing, it is used so the program knowns that when it sees it that the snap file is ready to work.
And thats it. So even if vss_7_64.exe crashes the vss_start.exe should still be making a log file, but you said there isnt any log files.
So perhaps the problem is in vss_start.exe, is something blocking it? Or is it crashing?
Also something to known, vss_start.exe looks for TweakingRegistryBackup.exe to be running, if it isnt it closes itself, so make sure you dont rename the main exe.
Shane
