Well, difficult to say, what happened in your case. If you start an image (VA803 - therefore the client installation process went fine) and you get errors I would think, that the 8.0x code did not make its way into the repository file you would like to work with or the newly image wants to connect to.
During installation of the manager-part of VA the system seems to look for a specific manager.dat filename (mgr80.dat ?) and then import the newly (VA803) code into this already available mgr80.dat (before that you get the question if you have backed up your repository ...). Depending on the first version of VA you have installed on your system I assume that it might look for mgr60.dat or mgr70.dat or as mentioned above: mgr80.dat - but this is just a guess.
I tell you, how I have done it in the past:
* I extracted the new ?.dat from the zipped-file.
* I used my old ?.dat (for example: originated from VAST 601 to include all OS/2 code)
* then I normally import the whole new ?.dat delivered with VAST 803 (the procedure to do that has been recently posted by Joachim Tuchel at http://joachimtuchel.wordpress.com/2011/02/08/use-the-library-importer-tool-to-upgrade-a-va-smalltalk-library/
) into my old ?.dat.
* then I change the abt.ini of my newly VA 8.03 to point to my old, but changed ?.dat
skydomine wrote:it happened when we tried to load the MGR0608.DAT. We use vast on windows platform. Thanks for your reply..