Nov 20, 2011 at 12:44 AM
Edited Nov 20, 2011 at 12:56 AM
I've been looking at this.. some things that I've found so far:
1. The error occurs on both Windows XP and Windows 7 in my testing
2. Based on this bug:
I don't see the above as the cause.. Everything I've done permission-wise is not solving the problem. Most of what I've found on the Internet mentions this as a permissions issue. There's even a fix here: http://url.cwl.cc/nkmzl
3. Creating the date-based directory structure "\shot_11\19" in this case, allows CloudShot to create the file and carry on. This would require creation of this directory structure every day for the application to work.
4. Creating half of the directory structure "\shot_11\" in this case, does not correct the issue
5. I have not been able to get this software working post-installation once without some sort of interaction.
6. on Windows XP, I used Sysinternals Procmon to watch the process. CloudShot was set to save a screen shot to C:\ - the following is what procmon sees: http://twitpic.com/7gkyvy/full
So, it would appear as though CloudShot checks the root, then the full path, then part of the path and then fails. It would seem better to just create the image file in the location specified and not hard code a dated path reference.
This seems like a useful tool and it would be a shame for it to remain in this unusable state.