This Forum is for the use of Software Developers requiring help and assistance for Tracker Software's PDF-Tools SDK of Library DLL functions(only) - Please use the PDF-XChange Drivers API SDK Forum for assistance with all PDF Print Driver related topics.
I finished implementing your library into our application. I tested the application on Window NT, XP, 2K, and 98 and the PDF was created fine. I then tested on Windows ME. The images and text are missing from the PDF file. Anything to do with drawing lines appears OK. The function PXC_AddFontA is returning an error code of 0x8204271b(PXC_ERR_INVALIDFONT). I am specifying the font "Arial". In addition, the function PXC_AddImageA returns an error code of 0x83f40078.
I have attached a test project that demonstrates this problem. Are you able to reproduce this? Any help would be greatly appreciated.
I verified that the unicows.dll wasn't on the Windows ME system. I also verified the same problem happened on Win98 with the unicows.dll missing. But when I added the unicows.dll to the ME system and my application will not run. I get the error
ProgramX has caused an error in PROGRAMX.EXE.
ProgramX will now close.
The error seems to be happening during the loading of the librarys, InitInstance() is never called. This only happens on my ME system. The Windows 98 system works fine.
My test app doesn't have this error though. I tried adding the DLL to a previous version of our application (pre the PDF library) to see if we had a problem before adding the PDF Library but in that case everything worked fine.
Thanks for trying, I have searched the system and that is the only UNICOWS.DLL. If there was another UNICOWS I would figure the error would occur all the time but if I remove the UNICOWS.DLL in the local directory the error goes away. The data and time of that UNICOWS.DLL are the same as the screen shot I uploaded earlier.
I'm assuming there is something that is installed that is conflicting or something that needs to be installed on that ME system. Figuring that out will be the trick. Do you know if the UNICOWS.DLL requires any other Microsoft DLLs?
I'm quite confused then. We found another PC running windows 98 SE that experiences the same problem. But a windows 98 SE system I have been using for a while works fine. As soon as we remove the UNICOWS.DLL, the app runs but of course the PDFs have problems. I have added messages in InitInstance() and the messages never appear.
We have found where the crash is created but do not understand. It is in some special math code of ours that works normally but not when the UNICOWS.DLL is loaded on some win98 and winME systems. Anyhow, I do not think you need to do anything at the moment. We will try to figure out a solution.
We share some code with embedded systems and they have a case where we do a float divide by zero. The value (1.#INV or 1.#IND) are used to check if there is invalid data being used. It seemed that when the UNICOWS.DLL is loaded the floating-point exceptions are unmasked but only on some Win 98 and Win ME systems. We solved it by doing a _fpreset() which masks all the floating point exceptions. This solved the problem but we were unclear why this was happening on only some systems. After some more research, we found the following thread on google groups.
Others have experienced this problem and there is a comment about it happening when there is a HP printer connected to the system. FYI, The systems we have troubles with here have HP printers connected to them.