PDF XChange Forum

Hello Fips, As a preliminary steps, could you please do the following: Make a screenshot of the error message when printing from Notepad. Check if the notepad main window is responsive (try to enter some text there) while the error message is displayed. Run Event Viewer (Control Panel->Administrativ...

Hello, The issue has been investigated and will be addressed in the next release of the editor. Until then, please set Edit->Preferences->Performance->Maximum number of working threads allowed option to be equal or more than 2 (but not more than the double number of the machine CPU cores). This shou...

The profile subkey in the registry is created after some custom settings have been made to the printer (until then the printer keeps using hadrcoded defaults). SystemProfile value references a system per-user printer settings profile (i.e. per-user printer preferences) and is generated at run time. ...

Hi Jeff,
Yes, it is available. See my previous message (I updated it).
HKEY_CURRENT_USER\Software\Tracker Software\PDF-XChange Lite 5\Printers\Profiles\SystemProfile registry variable contains GUID of the printer data profile that corresponds to per-user printer preferences.

ChocolateFactory wrote:But ONLY if run from a console window, right-clicking the CMD file and running it as an administrator is not enough.

Thanks. Fixed it (updated the attached ZIP above).

Thank you. I have updated the ZIP a little, so please download it again. Also if you have installed the editor you could try the steps above just to make sure this tool is working for you. Please remember that you must always start those steps with an empty directory. So to avoid future errors, dele...

Hi, Next time when you get this trouble please do the following: 1. Keep the error message window open. 2. Unpack the attached ZIP file into an empty directory (it should be on the drive that has at least 100 MB of free space). 3. Go to that directory, right click pxe_dump.cmd file and choose "...

Hi,

The issue has been fixed. The fix will be available in the upcoming maintenance update of the editor.

The only thing which troubles me are messages in the terminal immediately below the wine call: [...] You may ignore these messages until something wrong happens to your application under wine. Wine does not implement Win32 API completely but in many cases those implementation deficiencies are not i...

am@linux-il0q:~/wine_new/drive_c> wine /home/am/wine_new/drive_c/Program Files (x86)/Tracker Software/PDF Editor/PDFXEdit.exe bash: Syntaxfehler beim unerwarteten Wort `(' Bash requires a path containing spaces to be enclosed with qoutation marks: wine "/home/am/wine_new/drive_c/Program Files ...

Hi Arno, Please try to install the editor into a fresh wine installation (~/wine_new is a sample choose any empty/non-existing directory): WINEPREFIX=~/wine_new wine msiexec /i PDFXVE5.x86.msi During the installation please choose 'Custom' option and remove (deselect) Tracker Update from the compone...

Hi Arno,
The crash is due to insufficient implementation of a Windows system function in WINE.
The issue will be fixed in the next build of the editor.
For now please use 32-bit version of the editor under WINE.

Hi Arno, Here is the installation steps. Some prerequisites. WINE msxml6 implementation has a defect that can affect the editor. So install native msxml6 library first. The easiest way to do this is using the attached script file. Download it, go to the download directory and run bash install_msxml6...

Hi cPdfViewerUser,

Could you confirm that version 2.5.210 is not supported on 8.1

Yes.
Registration-free COM activation of the viewer has been made compatible with Win 8.1 in build 213.

Hi cPdfViewerUser,

While deleting my own irrelevant message (where I insisted on my previous request for the memory dump) I accidentally deleted your one.

I am sorry.

Anyhow please follow Vasyl's direction. If remote debugging session is feasible there is no need for dumps.

Hi cPdfViewerUser, I could not reproduce the issue with the latest (2.5.311) version of the viewer SDK. Please provide a memory dump of the crash along with your PrintDocument.exe, PrintDocument.pdb files. The crash dump file can be created with Visual studio (2012 or later) debugger attached to the...

Hi cPdfViewerUser,

In the demo you have provided you use a very old version of PDFXCviewAx.dll (2.5.200). The latest version (2.5.311) should work correctly.
As a general rule all components of the viewer should be of the same version to ensure correct work.

Hi Peter,
Thanks for confirmation.

peter altherr wrote:i only had to manually configure wine to use the native msxml6.dll instead of the builtin

You could also use winetricks script for this - it would install the native msxml6 and setup the DLL override "under the hood".

Hi Peter,
It seems that native 64-bit MSXML6 has some problems installing under 64-bit WINE.
While we are investigating please use 32-bit version of the editor. You will have to create a separate win32 WINE prefix for this. Install native (Windows) 32-bit MSXML6 there as mentioned above.

is there anyway to know the name of the {UNIQUE_NAME} key There is currently no documented way to know this. But in the upcoming build 311 there will be a special value for this: HKEY_CURRENT_USER\Software\Tracker Software\PDF-XChange Lite 5\Printers\Profiles\All\SystemProfile = {per-user devmode p...

Hi Jeff, Just after the printer installation you will have only single profile entry under HKEY_CURRENT_USER\Software\Tracker Software\PDF-XChange Lite 5\Printers\Profiles\All\. Additional 'service' profiles will be created with time to reflect the fact that some applications store printer settings ...

Hi Peter,
This is because of insufficient built-in MSXML6 implementation in WINE.
As a solution you can install native (Windows) msxml6 library under WINE. The simplest way to install is using winetricks.

Hi ds1,

We have found a most probable cause of this issue.
The fix has been checked in and will be available in the upcoming build of the editor.

Hi Tim,

We have found a most probable cause of this issue (the crash dump information is not sufficient to be completely sure).
The fix has been checked in and will be available in the upcoming build of the editor.

Thank you, Tim.
We will investigate this issue and will provide a solution unless it will appear to be a flaw in WINE that is difficult to workaround.

Hi Tim,
Could you please provide your PDFXEditCore.x86.dll? It should be in "C:\Program Files\Tracker Software\PDF Editor\" directory (under WINE) if you used the editor installer with default settings.

Thanks for the info, Nick. Please verify that HKLM \Software\Classes\PXCComLib.CPXCControlEx registry key is present on your system. As Ivan mentioned, it would be better to get remote access to your system and do live debugging. Site forum has too big lag to be used as an efficient debug channel. :)

Hello Tim,

Please choose to not install Tracker Update component in the installation options.

Hi Nick, Assuming you are using MS Visual Studio as your dev environment, what is the version of your IDE? that's also worrying: view.h(25): warning C4192: automatically excluding '_FILETIME' while importing type library 'AAF4C859-3ACD-4D27-88E6-B163C8D81 This warning means the #import detected that...

Hello Tim,

Please try to install the editor from the MSI package. You can download it here.
Select "32 bit MSI Installer" download option.

Hi ds1,

Please download build 309 anew, reinstall and provide crash dump when you face this issue again.
Thanks for the previous crash dumps - they are very useful to us.

Hi ds1,

Could you please provide your PDFXEditCore.x86.dll? It must be in "C:\Program Files\Tracker Software\PDF Editor\" directory (under WINE) if you used the editor installer.
I suspect it is broken or has wrong version.

Hi Ds1,

While we are investigating the issue here, please install the editor without TrackerUpdate (select 'Don't install' for the 'Tracker Update' component in the 'Custom setup' mode).

Suppose this issue would then be replicable on pre-SP1 systems on W7x64 & Haswell (or AMD64)?

Yes. And also on Windows 7 SP1 when AVX is disabled on boot (through bcdedit /set xsavedisable 1).

CodeSatori,
If you have run bcdedit /set xsavedisable 0 (see my previous post), please make sure you have also installed this hotfix from Microsoft.
This is important if you debug applications on your computer.

Hi CodeSatori, Thanks again. The problem is that your CPU reports support for FMA3 instruction set but does not support it really. I see the following possible reasons: 1. Broken CPU (maybe an early experimental revision?). 2. FMA/AVX instructions execution is disabled at system or BIOS level. Pleas...

Hi CodeSatori,
Thanks for the test.

Please do one more test:
Unpack the attached cputest.zip and run unpacked cputest.exe from the command line:
cputest.exe >cputest.txt

Then send me the cputest.txt.

Hi CodeSatori,

Please do the following:
1. Unpack attached cpu.zip into an empty directory. Go to that directory (make it current).
2. Run get_cpu_info.cmd from that directory. You should get cpu_info.txt file there.
3. Send that cpu_info.txt to us.

Hi ds1,

ds1 wrote: The crash that occurs when doing File - Export - Export to Images - Options is a bigger issue now.

This crash has been fixed.

hi ds1,

ds1 wrote:The crash that occurs when doing File - Export - Export to Images - Options is a bigger issue now.

We have reproduced this and are working to fix it.

ds1 wrote:the file I gave the link too actually crashed the program after moving the scrollbar button back and forth about 15 times.

Hi ds1,
While we are trying to reproduce this bug here, could you please give us the call stack dump (as you did in the first post) when you get such a crash next time?

Hi ds1,
The issue has been fixed. The fix will be included in the next public build.

Hello Hans-Peter, Sorry for so long investigation period. Partly it is for the highly specific repro conditions that was rather confusing to me. :) The problem actually was that a WinAPI (GetShortPathName) does not work as expected under these conditions. We have changed our code so that this API is...

Hello Hans-Peter,

Please try again (the same download link, the zip file has been updated).

Hello Hans-Peter, Please try to reproduce the problem with this test set (zip includes 32- and 64-bit builds). Just run OpenDocument.exe and open a pdf file with it). if you get a crash please make a memory dump of the failed process (you can use Task manager for this) and send the dump file to us. ...

Hello Hans-Peter, I have setup the configuration you described (WinServer 2012 as a terminal server (with UPD enabled), WinServer 2008 Std as a DC/AD) but could not reproduce the issue - regless activation works even in directories within UPD-based user profile. Could you please prepare a standalone...

Hello Hans-Peter, Is it possible to arrange interactive remote debug session on the problem server? For example we could use TeamViewer to access the server. The only requirement is internet access from the machine - there is no need for public IP, port forwarding, disabling firewall or so. However ...

[deleted]

Hello chesscourt, While we are awaiting for more info from you, here is an instruction assumed your system is Windows 7 or later. Please do the following steps next time when you experience this crash: Open Task Manager (Press Ctrl+Shift+Esc) Go to 'Applications' tab, locate crashed PDF-XChange Edit...

Hi Jim,

If you don't mind me asking what was the fix?

There was a rare condition that in some cases resulted in access to an object in an 'inconsistent' state (specifically - in the process of destruction).

Search found 306 matches