Joined
·
93 Posts
That's perhaps a file permission problem. The WIS databases (if you can call them that) are basically small websites held inside ZIP files.This new WIS has begun to manifest some interesting issues.
Two days ago I got this when attempting to open it, many, many times:
I rebooted and the issue apparently resolved.
This morning, when I tried to open it, I got the "Please wait while Windows configures Workshop Information System" so the program appears to be reinstalling itself.
So, I am uninstalling this and going back to the cactuz version, which appears to be much more stable. It does not have NG 900, but at least I don't have to reboot to use it, or go through the too long re-installation process if rebooting does not work.
When you try to look at an article (for arguments sake, lets say "9-5, 2002, Basic Engine, Engine block", the relevant ZIP is extracted to C:\Program files\WIS\Work. The html file is then loaded along with any images.
This doesn't work quite like this on Windows Vista and up (don't forget this program was written for XP 32 bit NOT Windows 10 x64). Microsoft tightened the security of the file system to stop programs writing to each others Program files folders. What happens now is that these files are redirected to a Virtual Store folder in your user area.
For whatever reason, either the ZIP wasn't extracted or your computer then looked in the wrong place for them (ie extracted to the Virtual Store but then looked in the real Program Files folder).
I did play with the idea of having the installer modify everyones file permissions in the Program Files (x86)/wis folder but decided against it in the end.
As for why the Aniversary Update messes up the installation, I have no idea why. That said however, the Aniversary update currently being rolled out by Microsoft is practically another OS install so I`m not surprised that some stuff gets messed up.
If I ever get a copy of the 9-2X WIS, I`ll sit down and re-do the entire installation. I`m fairly sure that I can turn off the MSI repair feature as the chances are that the installation is fine, it's just that the MSI installer got it's knickers in a twist and decided to re-install the program.
I have since noticed that the program needs to install for EVERY user on the computer, this is probably due to the ActiveX extensions for the .CGM viewer and the Toledo ISO view program. This also might be the issue if people disable the ActiveX controls (WebCGM) or run Registry Cleaners (don't get me started on those things!)
Frank.