This was mentioned in another thread and seems to have been very quietly slipped out
The release of that version changes the meaning of this page by 6 months and a year for the support of v8iSS4.
Strangely I have just had an email from Bentley confirming this release!!
f.mandoki said:Needing to install SS10 would mean half a day of work just to get all the settings back.
Custom toolboxes, links to function keys, dgnlib settings, you name it. We never managed to just install a new V8i version over an existing one without losing all personal settings. We did backup the old ones but some stuff we still needed to adjust.
Without knowing your V8i Installation setup, what I can tell you is that custom user settings & company standards are easily reinstated after an upgrade installation with next to no downtime at all. Typically your V8i Workspace folder will reside on a mapped network drive on a file server, this won't be modified in any way during installation of SS10. All those settings you mentioned are It's also common to have a custom shortcut with a command switch to tell MicroStation where your settings are stored (If you are unfamiliar with this, Open the V8i Help/Programmed Customizations/Command Line Arguments).
As an example, if I were to uninstall V8i SS4 and install SS10, once the installation is complete, the only thing I will have to do is open the properties of my custom shortcut and verify that the folder path to Ustation.exe is the same as it was to SS4. If its not, I just change it to what it needs to now be. Then I load MicroStation with the custom shortcut, open a dgn file and all my own user settings and company settings (not that I have any need for those currently!) are loaded and just as they were with SS4. The only loss of time is the time to uninstall SS4 and install SS10.
Or amend mslocal.cfg to point at the network workspace. A new install will overwrite it but you can just copy your custom version back over it.
Personally, I would advise against doing this as its not recommended to edit any of the default config files.
Instead, copy the mslocal.cfg to a suitable location in your custom Workspace and edit it as needed. It is this file which immediately pointed to by the command switch that i mentioned in my previous post (using -WC command switch).