OIPI and Windows Resources (OpenInsight Specific)
At 16 MAY 1999 06:48:43PM Tony Lillyman wrote:
Has anybody had extensive experience with Anthony Splavers OIPI
I mean programming with it in code.
How do you handle starting and stopping OIPI without consuming ALL your windows resources.
Any assistance appreciated.
Tony
At 17 MAY 1999 12:00AM Don Bakke wrote:
Tony,
We use the OIPI exclusively for all of our form/report needs. Anybody who uses S/List is also using OIPI, albeit indirectly.
What version of the OIPI are you using? The later versions working under Win95/Win98 don't give us resource problems. Under Windows 3.1 it did.
At 17 MAY 1999 04:41AM Tony Lillyman wrote:
Don
I'm using V3.6. I tried to load v3.8 but got al sorts of
problems so I re-loaded v3.6
I don't use SLIST at all - only OIPI with Set_Printer , Get_Printer
My logic is …
When I call my print manager screen..
- I do a Get_Printer(VERSION) to see if the OIPI is running. If it is I kill it with a TERM,2
Then I re-INIT it as a fresh session, as I only want to interrogate the printer for settings papaer etc.(I suspect this is what is feeding the blank page on the HP4000This ensures the OIPI is clean and runningThen I TERM,2 is to clear the OIP from memoryWhen I Start printing my reports..
- I re-INIT the OIPI (with the Preview Hidden if Preview is selected) which loads a fresh OIPI
Then I send my Set_Printer instructions checking Status after each and if negative call errors and then goto TERM,1at the End of printing I close with a TERM,1 which allows the preview to be seen and keeps OIPI in memoryshould they decide to Print from the PreviewWhen they close the Preview OIPI is unloaded.This appears to ensure no OIPI is left in memory after each report.
Would I be getting resource consumption with this approach ?
TIA
Tony
At 17 MAY 1999 09:22AM Don Bakke wrote:
Tony,
We too still use 3.6.
If you TERM,2 a lot then it is possible to consume your resources as the OIPI has small leak. So if this is a constant necessity then the memory program Jim Vaughan spoke of might help.
However, we rarely perform a TERM,2 - only when the entire application is being closed down. Why exactly do you need to do this?
At 17 MAY 1999 05:10PM Jim Vaughan wrote:
I use www.memturbo.com on my machine to make sure that any memory leaks get reclaimed.
Not really a solution but it does make the problem go away.
At 17 MAY 1999 06:49PM Tony Lillyman wrote:
Don,
I was experiencing *regular* GPFs / invalid operation errors when I was printing my reports.
*Regularly* OIPI would hang the client's computer.
When I was following the logic of my previous post, if I tried to INIT the OIPI a second time it would just freeze.
My "solution" was to ensure OIPI was unloaded every time by checking at the beginning and if it was TERM,2 it then re-INIT it.
Now it's (very) possible, I''m not approaching my printing from the exact right angle or that there is some fundamental step I'm overlooking.
Maybe you could have a look at the offending programs and see where I'm going astray ?!?
Could you spare a couple of minutes ? I could email them to you ?
TIA
Tony
At 17 MAY 1999 11:49PM Don Bakke wrote:
Tony,
Feel free to e-mail them to me.
If there is any way you can strip out application/data dependent code that wold be great. If the programs rely on current data from a form then just assign your variable used to hold the record data with hardcoded sample data.
At 18 MAY 1999 04:51AM Oystein Reigem wrote:
Tony,
What were you printing when you had problems with GPF/ill op? I had an obscure problem with BMPs. (And I've had problems with decimal characters - in Norway we write "3,14" instead of "3.14".)
What problems did you have with 3.8? There are several issues with installation of OIPI, but I haven't had any problems with running 3.8.
I see from my code I use TERM 1 when everything seems normal, but TERM 2 if an error occurred. Don't remember details any more, but I probably did it for some good reason, or perhaps on advice from Tony Splaver himself.
- Oystein -
At 18 MAY 1999 08:08AM Tony Lillyman wrote:
Thanks Don
Will send as soon as I can.
Tony