OI16 3.7.5 - How can I determine if OIPI32 is running?
Sometimes the START32 commands fails and the workstation starts OIPI, only. Since I'm printing image files, "BMP", I need to stop the process, tell the user to shut down and restart.
Dave-
Use Findwindow:
hWnd%=FindWindow("ThunderRT6FormDC":\0\, 0)
If the handle has a value, OIPI32 is running.
Mike
Thanks Mike. It occured to me that maybe I could just copy OIPI32.EXE over OIPI.EXE and would always have 32-bit available? What do you think?
It would be even better if there were no longer two version, you know.
Dave
Hi Dave,
Is this problem still occurring? This is a situation that I have not seen before. The OIPI will be in a very strange state if the START32 command fails, because the next INIT message may try to start the OIPI (16-bit) while it thinks it is in 32-bit mode. Do you think calling START32 after a failed attempt will fix this problem? How do you know the START32 failed – does it return an error code? You should be careful using the FindWindow("ThunderRT6FormDC":\0\, 0), because it will return a positive if any VB6 program is running. You should check the caption of the window handle returned by the FindWindow().
Tony
Dave,
I would not suggest copying the OIPI32.EXE over the OIPI.EXE. This would cause problems with the 16-bit version. Let me know if this problem is still occurring.
Tony
Tony,
I would not suggest copying the OIPI32.EXE over the OIPI.EXE. This would cause problems with the 16-bit version.
For various reasons, I deleted all occurence of OIPI.exe (16-bit).
If I'm using OIPI32.exe, why would I need the 16-bit version.
Appreciate your advise on this.
Thanks,
Ray
This is an elusive problem so I can't easily control when it happens.
However, I know it DID happen because first I print a scanned image to a page, a .GIF or .JPG file via the BMP message. Then, I document the image by printing a little TEXTXY box with the date received of the image. I get pages that have only the text box and otherwise blank. I include an error message in the text box if the BMP message returned a "file not found" error. The START32 is run when the operator starts the process, well before the PRINT button is pressed.
Hi Ray,
You can delete all references to the 16-bit OIPI, but you should not replace the OIPI.EXE with the OIPI32.EXE – this will cause problems with the OIPI in 16-bit mode.
Tony
Hi Dave,
A few more questions:
Can you determine if specific images are not printing, or do images that fail to print one time work correctly the next time? Once the problem occurs, do all images stop printing in the report once there is a failure? Have you tried downloading and installing the latest printer driver?
I'm not sure what to try next, but here are a few thoughts:
1. "The START32 is run when the operator starts the process" – Make sure you do not run the START32 message more than once (without calling STOP32 between).
2. Is the OIPI.EXE running when this error occurs? You might try deleting (not copying over) the OIPI.EXE – because then you will get an error on INITs that are called without first calling the START32. This will only work if you never plan on having the end users use the 16-bit version.
3. There is the possibility that there is a problem with the BMP message, and we may be able to get more details from the OIPI by using the debug version of the OIPI32. This will work best if you can reproduce the problem at your site.
Tony
Tony,
You can delete all references to the 16-bit OIPI… I deleted only OIPI.EXE and did not delete any other OIPI files. I just "assumed" that all 16-bit OIPI files were replaced. Any case, if they are there, should I delete them. If so, what are the specific names of 16-bit OIPI files? … but you should not replace the OIPI.EXE with the OIPI32.EXE – this will cause problems with the OIPI in 16-bit mode. Does OIPI still have a need to go into 16-bit mode? Excuse my ignorance. Thanks, Ray </QUOTE> —- === At 26 MAR 2002 04:01PM Dave Harmacek wrote: === <QUOTE>I posted a few more questions for you on the web site: 1. Can you determine if specific images are not printing, or do images that fail to print one time work correctly the next time? – This will help us determine if the problem is with specific images, or if the problem is within the OIPI or VSVIEW.OCX. I know that VB cannot always "import" all forms of GIF and JPEG files (I think some types of compression and other variations are not supported by VB). If the problem is with specific images, then please email us the images and we will test it out directly in VB. This morning I inspected the task list and found only OIPI32.EXE running, not OIPI.EXE. I inspected "My Computer" to make sure the drive containing all of these images was available, it was. So, instead of rebooting, I just re-started OI16 the exactly same way our Mailroom Guy did at 0500 this morning. Then everything has worked perfectly! So, there are no different version of GIF or JPEG. The images that failed worked fine the next run. 2. Once the problem occurs, do all images stop printing in the report once there is a failure? – If all images stop printing at a specific point, then we can look into this specific area of the BMP code. It looks like all BMP fail once there is a failure. However, TEXT and TEXTXY continue to work. Since I noticed a problem with the server drive that contains images not being found in My Computer I have the system first print an image using BMP. Then I have the Mailroom Guy wait and confirm that it printed. It printed just fine today. 3. Have you tried downloading and installing the latest printer driver? Does this problem occur on other computers too, or does it only occur on a specific computer? – I have seen very strange problems with the 16-bit version of the OIPI when using older printer drivers or the printer drivers from the Windows Setup CD, and I know that VideoSoft (the printer control vendor used in the OIPI) strongly recommends using the latest full-featured printer drivers with both the 16-bit and 32-bit controls (this is always the first thing they require before working on technical support issues). Yes, latest printer driver was installed. All failures are on the machine that ALWAYS prints these images, not my test version. That workstation is Win98SE. It only runs ARev and OIPI16. You should also consider the following: 1. "The START32 is run when the operator starts the process" – Make sure you do not run the START32 message more than once (without calling STOP32 between). It is in the CREATE and CLOSE events of the child window doing the printing. 2. Is the OIPI.EXE running when this error occurs? You might try deleting (not copying over) the OIPI.EXE – because then you will get an error on INITs that are called without first calling the START32. This will only work if you never plan on having the end users use the 16-bit version. I did not copy over because you said not to. </QUOTE> —- === At 26 MAR 2002 08:01PM Tony Splaver wrote: === <QUOTE>Hi Dave, Thanks for the great feedback and information about this issue. Looking back through this thread I did not realize that the OIPI returned a -2 every time the BMP message failed (I was still stuck on the OIPI16 and START32 issue). These images must be OK, because the same image prints one time and not another time. The BMP message will return a -2 if any unknown error occurs when VB tries to load the image – this will occur if the image file is missing or if VB cannot load the image. It seems very strange that VB cannot load these images sometimes. The OIPI "hides" the actual VB error code from the OIPI developer… so it would be helpful if Revelation could help you get a debug trace of this issue. This involves backing up the current OIPI32.EXE and installing a debug version of the OIPI32.EXE, and then sending us the OIPI.LOG file from the Windows directory. This debug file will give us the exact error code that is occurring when the image fails to load. Thanks for your continued help in resolving this issue. Tony </QUOTE> View this thread on the forum...