three small bugs I found while using XnView

Ask for help and post your question on how to use XnView Classic.

Moderators: helmut, XnTriq, xnview

zsoltpen
Posts: 1
Joined: Sun Apr 03, 2022 2:33 pm

three small bugs I found while using XnView

Post by zsoltpen »

When I start XnView Classic on Windows XP, I get an error message that says, "xnview.exe - Entry Point Not Found
The procedure entry point InitializeCriticalSectionEx could not be located in the dynamic link library KERNEL32.dll."

After I click on OK, the error message goes away, and I can use the program without any further error messages, so this is not a critical bug, but it's just an annoying thing.

Another completely different issue: WBMP and XBM decoders have bugs. But they are not critical bugs. They just make it impossible to view certain pictures. Some WBMP photo editors save the image width and height as one byte, while others save the width and height as type uintvar. This inconsistency requires a special algorithm that also checks the file size to determine the correct image size. XBM files are C source code files. XnView makes very little effort to try to read the C source code as C source code. It expects its input in a certain format, and if you do anything differently, it won't display the image. Also, it does not seem to support the hotspot feature of XBM files.
User avatar
xnview
Author of XnView
Posts: 37750
Joined: Mon Oct 13, 2003 7:31 am
Location: France

Re: three small bugs I found while using XnView

Post by xnview »

zsoltpen wrote: Sun Apr 03, 2022 2:42 pm When I start XnView Classic on Windows XP, I get an error message that says, "xnview.exe - Entry Point Not Found
The procedure entry point InitializeCriticalSectionEx could not be located in the dynamic link library KERNEL32.dll."
Try to remove the webp or openexr plugin
Another completely different issue: WBMP and XBM decoders have bugs. But they are not critical bugs. They just make it impossible to view certain pictures. Some WBMP photo editors save the image width and height as one byte, while others save the width and height as type uintvar. This inconsistency requires a special algorithm that also checks the file size to determine the correct image size. XBM files are C source code files. XnView makes very little effort to try to read the C source code as C source code. It expects its input in a certain format, and if you do anything differently, it won't display the image. Also, it does not seem to support the hotspot feature of XBM files.
could you send me some sample files?
Pierre.