Continuous Request to 1 Hour Sort

boleyd

Well-known member
Yesterday I had done 2 or three "required" sorts per version 19 and 22 which are on the same SSD that is not close to full. Both ran ok. This morning both auto-start a 1 hour sort/repair of the database when I start them. Right now, on this PC, I am running yet another sort/repair that began automatically upon the start of TRS22. I am starting to accept the conclusion that I may need to just erase the SSD. Find a maintenance program (if there is one) and see if it has any issues. I can get a reasonable reconstruction of the route I was working on from CPDs. Reasonable is defined as "better than nothing".

The program will run ok on a traditional disk if the SSD is found to be defective. Just a comment on the fragility of what we rely on for entertainment.:'(
 
Well, for now it not only works, it works better. This is after a TRS22 rebuild. I have to try TRS19 next. Strangely all of the temperature readings are within the tolerance range (88c avg) Yesterday, and before, I was at the Thermal Junction Maximum of 98c. Never came close. Outside temperature is 70f so not exactly cold. Yesterday hitting the temp Max was normal. Note: at that point clock cycles seem to be skipped to preserve the CPU. Trainzers in the UK & Europe must be very nervous about running in their conditions. I was in Europe one hot summer and it ain't dry heat. Those old buildings that have strong historical value make great tinder. Well, off to try TRS19.

TRS19 did not do as well. More errors and missing items after extended rebuild. But despite the errors shown in the database the actual routes I looked at looked fine. So that was a success.

I am back to an "acceptable" level in both versions with low temperatures (for the season) and route effecting missing content not an issue.

Why the darn things kept insisting on a rebuild is not evident but strangely no harm and an improvement in both versions with lower load and thus lower heat. Heat was possibly why I had both mess up the database and multiple rebuilds. I was running maximum settings for evaluating my latest "improvements". Relying on the automatic CPU throttling is not a good idea unless you can set the trip-point your self which I could not.
 
Last edited:
I would recommend Hard Disk Sentinel, it's free to download and apart from nagging you to buy it, it carries on working and it will tell you pretty much if there is any problems with an HDD or SSD even down to suggesting a new Sata cable or checking it's seated properly for intermittent problems, which happened to me a couple of weeks ago, just changing the SATA lead sorted it.



https://www.hdsentinel.com/ You will often find a lifetime registered version on the giveaway sites by the way.
 
Last edited:
Will get that disk evaluator - THANKS

Now, after successful full extended rebuilds BOTH TRS19 and TRS22 request to start an extended rebuild. I deleted some large files but they still ask to rebuild YES, they are different databases but on the same Solid State Disc (SSD). It is only half full. This is a full 1 hour process each time I start the program. During the process there is no activity on the PC.

Ran Disk Evaluator - summary of the parameters was "Disk Perfect".
 
I had run TRS22 on a hard disk for evaluation. I moved it to the SSD , but original remained. So,now trying to use that old database. It is doing a Rebuild, but that is understandable.

If this does not work I'll download a new copy of TRS22 and put it on this hard disk with the database that is under Rebuild. Might work or it all goes up in smoke.
 
Ok, I kept the Program on the SSD but linked it to an older database copy that was on Drive F: conventional hard disk.Started Trainz 22 Latest version. It rab. Went through ver routs abd functions with no issues. Stopped the program removed it from the Stat Que and restarted - no problem. It did not try to rebuild the database, which was my original issue. Restarted a few times no problems. Program ran smoothly with both simple and larger routes, editing no issue. This was on a conventional "hard disc" at this time.

The original "perpetual ReBuilds" never re-occured. I am very surprised and pleased with the smooth operation on the hard disk. The actual program remains on the SSD which may be sustaining the smooth performance.
 
Back
Top