|
Post by LillaThrilla on Jul 8, 2011 13:07:32 GMT -5
Any dealt with Error 53 in TNM before?
Weeks ago I got an Error 53 while deleting moves. (I had less than 600 moves and less than 200 wrestlers.) I trashed my Moves database. If I ran TNM7DIAG, it would tell me my datbase was a mess then crash with it's own Error 53. I was able to use a Backup so I didn't completely lose everything.
Same copy of TNM (the one I use for WCW97) and the other day I booked Nitro. When I started the card, I got an Error 53 crash. I was able to get around it by Shutting Down Current Match (the Dark Match between Prince Iaukea and Brad Armstrong was alas lost). Rest of the card ran fine as did the subsequent WCWSN. TNM7DIAG says all is fine too.
I've messaged Oliver, but I was curious if anyone else has had problems like this.
|
|
Jake
Enhancement Talent
Posts: 1
|
Post by Jake on Aug 17, 2011 18:12:26 GMT -5
UPDATE: Starting a brand new circuit has solved my problem. Thankfully the original circuit was merely a test to begin with.
----------
Similiar experience just now except I have 400+ wrestlers, had 600+ moves. Loading TNM gave me a message about being 50+ moves over limit, so I set about deleting/combining moves (using the TNM UK site as a guide).
Tried to book a single match: Error 53 when I go to run.
Running the diagnostic shows NO PROBLEMS whatsoever.
Unfortunately, I have NO backups, and I really don't wanna reinstall and have to clean the move database again.
|
|
|
Post by LillaThrilla on Jun 14, 2013 21:03:24 GMT -5
I was just booking my 3rd card for a new circuit and TNM crashed on me with an Error 53. This is a different copy of TNM than my original post from 2 years ago. (Running in DOS-Box this time.) Thankfully, when I went back in and tried to book it again things worked just fine.
|
|
|
Post by mdale2k on Sept 4, 2013 14:02:15 GMT -5
I have the same problem after deleting moves and getting error 53.
So no real ideas eh?
|
|
|
Post by MarkusAEW on Sept 5, 2013 6:26:08 GMT -5
Did you use TNMdiag? There you can check if there is a problem with the database or the circuit.
|
|