Faulty Install of 97513

boleyd

Well-known member
The erratic nature of my activities proved the original load was faulted. New install alongside of original. So far I have had only one 3/2/1 mph stop and not able to duplicate.

I see no interaction between the loads as it should be since the data package and the code are totally separate. Now have to put routes and picklist back together. Best simple test in my case -- straight piece of track and three 04 signals. Should show red, yellow, white far to near. Faulted load did not.
 
I'm sorry I can't follow your description here.

Please try to explain each issue individually and in detail in plain English rather than shorthand so that we can assist further.
 
I had some problems with locomotives being seriously delayed at signals and switches. Naturally the first thought is that some common components may be the fault. However, after hours of messing ( I do not test) with various settings, assets, routes, etc. I could only conclude that the common element was the program itself in some form or manner. So, I installed a fresh copy and updated it to the present build. None of the issues I have had in the past, related to slow approaches or stops occurred in this load. Thus, I can only conclude that my copy of the program had become tainted in some manner and thus exhibited the odd behaviors of the trains.

Or, in simple language - the darn program became messed up and was wasting my time. It made me mad. $70 bucks and I was getting crap not joy.
 
There's nothing worse when there are multiple issues that can cause the same symptoms, or have multiple problems that are influencing each other and confuse us. I ran into this one day with my network. We initially lost our internet the same day we upgraded service. I called our ISP to complain about the DNS and other problems we were having, and being evening and very dark when the service was turned on, the tech said he would be out first thing in the morning to replace our router.

In between the time we called for service and when the guy came out to check the setup, we found that a truck had passed by and pulled the phone wire off the house. I forgot to mention that this was in the old ADSL days. The tech replaced the wire thinking that was it, but that still didn't fix the problem. The issue turned out to be the initial DNS issues we were having now complicated by the broken line! Sixteen hours later, we had network access again, and what was worse is I had to keep telling the front line helpless desk tech on the phone that the broken line didn't fix the initial problem.
 
Back
Top