The 52779 assets aren't mine; if they are no longer available, there isn't much I can do about it. The P42s at this point are legacy assets, and I don't have any plans on fixing them.
It's also not fixing any content; it's just updating what is essentially a glorified spreadsheet that tells trains where all your content is & what it is. With a regular repair it's just scanning through everything & looking for places where the spreadsheet doesn't match your content collection...
Internet speed has nothing to do with a database repair, it's all happening locally. The typical factors that effect a database repair are your computer's specs & the size of your collection of content.
Is the repair status window actually doing things during these 11 hours, or is it hung up...
No earlier versions of Trainz had a completely different Content Manager software. Apparently it was developed by a 3rd party company & N3V didn't want to keep paying for the license so that's how we ended up with the one we have now. They both of their pros & cons; but the old software was...
I don't do anything special to keep track of them. If I'm running a train, I'm the engineer... I don't know what other trains are out there. If I'm setting things, I just use the built-in tools.