Network installation of scribe

[Fdesser]

So here is the scenario:

 

We have 8 people typing incoming dictation from our accounts and all of them are within the office. In order to maintain a current file list, which is shared by all of the users, it was necessary for all users to see the same "file location"

 

The initial solution was to run express scribe on a terminal server and have all users access the "same" copy of scribe from the TS virtual desktop. The advantage of this was that all of the users were pointing to the same source directory of "c:\documents and settings\all users\application data\nch swift sound\scribe\..." The disadvantage is that Terminal Services, for unknown reasons, caused a latency in the release of the foot pedal which accounted for a 4.5-5 second delay of streaming sound. In other words, you release the pedal and sound continues for 4.5-5 seconds. Not an easy thing to deal with, as a typist.

 

So... a new solution needed to be reached.

 

Here it is, quick, relatively simple, and it doesnt seem to cause much of a problem in a shared environment. The downside may be seen if Word or another windows based software package is used and the user has customized settings for their environment that are saved in the common file location. The end result of the "fix" is a registry change that will affect all programs which refer to the "all users\application data" registry entry. We did not have issues with this as we use WordPerfect 5.1 for DOS, imho the fastest proram, still, for power typing.

 

Anyways, here are the steps which I took:

1. Install Express Scribe onto the distribution server.
   
2. Map network drive to the shared directory location.
   
   Create a share on your server to the "C:\Documents and settings\" folder.
   
   
   Map a network drive to this share. In this example we will use
   N:\
   for the network drive.

   
   

3. Create a batch file to modify the registry changes.
   
   Use notepad to create a new batch file (we will call it
   scribe.reg
   ).
   
   
   Place the following entries into this file:

   
   

   [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]
   
   
   "Common AppData"="N:\\All Users\\Application Data"

   
   

   Place this file (
   scribe.reg
   ) in
   N:\
   
   
4. Create an express scribe startup batch file.
   
   Use notepad to create a new batch file (we will call it
   scribe.reg
   .
   
   
   Place the following entries into this file:

   
   

   %systemroot%\regedit.exe /s N:\scribe.reg
   
   
   c:
   
   
   cd "\Program Files\NCH Swift Sound\Scribe"
   
   
   Scribe.exe

   
   

   Copy this file to
   C:\ AND to N:\
   
   
5. Create an express scribe shortcut to the batch file.
   
   Refer to the batch file on
   C:\
   
   
   Change the icon (if desired) to use the icon in file Scribe.exe

   
   

Thats it! Ultimately, it is transparent to Scribe. One more warning: make sure that scribe is set to use "Default sound out" or the users will not have control of their system sound. Also, changing the speed/sound in the program effects all users as the settings.ini file is shared by everyone.

 

The net result of the above is to launch a small script that will incorporate the registry entry each time you run scribe, in order to ensure the list is always accurate. You must incorporate the .reg file into the registry AFTER the drive is mapped as Windows will rewrite the registry entry to C:\ if the original mapping is not present (and it isn't because windows maps the drive after loading the registry) when the registry is loaded.

 

You may not be able to install scribe to an alternate location but you can spoof it into using a different location for data.

 

I don't know if anyone else has experienced this, but hope this helps.