Those who hope to use Microstation 8.5 nowadays must resort to Windows XP on virtual machines for incompatibilities with Windows 7, much worse on 64 bits. They mention the Problem with text editor, which I talked about earlier how to solve it and also refer to the image manager and the ODBC connection. Let's see how these issues are resolved.
Problem with Raster Manager.
It is not a matter of discussion why people continue to use this 10 version years later. The certain thing is that Microstation V8 of the year 2004 was all innovation. People loved this version because of the potential after suffering with the last few years with a dgn that was still 16 bits. Now I was able to read and edit the dwg / dxf file of AutoCAD 2006 natively, it integrated the historical save, it left on the one hand the painful MDL language, adopting Visual Basic for Applications (VBA) and of course exploited the potential of the dgn v8 that already it was not limited to 64 levels or number of objects.
Despite the above, the development of the tool was still on Clipper, with a limited graphical interface in the handling of transparencies and in the interaction of the cursor, it made a kind of refreshing in the form of an image that returned the object in a black tone. But outside of these things, having an environment of its own that was not proportional to the computer's RAM, in an impressive way could handle large amounts of data efficiently.
Bentley promised to release a "really windows" version, promising not to damage the potential. It was so that in 2006 the XM series appeared, although strangely people asked themselves why they announced it with a message of «not being the last thing, and waiting for something more». It was until a couple of years after V8i appeared, that it brought everything that Bentley now exploits under the concept of i-model.
Of course, that version is obsolete with what can now be done with Bentley Map or any version of Microstation V8i. But if someone developed on VBA for that version, it will not be easily changed if the program meets their basic needs; much less if the development was on a vertical as the case of Microstation Geographics, ProjectWise, Geoweb Publisher, or if it exploited dgn functionalities of that date as the historical.
Bla, Bla, Bla ... history. Let's see how to solve the problem:
Going back to the issue of the Raster Manager problem. Everything is in the change in the handling of Microstation cache, which was defined in different variables, including MS_RASTER_CFILE_FOLDER.
For XM Bentley integrates a different management, and of course the change of folder locations that comes after Windows XP makes it impossible to reach the cache ... much more with 64 bits where the rights are more complex in certain folders. But the functionality exists because it does not happen with primitive files like jpg, only happens with compressed files, like .ecw .hmr or .tiff.
The easiest way to resolve the issue is by copying the file Hrfecwfile.dll, which is what solved this in the first tests we did of Microstation XM.
So, what is required is to search the Microstation XM Internet, install it, and search for this file. Then it is replaced in the location where the common files are:
C: \ Program Files (x86) \ Common Files \ Bentley Shared \ RasterFileFormats \ ECW \ hrfecwfile.dll
With this you can call attach, but when you drag and drop it hangs. To solve this, you have to disable the visual themes in the composition of the desktop.
Problem with the Microsoft Access ODBC driver in 64 bits
In the case of users of Microstation Geographics, it was very robust to connect to a database through an Oracle Driver, Microsoft Access via ODBC. Although Geographics is obsolete with respect to Bentley Map, it is still used by many projects, to the extent that it is not strange to see even in the Be Inspired developments using these functionalities.
The problem for those who do not usually read, is that in Windows 7 on 64 bits can not make an ODBC connection to Access or Excel.
If we access the ODBC connection in a traditional way:
Start / Control Panel / Administrative Tools / System and Security / Administrative Tools / ODBC Data Sources
You can see that you can only add drivers for SQL Server. But this is because the first alternative is to execute this from 32 bits, so administrator permissions are not enabled in the Odbcad32.exe file of the address
C: \ Windows \ System32
In theory you could activate the properties on the right button and modify the execution rights as an administrator, but in some cases could not allow it, so that,
What we do is look for the same command but under the 64 bits environment, in the path:
C: \ Windows \ SysWOW64
Here we look for the command Odbcad32.exe. And in effect, when executing the command we see all the options that we expect.