WorkSpacer is brought to you by WiGuys Software - "Software designed because we THOUGHT we needed it!" Welcome to WorkSpacer. The Zip should contain the following files : README.TXT - This file WSPACER.WBT - An optional front-end for WorkSpacer. WSPACER.WBD - Dialog Box required by WSPACE.WBT WSRUN.WBT - The Batch Builder File to restore workspaces WSMAKE.WBT - The Batch Builder File to create workspaces WorkSpacer requires the Norton Desktop for Windows Batch Builder and Batch Runner. First, WorkSpacer is freeware, with no warranties as to purpose or usability, implied or express. In other words, you use it at your own risk. I have tested WorkSpacer on my system, trying to simulate all possible conditions, and thusfar, it has run successfully. However...... That out of the way, what is WorkSpacer ? ----------------------------------------- Way back when, I tested something called hDc FirstApps. One useful application included in those applications stored desktop configurations as a named workset, and at your request, would restore that configuration to the desktop. I no longer use hDc FirstApps, but have always liked that concept, and missed the application many times. After some minor experimentation with batch files under the Norton Desktop for Windows, I decided to see if I might be able to accomplish something similar using the Norton Desktop for Windows Batch Builder Language. The result is WorkSpacer. How does it Work? ----------------- WorkSpacer operates by 1) obtaining appropriate information about your current desktop configuration, 2) storing that information in a private ini file in your windows directory (WSPACE.INI), 3) storing an appropriate list of chosen workspace names in a file in your NDW directory (WSPACE.LIB), and 4) Restoring to the desktop, the workspace that you choose from a list of available workspaces. Operation --------- A - Installation Unzip the WSPACER.ZIP file, and copy all of the WBT and WBD files to your NDW directory. WorkSpacer defaults to a setting of " C:\NDW\ " for this directory. If this is not applicable for your system, use Batch Builder to open WSMAKE.WBT, and edit the first two variable defaults (spacelib and spacebak) to the correct drive and directory. The only other default needed is the maximum number of applications that can be setup in a given workspace. WorkSpacer's default is 4. If you want a higher (or lower) default, using Batch Builder, open WSMAKE.WBT, locate the "maxhere" variable at the beginning of the file, and change the default to your default. After saving the changes, use Batch Builder to open WSRUN.WBT and locate the "maxrun" variable, and change the default to your chosen default. That's it. B - Operation There are two options for running WorkSpacer. The first is the simpler one. Simply run the file WSPACER.WBT. It will present a Dialog Bog asking whether you want to "Restore a Workspace" or "Create a Workspace". Take your pick, then follow the directions. The second option is to use WSRUN.WBT and WSMAKE.WBT as standalone operations (I prefer this as I find it faster to not have to always click "Restore a Workspace" everytime.) In order to create a workspace, you must first load all of the Window applications that you want (no files though... WorkSpacer currently will only restore empty Windows applications ). You will also need to know the EXE name for each application, and the full drive\path combo if the application is not in your path. Once you have the applications open, and sized to your liking, run WorkSpacer (either via WSPACER.WBT or WSMAKE.WBT). Choose the appropriate applications from the list presented IN PREFERRED ORDER OF LOADING. In other words, pick the apps from the list in the order that you want WorkSpacer to restore them, ending at the active application. Then, merely answer the questions as asked. WorkSpacer will do the rest. To restore a workspace, run WorkSpacer (using either WSPACER.WBT or WSRUN.WBT), and answer the questions. C - Error checking WorkSpacer currently checks the following when creating a workspace : 1) That the name you give the workspace does not duplicate an existing name EXACTLY and is no larger than 30 characters. 2) That you have typed in a valid filename, extension, and path. All filenames MUST have an EXE extension (99% of Win apps do) AND must either be on your path or have the correct path specified. Should you forget to type the extension, don't worry. WorkSpacer will add it if necessary. 3) That the application chosen has not been duplicated in this workspace name. Legal Stuff ----------- Not sure how this should be worded, but, for legality's sake, any tradenames used in this document are the trademarks of their respective companies. (Does that do it?) Future Stuff ------------ This version of WorkSpacer works, and works well (at least, by my testing.) However, I want to really push it, and make every "stupid" blunder I can, to ensure that my error checking is complete. If I do find something that gets past the current error checking routines, I will modify them to take that fact into account. I also may add a dialog box confirming the content of the entries to WSPACE.INI, however, I personally dislike too much screen activity, and decided, for now, to keep that one extra dialog box off my screen. Although I have attempted to optimize sub-routines as much as possible, if I discover a faster/easier way to perform the same function, I will incorporate it. I am not sure precisely how Batch Builder/Batch Runner search for labels in a WBT file (will have to ask Symantec/Norton), but once I find out, I intend to reorder the WBT's to take advantage of that. Should it turn out that calling another WBT is the fastest way to handle subroutines, then WorkSpacer will be modified accordingly. In Conclusion ------------- Right now, I can't think of anything else (although I am sure someone using WorkSpacer will!!). Any questions, comments, ideas, or suggestions can be addressed to : Gregg Hommel, WiGuys Software, 19 Rushbrook Drive, Kitchener, ON, CANADA N2E 3C1 (519) 745-9717 CIS # 72537,552 I also frequent the following BBS Windows conferences : EchoNet, RelayNet, NaNet, and ILink and can be reached via any of these networks. Take care, and have fun!!!