Moderators:PDF-XChange Support, Daniel - PDF-XChange, Chris - PDF-XChange, Sean - PDF-XChange, Paul - PDF-XChange, Vasyl - PDF-XChange, Ivan - Tracker Software, Stefan - PDF-XChange
With any pdf loaded, I go to File|Export|Export to Image. Enter any destination file name. Hit the Export... button:
Dr Watson says
The application, , generated an application error The error occurred on 09/08/2011 @ 11:01:27.093 The exception generated was c0000005 at address 77C856F2 (StrStrIW)
Allegedly an error log has been written, but I've found nothing except the above.
We will need the exact settings you are using when exporting to image, and also if this only happens with a specific file - the file in question as well.
The easiest and fastest way for you to show us all your image exporting settings is to make a screenshot of the window with all the settings you use.
You will need to archive the files before attaching them to this topic, as image files can not be attached directly.
Same behaviour, I'm afraid, with current version of free Avast turned off.
Might it be related to the call to strstrIW reported by Dr Watson? I have a very basic Win2000 SP4, rebuilt after a system crash last week; it wouldn't surprise me if there's a bolt-on for WIn2000 that your application assumes is present - but in my case, isn't
Thanks for the update, but our Products do not rely on any additional components being installed on your windows and should work on a brand new fresh one just as well.
Lets see if the devs have any further suggestions.
Looks like version of Shlwapi.dll in your system was lower than 4.71 and therefore was problems when calling StrStrIW (function StrStrIW require Shlwapi.dll version 4.71 or later). After updating IE to version 6 Shlwapi.dll was updated as well and this resolved problem. Sorry that we frogot about this requirement, we are not using W2k for years.
Victor
Tracker Software
Project manager
Please archive any files posted to a ZIP, 7z or RAR file or they will be removed and not posted.
Lzcat - Tracker Supp wrote: After updating IE to version 6 Shlwapi.dll was updated as well and this resolved problem. Sorry that we frogot about this requirement, we are not using W2k for years.
I'm not surprised, and thank you for taking the trouble to confirm it. I dabble with software development myself, and ancient versions of shlwapi have bitten me in the past.