FAQ: Server Access
In a networked environment, does Sketchpad need to write to the server? To the workstation?
As described below, when run from a server, Sketchpad attempts to write to the local workstation, but only if the workstation is write-enabled. Disallowing local write-access does not prevent Sketchpad from working.
When users exit Sketchpad, the program attempts to write any modified user preferences to the local volume. (On Macintosh, it attempts to update the "Sketchpad Preferences" file in the local volume's System Folder's Preferences folder. On Windows, it attempts to update the "Sketchpad Preferences.dat" file in the Windows directory.) If this file is locked, or if the user does not have write-access to that file, no update is made and Sketchpad reverts to default user preferences on the next launch.
Windows users have additional control over where Sketchpad attempts to locate its Preferences file. For more information, see Sketchpad Help or the Reference Manual [Advanced Topics | Tips For Experts | Command-Line Flags for Sketchpad (Windows Version)].
Of course, when users attempt to save their documents, Sketchpad attempts to create or modify files in the volume and directory that the user chooses. If a machine has no floppy drive and the user has no write-access to any local or networked directory, then that user cannot save their Sketchpad documents across sessions.
Sketchpad is also configured to take special advantage of any files stored in the Tool Folder, a folder stored immediately next to the Sketchpad application. In write-protected networked configurations, users may not have write-access to the Tool Folder. As of Sketchpad version 4.03 and later, both Macintosh and Windows platforms support alternate Tool Folder locations, allowing users with limited write-access to still take advantage of Tool Folder functionality. For more information, see Sketchpad Help (version 4.03 or later): Advanced Topics | Advanced Tool Topics | Alternate Tool Folders.