|| Zedex || How to install Zedex || How to Set Up a Peer to Peer Network

 || Windows for Workgroups || Policy Editor || Download || Installing Programs on Workstations  || Zedex and Mac's 

Running programs from the server.
 
Normally in a peer-to-peer setup you will be running all programs from the local C: drive.   If your disk space is limited on the local drive, or you have a very large application that rarely gets used, it may be wise to run the program off the server .  This can almost always be done.  You don't need to purchase server software to do it. However, you must have the proper network license for the program you intend to run or individual licenses for each peer workstation.

First you must dedicate a specific drive letter that connects to the directory on the server that holds the program (lets face it, your computer needs to know where to find the program).  If you program is on c:\programs\admina on your server (this folder must first have been made to share on the server), run File Manager or Explorer while on a peer workstation and select Connect Network Drive ("Map Network Drive" on Explorer). Choose the letter you want to use (do not use Z: or X: because these letters is reserved for Zedex)( for our example we will use the letter H) and type in the path as follows \\zedex\programs\admina and select "reconnect at logon". In this way, every time you boot your computer, it automatically sets up a drive letter H:  and the path to the specific directory on the server. Of course, the server must be on beforehand!

Is is best to put all applications under one directory, so that when the computer connects to that directory, all shared programs are available through one drive letter. Of course, you will have to place each program in a separate folder under that directory.

Administrative setup on server:
Some floppies are prepared for an administrative setup. Usually an administrative setup is strictly for the purpose of running the programs off a server, and not for distributing the programs to the individual workstations so that they work locally.  But some programs will allow you to choose how you want them set up on the server.    Try to make an administrative setup.  Load the program onto the server, but instead of typing a:setup, type a:setup /a
If it says it can't find the admin.ini (or something like that),  then the disks are not set for network installation.  If they do proceed, then tell them the path to the administrative directory you want to use (as an example,  c:\programs\admina). If they ask where to put the MSAPPS files, save them to a sub directory of the same directory,  (as an example, save files to c:\programs\admina and the MSAPPS files to c:\programs\admina\msapps). Now you can put those floppies away for safe keeping. You may need to map a different path to the MSAPPS directory.

Network Setup on each workstation:
On each peer workstation, at the Run command, type H:setup /n .   Setup will set up the program to run as a shared program. It is as easy as that. Check the program's readme.txt to see if there is an alternative way to setup their program. The MSAPPS directory may need to be mapped on a separate drive.
 
Other Programs:
If the program does not have a network setup, you can still succeed, but it takes a little work.  First setup the program as a running program on the server.
Next install the program on the local peer workstation as a running program. See  Zedex and Installing Programs on a Peer-to-Peer network.
Having done so, delete the directory of the program and all its files (so that you recover the disk space) on the local peer workstation.
From the peer workstation map the network drive H: (or whatever) to the directory of the program you want to run (this is the running program, not the setup directory) on the server.  Under Program Manager, select File, New, Program, and in the path select "h:\XXX.exe" (where XXX = your program name).  The program should now be setup to work.

Using Explorer, create a shortcut on each local computer to the .exe on the server.