· These installs work with PrintDriver versions 3.40b and greater. (This is because the newer PrintDriver relies more on the existing \elixir\desktop\system\system.ini.

· If previous versions of the PrintDriver had already been installed, then delete the PrintDriver information in the WIN.INI before installing:

- delete the section of the WIN.INI called [Elixir PrintDriver,DISK]

- delete the section called [Elixir 3.0].

Installing the PrintDriver will recreate these files

In these sample cases I am using the V: drive as the network drive. Substitute your own correct drive.

Network install #1:

Program files installed on V:\

Data files installed on V:\

Config files installed on C:\

PrintDriver installed on C:\

Once the Desktop has been properly installed, then you can install the PrintDriver locally on your C: drive. The PrintDriver will automatically read the Desktop’s system.ini file, which will direct all resources to the network drive.

(Note: The ttfont.nam file does not get created on the network drive unless the user has tried to convert a TrueType or ATM font to an Elixir font. So if a user tries using the PrintDriver, they might get the error "Cannot find TTFONT.NAM file". All they need to do is copy the file from C:\elixir\fonts\maps to V:\elixir\fonts\maps. (The need to manually copy this file will be eliminated with Elixir 4.0.)

(Note: Don’t forget that C:\ELIXIR has to be in the Path statement (of the autoexec.bat) for the PrintDriver to work.)

Network install #2:

Program files installed on C:\

Data files installed on V:\

Config files installed on C:\

PrintDriver installed on C:\

Same instructions as Network #1 install. The ttfont.nam file needs to be copied from C:\elixir\fonts\maps to V:\elixir\fonts\maps.

Network install #3:

Program files installed on V:\

Data files installed on V:\

Config files installed on C:\

PrintDriver installed on V:\

This worked also for me. At one point I got some Spooling errors, but on subsequent tries, there were no errors (I think it was a temporary network conflict).