System Editor++ and Windows 7 (OpenInsight 32-bit Specific)
At 12 JUN 2010 05:32:07AM John Godfrey wrote:
Anyone else having problems making this run? The old system editor is fine. Black text on a white background. The ++ editor gives a bluish background with no text displayed. .ini settings perhaps but what should they be?
At 12 JUN 2010 05:42AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
You have to regsvr the scivbx.ocx with admin privileges.
World leaders in all things RevSoft
At 12 JUN 2010 09:49AM Eric wrote:
And mistype and mispronounce the filename several times.
At 13 JUN 2010 04:21AM John Godfrey wrote:
Thanks everyone
At 13 JUN 2010 08:14AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
That too :( :)
World leaders in all things RevSoft
At 16 JUN 2010 03:27PM John Godfrey wrote:
Also exposed extra security settings in W7 that have to be cracked to make this work. Probably explains why not installed correctly in the first place.
At 27 JUN 2010 07:00AM John Godfrey wrote:
Rounding Up - See the following notes in the Knowledge Base -
OpenInsight 9.0 Workstation Installation Notes
I am not a systems engineer so I did the following hacks to get the ocx to install. In case anyone else hits this prob this is what I did. Rightly or wrongly.
RWM etc access was greyed out. I saw that Windows files were all set as read only. Tried to make them accessible by removing Read Only switch - didnt work. Tried reinstalling Client files Running as Administrator. Still didnt work. Tried to remove read only access again. This time it worked. Set RWM etc switches to allow amendment. Copied the OCX into System32 directory. Ran regsrvr32 again and this time it worked. I dont know how. I got System Editor++ working again. Why did I need it? To edit Revmedia and copy in new dict items.- may have been able to use old syseditor but couldnt remember how to fire it up.
Hope above helps anyone else with this problem when out on site with a customers Vista /W7 machine. Not the perfect answer I realise.
At 14 JUN 2011 09:30AM Mark Marsh wrote:
Ive seen this issue too, But for me installing the OI client fixed it. Look in OI folder and run the clientinstall.exe.