VuePro32 Crashing

I've been using VuePro32 for years as a pic viewer/editor. After installing Dopus v10 on my 64bit Win 7 Ultimate, I can no longer run the program. When I attempt to run it, I get the error, "Unhandled Exception" "Create fail for window VuePrint, 0, TVuePrintWin." The curious thing is that the program continues to run properly from Windows Explorer.

Has anyone experienced this problem or know of a fix?

According to http://www.hamrick.com/upg.html:

"If you're using Windows 7, Vista or 64-bit XP, you might need to turn off Data Execution Protection (DEP) for VuePrint."

I suspect that's what you are running into.

Personally, in most cases I would stop using the software rather than turn off a useful security feature, that has been part of Windows for several years now, to use it. Especially with image-viewing software where DEP can save you from maliciously crafted images that exploit buffer-overflow bugs in image-decoding libraries.

It doesn't sound like VuePrint can do anything that Opus doesn't do itself anyway.

[quote="leo"]According to http://www.hamrick.com/upg.html:

"If you're using Windows 7, Vista or 64-bit XP, you might need to turn off Data Execution Protection (DEP) for VuePrint."

I suspect that's what you are running into.

Personally, in most cases I would stop using the software rather than turn off a useful security feature, that has been part of Windows for several years now, to use it. Especially with image-viewing software where DEP can save you from maliciously crafted images that exploit buffer-overflow bugs in image-decoding libraries.[/quote]

I did try setting DEP both on and off with no effect on the program's ability to execute. Both ways it runs under WE and both ways it cannot under Opus.

I agree that there are a number of similar programs but this is one utility that I've used for years and have become very proficient at using. I just hate to have to quit using it, or having to use WE in order to use it.

Since VuePrint is the thing that's crashing, you'll need to contact the manufacturer of that product for support with it.

I just installed it in a Win7 x64 VM, which had DEP off for non-system processes (the default).

VuePrint worked fine when launched from both Explorer and Opus.

I then turned on DEP for all processes and rebooted the machine.

VuePrint now crashes with same error message you're seeing, in both Explorer and Opus.

So I'd say that's definitely the problem, and it's probably only luck (probably some random memory-layout fluke depending on how the program is run) that means it's working for you in Explorer.

You're right, it was a fluke. I hadn't tried the reboot thing but after reading your advice, turned off DEP and rebooted. Progress!! But, the wrong kind. Now it won't work in WE either. It does seem to be installation specific because it works just fine on other computers too with Opus.

Thanks anyway, for your ideas and support.