Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Same Installer problem with Treez, didn't actually ask anything, seems you have to point it at your current trainz install if it's not the one not the one it thinks it is if more than one and then manually remove anything after \auran\TS2009 otherwise it will create a sub folder in your 2009 folder, a point I didn't spot first time around. (makes note to pay more attention to Auran installers!)
Worse news is that on running this installer again, I assume the S&C one is the same? it won't let you choose a path on the second attempt, a quick visit to regedit fixed that however people should not need to do such things when using a properly setup update installer which is effectively what this is.
Same Installer problem with Treez, didn't actually ask anything, seems you have to point it at your current trainz install if it's not the one not the one it thinks it is
I have TS2009 WBE. Just downloaded Treez addon pack. It will install as a standalone, but will not install as an addon to my Trainz program. (Even re-downloaded Treez as I thought it might be a bad download.) WBE runs fine in both native or compatibility mode. The installer gets all the way to where it indicates it is setting up folders/directories then stops responding. Have sent a ticket to the help desk, but no reply as yet. Reading these posts I have seen that other people are having similiar problems? Is there an answer yet on this?
Ernie, The Task Manager will always say that the program has stopped responding, but it is just waiting for other processes to do there job, to find out, look at the Task Manager, but this time click on the Processes tab, now click on the CPU column, this should bring to the top all the processes that are working in the background, and one of these should be trainz related.JCitron,
I just waited and waited and finally the program did install as an addon. I guess the Windows Task Manager indication that the program had stopped responding was incorrect. Again, I guess waiting was the answer.
Thanks,
Ernie