[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]


==== OIPI Question.  SSUTIL.OCX (OpenInsight 16-Bit Specific) ====
=== At 11 SEP 2002 12:05:56PM b cameron wrote: ===
 
{{tag>"OpenInsight 16-Bit Specific"}}
 
<QUOTE>
I have searched the online discussions and knowledge base for information on the OIPI error '367' Can't load (or register) custom control: SSUTIL.OCX, which we are getting from users running on NT workstations.



The only posts I found referenced running the register routine from windows\system.  I have tried this but did not get it to work.



Our app. is OI (16 bit).  Does anybody have any information or suggestions.  I have noticed posts and information regarding 

START32 and STOP32.   Would this help?  Can I put this into the

Create/Close event of the app. entry window? What is the correct

syntax as I tried call start32 but did not try call set_printer("START32","").   Will this even help?



Thanks
</QUOTE>
----

=== At 11 SEP 2002 02:03PM Donald Bakke wrote:  ===

<QUOTE>Bruce,



What version of the OIPI are you using? Was this a pre-Revelation version (i.e. Splaver Softare) or post-Revelation release?



dbakke@srpcs.com

[url=http://www.srpcs.com]SRP Computer Solutions, Inc.[/url]



[img]http://www.srpcs.com/srpicon1.gif[/img]

</QUOTE>

----

=== At 11 SEP 2002 05:49PM Richard Bright wrote:  ===

<QUOTE>In SYSTEM Monitor try



RUN SET_PRINTER "START32"



or in stored proceedure





$Insert OIPrint_Equates

Declare function Set_Printer, MSG



Stat=Set_Printer("START32","","")

if stat # 1 then

      x=msg(@Window, 'An error occurred during Set_Printer START32 operation. |Error is ':stat)

end

*------*



(of cause OI 4.1 has great HTML help which explains this.)

Regards Richard Bright

</QUOTE>

----

=== At 11 SEP 2002 06:33PM Matthew Crozier wrote:  ===

<QUOTE>Sometimes we've had to do this by brute force - unregistering it, copying over a new copy, then registering it again:



	REGSVR \WINNT\SYSTEM\SSUTIL.OCX /U

	Copy the SSUTIL.OCX again

	REGSVR \WINNT\SYSTEM\SSUTIL.OCX



M@

</QUOTE>

----

=== At 11 SEP 2002 11:50PM b cameron wrote:  ===

<QUOTE>Thanks for the responses!



Don,

I believe it was as pre-oi release of oipi.



Bruce

</QUOTE>

----

=== At 12 SEP 2002 03:16AM Oystein Reigem wrote:  ===

<QUOTE>Bruce,



Run OIPI.EXE by itself and it tells you which version number it's got.



- Oystein -

</QUOTE>

----

=== At 12 SEP 2002 08:46AM Donald Bakke wrote:  ===

<QUOTE>Bruce,



Then I would simply try to run the original OIPI setup program. You should be able to use the one Revelation has available for download but I can send you a Splaver Software version if you want it. It would be good to get the exact version number as Oystein suggested, but I wonder if running OIPI.EXE will work if you SSUTIL.OCX control is not working right.



dbakke@srpcs.com

[url=http://www.srpcs.com]SRP Computer Solutions, Inc.[/url]



[img]http://www.srpcs.com/srpicon1.gif[/img]

</QUOTE>

----

=== At 13 SEP 2002 01:15PM b cameron wrote:  ===

<QUOTE>Don,



Thanks, I found out (once they coughed up all the information) that many users were not set up and that only some of the required Dlls

were present.  Seems to be under control now.



BC

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=041AA5AE1E009D0885256C3100586F24|View this thread on the  forum...]]