Can LeadTools 12 save PNGs on a 64-bit system?

Can you confirm whether PNG files work (or not) on a 64-bit PC, using LeadTools ver. 12?

I am using the DLLs, C++ interface. My program is a 32-bit application. When I call  L_SaveFile(FILE_PNG) on a 64-bit system, the program crashes. The program works OK (is able to save PNGs) on a 32-bit system.

The program also crashes while saving GIFs on a 64-bit system.

It works OK with BMP and JPG (both 32- and 64-bit systems).

I would prefer not to upgrade if I can postpone it.

Leadtools 12




OSJPG
BMP
PNG
GIF
32-bit
OK
OK
OK
OK
64-bit
OK
OK
Crash
Crash

Note: I am including LFPNG12N.DLL and LTKRN12N.DLL (otherwise it would fail on 32-bit platforms).

Also, I don't want the 64-bit SDK, my app is 32-bit.

I added the following code to a program that uses LEADTOOLS 12.1 headers, LIBs and DLLs and compiled it on a Windows 7 64-bit PC using Visual C++ 6:
+============================================+
BITMAPHANDLE Bitmap = {0};
L_CreateBitmap(&Bitmap, TYPE_CONV, 800, 600, 24, ORDER_BGR,
   NULL,     //LPRGBQUAD pPalette
   TOP_LEFT,
   NULL,     //L_UCHAR L_FAR*pData
   0);       //L_UINT32 dwSize
L_FillBitmap(&Bitmap, RGB(255, 130, 180));
L_SaveFile("e:\\Test\\out.png", &Bitmap, FILE_PNG, 24, 2,
   0,       //L_UINT uFlags
   NULL,    //FILESAVECALLBACK pfnCallback
   NULL,    //L_VOID L_FAR * pUserData
   NULL);   //pSAVEFILEOPTION pSaveOptions
L_UnlockSupport(L_SUPPORT_GIFLZW, "sg8Z2XkjL");
L_SaveFile("e:\\Test\\out.gif", &Bitmap, FILE_GIF, 8, 2,
   SAVEFILE_OPTIMIZEDPALETTE,
   NULL,    //FILESAVECALLBACK pfnCallback
   NULL,    //L_VOID L_FAR * pUserData
   NULL);   //pSAVEFILEOPTION pSaveOptions
L_FreeBitmap(&Bitmap);
+============================================+

The program worked and it saved 2 files, one GIF and one PNG. If the same code doesn't work in your project, please send your toolkit serial number to support@leadtools.com and ask for latest v12 setup and patches.
Important note:
Please do NOT post your serial number here.

Our DLLs do not specifically call this software. However, from the exported functions list, it appears to be a COM object of some sort, which means it gets registered on your system and is probably being accessed by some other process in the system through its COM interfaces.

I don't know for sure why this DLL is causing problems with our toolkit and since v12 is out of production, there is little we can do other than offering you the latest patches to try.

If a similar problem is active with the current version 18 of LEADTOOLS, we can ask our engineers to investigate it.