Scratch
archived forums
#1 2007-09-20 00:13:17
Problems saving to a redirected Desktop path
Hi there,
We run a Microsoft Active Directory-based network with Windows Server 2003 R2 on the backend. The clients all run Windows XP Professional SP2.
We use Group Policy to redirect a number of common folder paths including the user's Desktop and My Documents. This allows users to "roam" seamlessly.
I've been testing Scratch 1.1 on our network by scripting it to install silently which works fine with the silent flag "/S".
The problem is that while saving to the redirected My Documents path works fine (e.g., \\file-server\users$\<username>\My Documents), saving to the redirected Desktop path doesn't (e.g., \\file-server\users$\<username>\Desktop), and produces the following error:
"Save failed: Folder may be locked or read-only."
The user has modify/change permissions to \\file-server\users$\<username>. This flows down to all sub-folders which include the My Documents and Desktop folders. In other words, the My Documents and Desktop folders have the *same* permissions. Which leads to the question, why does this error occur?
My other concern is that the error message is rather small and not centered on the screen (i.e., it doesn't really catch your attention). In fact, I must admit that I missed it several times at first which lead to much confusion! Also, the fact that you can click anywhere on the screen to discard the message doesn't help either (even though there is an "OK" option beneath the message).
It would also be ideal to set the default "save" path. Because at the moment, it defaults to C:\Program Files\Scratch\Projects which users do not have write access to.
Thank you for your help. Looking forward to a response soon 
And cool product by the way Looking forward to using it in the classroom.
Last edited by fault (2007-09-20 00:14:47)
Offline
#2 2007-09-26 09:24:46
Re: Problems saving to a redirected Desktop path
Thanks for reporting this problem. I'm not sure why the desktop path is not working. It's a good idea to show the path in the error dialog to aid in debugging.
Someone else reported a problem similar to this, but in his case only one machine on the network had a problem writing to the shared drive. It turned out to be a small difference in that machine's configuration and it was easy to fix but, unfortunately, I cannot find his email or remember what he did. But in your case, you might look at the difference between the desktop and documents path names and see if there are any small differences in syntax that might account for the difference in readability. Something like a difference in how the shared drive is named or the folder delimitors. (Although, from what you wrote, I did not see any differences that could account for it.)
It may be a good idea for Scratch to make the default save path be the user's documents or desktop folder. We'll consider that for the next release.
Good luck. And if you figure out how to solve this, please post the solution here. Thanks!
-- John
Last edited by johnm (2007-09-26 09:42:12)
Offline