Create an Obey file called User in !Boot.Tasks. E.g. SCSI::SSD.$.!Boot.Choices.Boot.Tasks.User In this User file set up the following: Set Server$Path to point to the server on all computers. So on our system the Server is called Lab. On all the computers the command is then: Set Server$Path Share:Lab On the server itself, you could have Set Server$Path ADFS::HD4. In this User file, you also need to setup PipeDream$UserPath to tell Pipedream where to ook for common resources that you wish to share. You may have your PipeDream files in several places. On our system these are in two places, ADFS::HD4.$.PD.Data and ADFS::HD4.Resources.Stationery So we set: Set PipeDreamUserPath Server:PD.Data.,Server:Resources.Stationery. Yet there is a problem: if on another computer (in our case, the computer called "Office") we open a Share window and run a PipeDream file, say the file called PD.Data.Sales, Pipedream will run the file Share::Lab.PD.Data.Sales. As that sales system has supporting documents, these will all be picked up as Server:etc. Put they point back to the file Sales. So another copy of Sales is picked up as Server:PD.Data.Sales and the system oes not work. To get around this the mainfile must be indirected so it runs as Server:PD.Data.Sales. This can be done in two ways: An Obey file with contents Filer_Run Server:PD.Data.Sales A PipeDreamCmd file with the command \Fl|i "Server:PD.Data.~Sales"|m Or you can use a virtual link pointing to Server:PD.Data.Sales Multiple access There is a problem where two or more people want to use the same data. PipeDream is not multi-axess, so if two people load and change the same file, the second person to save the file will win and all changes made by the first user will be lost. To get around this, we have evolved two systems: the first effectively locks the second user out, so only one person at a time may use the file. The second is a lot more complicated and involves a mirror copy of the original file with special columns for the new data. A series of scripts ar run every so ofte to merge the changes into th main file, delete the mirror and create a new mirror file. Such a system is complicated to define so is likely to be complicated to set up and will not be described here!