here I am diagnosing computer problems from 3000 miles away, and no clue as to the system...
I think your problem occurred after the machine crash, correct ? Then tech support worked remotely on your system, correct ? And other applications are now running, but not TOAW, correct ?
I suspect that the crash mucked up Matrix' serial ID checking - either the routine cannot find the id record, or its own index/history of checking, as that error was the source of the earlier reports with ERROR 200.
I think 3.4.202 is stand-alone. Else all those people who skipped the betas could not install it and then get surprised at how different 3.4 is. You may install all the previous betas; I kept them as separate installs when I upgraded, but I was playing some games at earlier versions during the beta process.
Ralph would know. Have you checked with him ?
If you want to retain 3.2, or any of the betas, I think you will have to rebuild your 3.4 TOAW directory incrementally -- loading 173, and then 191 or whatever until you load 202 on top of it. (All the while copying the 173 directory, and renaming it; and then copying the 191 directory and renaming -- if you want to preserve these older beta versions.) But if you do not want to preserve all these versions, I think you can skip them.
I recollect your running on an older system and Ralph helped in the past, so what I did may not apply to your system. Anyway, I do think it's the serial nbr checking, and that would be a Matrix support issue; I'd focus on resolving that first vs the installation steps.