OIPI32 Runtime Error 50003 (OpenInsight 16-Bit Specific)
At 15 APR 2002 09:38:18AM Colin Rule wrote:
When running our application we get an error dialog titled 'OIPI32' with a message 'Runtime error 50003', 'Unexpected error'.
This occurs on a basic Windows 95 workstation.
Windows 98 and later are all OK with the same application.
We are running OIPI 4.01 Pro.
The manual states that OIPI32 is supported on Win95.
Loading back the OIPI 3.8 resolves the problem, but then the new features added to our application will not work.
Is OIPI32 really supported on Win95?
If so, any ideas as to the problem resolution.
Thanks
Colin
At 15 APR 2002 01:46PM Tony Splaver wrote:
Hi Colin,
This is a VB runtime error (not an OIPI error) that is extremely strange, and I could not find any reference to it in the error codes for VB. I have not tested the 32-bit version of the OIPI under Win95.
When does this error occur?
The printer control in the OIPI is optimized to work with the latest printer drivers, and it is possible that the printer driver on this Win95 computer is very old… so you should try updating the Win95 printer driver first.
Tony
At 19 APR 2002 09:11AM Colin Rule wrote:
Tony,
The error occurs when the application starts, ie when we START32.
The printer driver is current, HPL5, but as it has not even go that far I dont this this is an issue.
Any ideas?
Colin
At 19 APR 2002 12:07PM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site';return(true)]The Sprezzatura Group[/url] wrote:
Wasn't there a problem with HP5 drivers, esp. versions shipped outside the USA? I seem to remember the Revelation Reporter would hang if this driver was running.
[i]Celebrate CeBIT with Sprezz Local![/i]
At 22 APR 2002 10:52PM Tony Splaver wrote:
Colin,
I still could not find any reference to this specific VB runtime error. It may be necessary to run the debug/logging version of the OIPI, which may display more information about the specific error code.
There may be a problem with the installation of the VB runtime dependencies (COM DLLs, OLE2 DLLs). If you can manually uninstall and manually install the OIPI, then we can eliminate the possibility of DLL version problems with the VB runtime dependencies.
Tony