QUOTE(charliechan @ Jul 1 2008, 04:51 PM)
Good Morning:
This is a copy of a post that I left over at Ohio Valley System. It explains that I used Activity Generator to convert the signals to permissive before the route update. The backup file was used after the upgrade to restore the signals.
"Good Morning:
I had the same problem, what I found out was that I used Activity Generator to turn the signals off, and when I tried to change them back, Activity Generator copied the old sigscr.dat file from the former Bodiddly folder. When you use Activity Generator to convert the signals, it copies the sigscr.dat to sigscr.sbk as a backup and then when you restore the signals it renames the sigscr.sbk back to sigscr.dat.
Drove me crazy until I figured it out.
Hope this helps.
Chandler"
Good advice. This usually won't be a problem but bears some discussion. If you convert signals in a route to permissive, then upgrade or change that route w/o converting back, then, when you "restore" the signals the program will recover the old signal script from the previous version of the route since AG saves that. My advice: if you are going to upgrade a route and the signal script might change, first restore the signals to default. Next delete the sigscr.sbk file in the \Archive folder for that route. Then this won't happen. Thanks for bringing this out, it is a side effect I hadn't thought of!