- Joined
- Sep 22, 2004
to teh FOLD!
The batch files available in this thread are for Wedo style service installs (also available in this thread). You have done a service install in Stanford style (download available direct from Stanford). Wedo names the service FAH (single instance) or FAH1, FAH2, etc. (multi-instance) while stanford uses FAH@(path to FAH) as the service name. You could probably edit the batch files and change the service name to what you see in the service manager (services.msc) and that will probably work, don't see why not. Otherwise, you could ditch the Stanford install and reinstall with the Wedo One-Click found in this thread. I, and many others here, like the way Wedo did the services install better than the way Stanford does it. Seems to start/stop quicker to me. Also, once you install the Wedo service the batch files will work without issue.
The batch files available in this thread are for Wedo style service installs (also available in this thread). You have done a service install in Stanford style (download available direct from Stanford). Wedo names the service FAH (single instance) or FAH1, FAH2, etc. (multi-instance) while stanford uses FAH@(path to FAH) as the service name. You could probably edit the batch files and change the service name to what you see in the service manager (services.msc) and that will probably work, don't see why not. Otherwise, you could ditch the Stanford install and reinstall with the Wedo One-Click found in this thread. I, and many others here, like the way Wedo did the services install better than the way Stanford does it. Seems to start/stop quicker to me. Also, once you install the Wedo service the batch files will work without issue.