For those that are interested, it is possible to create a service for a 2nd instance of CF that will survive a server restart. (The new instance should be set as a service if you specified that when you created the instance, but if it doesn't....)
1. Using the SC.EXE program (see Microsoft KB 251192 referenced in previous message), create the service. The commad line is
sc create "Adobe ColdFusion 9 AS <instance-name>" binPath= "<path-to-jrun4-install>\bin\jrunsvc.exe" DisplayName= "Adobe ColdFusion 9 AS <instance-name>"
Replace <instance-name> with the name of the instance as shown in CF Admin Instance Manager. Replace <path-to-j4un4-install> with the location where you installed jRun4 (I recommend installing it in a non-default location for a bit of obfustication for hackers.)
If all is well, you should see a message "[SC] CreateService Succcess". If something goes wrong, you will get a syntax help screen. Make sure you put an space after (but not before) the equal sign in the command.
2. That will create the basic service; you should be able to see it in Services. There are some additional parameters that are needed; they are set up via RegEdit. You should find the registry entry for the new service in \\HKLM\SYSTE]CurrentControlSet\Services .
3) the additional registry entries needed are
-- CurrentVersion - REG_SZ - 4.0
-- JRunServer - REG_SZ - <name of the instance as shown in CF Admin>
-- NoRestart - REG_DWORD - 0
-- SystemErr - REG_SZ - {jrun.rootdir}\logs\{jrun.server.name}-err.log
-- SystemOut - REG_SZ - {jrun.rootdir}\logs\{jrun.server.name}-out.log
-- Description - REG_SX - whatever text you want to appear in the Services description area; default is "J2EE Applicaiton Server"
4) After you add these values via RegEdit, you will need to manually restart the service, which you will find in the Services screen. If the instance is running in CF Admin instance manager, stop it there first, then start it via the Services screen (takes about 30 seconds). Once started, it should show up as started in the CF Admin instance manager. If the service doesn't start manually, look in the Windows Application Event log for errors.
5) When the manual start of the service works in Services, change the Startup Type to "Automatic".
The results should be that the CF instance will be automatically started on server restart.
Good luck !! ....Rick...