oipi32 - HELP! (OpenInsight 16-Bit)
At 13 AUG 2004 11:05:08AM Michael Norton wrote:
I know OIPI32 on OI 16-bit is a bit of an old chestnut but I appear to have a different spin on it (or I am completely missing the point!).
Have WinNT server, Win2000 Clients, upgraded to OIPI32 looks to run correctly, and taskmanager shows OIPI32 becomes active when users acccess main menu (has START32 in it). BUT STOP32 crashes (first time it is used after reboot) and SYSPROCS does not have DLL_OIPI_USER32! ALSO to use print functions from system crashes with REGISTERWINDOWMESSAGE.
Have re-run set-up repeatedly with no joy.
At 13 AUG 2004 01:18PM Toxteth O'Grady wrote:
Replied to my own message simply so that it becomes more promenant in the list - Mike Norton
At 13 AUG 2004 01:40PM Sean FitzSimons wrote:
Michael,
See the following:
Sean
At 13 AUG 2004 03:09PM Michael Norton wrote:
Thanks for that Sean, but I have already found that thread and unless I'm missing something obvious that solution is a little further down the line that I am currently. I can perform the deletes and the system already has START32 and STOP32 but what I don't have is STPROCS DLL_OIPI_USER32 so that I can perform
RUN DECLARE_FCNS 'DLL_OIPI_USER32'!
I donlt understand how OIPI32 appears to be running in the windows stack whilst I do not have this item in STPROCS which I would have been essential to a successful upgrade!
Yours in a confused state………
At 13 AUG 2004 03:22PM Sean FitzSimons wrote:
Michael,
I misread your original post. I thought you working on OI 32 as well as OIPI32. OIPI32 will start but cannot communicate with OI unless the DLL prototype is there. Can you copy the DLL_OIPI_USER32 record from your OI 32-bit system into your OI 16-bit system and then run the declare_fcns?
Sean
At 13 AUG 2004 03:33PM Michael Norton wrote:
Hi Sean, no worries.
I'm not on site now but I did try what you suggested and the DECLARE_FCNS failed with some very odd errors which I'm afriad I do not have to hand. I also noted that DLL_OIPI_KERNEL32 was missing on site and tried editing it in with similarly successful results!!!!.
Do you have any idea why the setup.exe is not putting these SYSPROCS in place, it calimed to have run successfully.
At 13 AUG 2004 05:56PM Sean FitzSimons wrote:
Michael,
Can't seem to tell why the records were not created. The strange messages could occur if declare_fcns was done from an account other than sysprog.
Sean
At 16 AUG 2004 06:04AM Michael Norton wrote:
Hi Sean,
The message I got when I tried to edit into place the DLL_IOPI_USER32 was something about it not liking or recognising UINT as arguement for GetNextWindow.
All very strange - any ideas on best way forward on this one?
At 16 AUG 2004 09:59AM Donald Bakke wrote:
Michael,
I believe the problem lies in the fact that you are using OI32 DLL parameters types within an OI16 application. That's why UINT isn't recognized.
I think you need to do what Sean recommended except that you shouldn't borrow the DLL_OIPI_KERNEL32 from an OI32 system. I suggest you do the following:
1. Delete all references to DLL_OIPI_KERNEL32, DLL_OIPI_KERNEL, DLL_OIPI_USER32, and DLL_OIPI_USER.
2. Re-install OIPI32. Make sure it is a download designed for OI16 and not OI32.
3. Then log into SYSPROG and do the RUN DECLARE_FCNS command for DLL_OIPI_KERNEL32 and DLL_OIPI_USER32.
dbakke@srpcs.com
At 16 AUG 2004 01:05PM Michael Norton wrote:
Thanks Don, I'll check our OIPI library and give it a go.