PDF XChange Forum

Hello Peter,
Please check if you can reproduce the problem on Windows 10 with "2017-07 Cumulative Update for Windows 10 Version 1703 (KB4025342)" installed (see Settings->Windows Update->Update History).

We have hope to see it working?

Yes, we have created an internal ticket on this issue.

the editor is not working when i use a Link URL with #page=

Do you mean File->Open From->URL function?
Can you please give me an exact link you have a problem with?

Hi samuele diella,
Yes, the Editor currently does not support viewState property for write.

Hello Christensen,
This is a known case. The issue is caused by a system bug. You have an interim version of a system file. Microsoft has already fixed it.
See here for details.

Hello Christensen,
Please unzip the attached file to an empty directory and run it there. The file contains a script to collect version information of some your system files.
Send us the Output.txt file this will generate.

I gave you a fix derived from the latest release (build 322.4) code branch, as you told us that you need the fix asap for the upcoming release of your product. 322.18704 is a code revision from our development (trunk) branch. The trunk will eventually originate the next 323 release branch. Of course...

Also this build removed a function Alex added for me in 6.0.322.18704

Are you aware that 18704 is an untested preview (alpha) version that should not be used in a public release of your product?

prime clinical systems wrote:Is there any progress regarding this post?
https://forum.pdf-xchange.com/ ... 66&t=28826

I have to consult other guys to give you the answer - this question is a bit away from my sandbox.

No problem, Clifford, glad to know it is fixed. You probably did this DLL replacement without closing VB6 IDE. In this case the same old DLL remained loaded into the VB6 process - Windows just kept mapping it to a renamed file.

I could not reproduce the crash with the updated DLL and your fresh test project. Please follow this guide to create a memory dump of the crashed VB6.exe process and send it to us (zipped). The dump file will most probably exceed the limitation of this forum for attachments, in this case please uplo...

Hi Clifford, Please verify that the issue has been resolved in the updated binary (see the attached file). Replace the original DLL in the Editor SDK installation directory (the default path is %ProgramFiles%\Tracker Software\Editor SDK\bin\) with the unpacked DLL. Make sure you did not move and re-...

Hi DolphinMann, This is most probably because SDK FullDemo is a 32-bit application. 32-bit application is limited not only in total available memory. Multiple opened ducuments make application memory highly fragmented and limit contiguous memory chunk size that could be allocated. This in its turn m...

Hi Philip,

I guess you can use IPXC_Document::SrcInfo.DispFileName or IPXC_Document::SrcInfo.ActualFileName property.

Hello, Probably the most portable way (across al supported WIndows versions) to this would be to use WMIC - this is a command line utility to access the system configuration through WMI interface. This is a sample batch file that detects if any printer with a given driver name is installed: wmic pri...

Hi Peter, It seems that this dump is unrelated to the crash - it is a dump of a normally working Editor process. Probably the editor was restarted after the crash. Please follow these instructions to create a new memory dump. Alternatively, we can arrange a remote debug session (see here for details...

Hi Peter, Please provide a memory dump of the crashed Editor process. To do this when you see the error message (the first one from your post) please Open Windows Task Manager (by pressing Ctrl+Shift+Esc), select "PDF-XChange Editor" on the Applications tab, and select "Create Dump Fi...

Hello vivekpatel, As you can see this is an end user forum. PDF-XChange Editor does not provide such a facility to end user. So the answer to your request here is "this is not possible to do" . It is possible for a developer to do this using PDF-XChange Editor SDK. If you are a developer p...

Hi Chris,
The issue has been resolved. The fix has been included in the upcoming build 321 of the editor.

Hi Charu,
Please provide us with a memory dump of the faulting process when the crash occurs.
Here are the details.

And please try the latest build of the editor SDK (319) - the problem might be already fixed.

Hi Jeff, your question has been forwarded to the installer team.

I sent it again, with the attachment encrypted.
There is no virus in the binaries. Gmail just disallows executables in attachments.

Guillermo, did you receive my e-mail with the debug binaries and instructions? I sent it to your forum e-mail address.

Hi Mark,
Yes it should work now. The documentation on this property is outdated.

Hi Guillermo,

I am preparing a debug build on this issue. I expect to finish it tonight.

John,
I could not reproduce the issue with the preferences. Using Wine 1.7.28 (64-bit). What is the build number and the platform (32, 64-bit) of the PDF-X Editor you are using?

Hi John, The preferences are stored in the registry under the key you have found yourself: HKEY_CURRENT_USER\Software\Tracker Software\PDFXEditor\3.0\Settings But only options with non-default values are actually stored in the registry (this is done for optimization). For example, if you change some...

Ok, I will do with an enlarged file. In fact, I tested printing in the way you described - from an external application (Windows Photo Viewer). Do you run 32- or 64-bit Windows 10? But it is strange that you cannot print with manually launched pdfSaver process. Please forcibly end the running pdfSav...

I could not reproduce the problem with your file. Probably it is specific to the way your application prints this file.
Please provide an appropriate temp file (PDF-XChange printer generates a temp file for each print job).
Here are the instructions.

Please zip the temp file before uploading.

Hi markoa,
We have downloaded the file and will try to reproduce the issue. We will let you know the outcome soon.

Hi Wouter,

Thanks for the info. I am preparing a custom build to collect more info what happens with the printer on your machine.
By the way, is a live remote debug session possible on your machine?
Here are more details.

Please give me the output of the following command on your machine (enter it in the Command Prompt window): powershell "(gi $env:systemroot\system32\spool\drivers\x64\3\mxdwdrv.dll).VersionInfo | fl" Also please confirm that the problem exists when printing a small text document from Windo...

Hi Wouter,

What is the result if you print a document of another, smaller page size? Say, A4 or Letter. Still the same fixed output page size (220 x 110mm)?

Unless you want to change the existing (modified by the user) printer settings (i.e. not just setup the settings 'from scratch' (based on the hard-coded printer defaults)), I do recommend using a .reg file with the latest additions from my post above. Because the old .reg file to work correctly must...

We left the registry name unchanged for backward compatibility. Agreed it looks awkward. Like 64-bit kernel32.dll in Windows. :) And I thought {079FD97E-8382-482B-9A09-30D25094ABCB} would be different now in version 6. You can use any GUID. It is the identifier of a new printer settings profile you ...

Hi Jeff, The bug was that "SystemProfile" registry value was not updated after the printer settings modification (done by the driver). Therefore when you modify the "system profile" data in the registry, the result will be like your changes are not applied to the printer. Now it ...

Hi Jeff, The issue has been fixed. Until it is released please use the following .reg file as a workaround: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Printers\DevModes2] "PDF-XChange Lite V6"=- [HKEY_CURRENT_USER\Printers\DevModePerUser] "PDF-XChange Lite V6"=- [HKE...

Hi Jeff,
It seems to be a bug in the recent version of the driver that breaks this technique. I am working on this issue. We might provide you with a custom build, if unable to find a reliable workaround.

Hello Andy,

The printing fails because the sample file contains an embedded PostScript data and Adobe Digital Edition EPUB reader tries to pass this data directly to the printer.
PDF-XChange does not support embedded PostScript in print job.

Hi Michael, Recent PDF-XChange Lite printer uses another rendering engine that does not support paper scaling natively. Although we plan to implement this feature, it will not be present in the next release. For now please consider using a precomputed (custom) paper size according to the required sc...

Please follow this post.

Hello,
Did you customize your TEMP directory location?
Please run System Information utility (msinfo32.exe), select Software Environment->Environment Variables, then export the selected content to a file (File->Export...).
Send us the file.

Sorry - it seems I can see it due to my admin privileges on the forum.
I emailed to you.

Please e-mail it to me (press "EMAIL" button below my post).

Can I have a remote debug session on your machine (see the details here)?
I mean your VM.

Did you try the unmodified C# demo ("%ProgramFiles%\Tracker Software\PDF-XChange 6 API\Examples\Bin\C#\PDFdriverAPI.exe" )?
Please check if pdfSaver6.exe has been updated ("%ProgramFiles%\Tracker Software\PDF-XChange 6 API\pdfSaver6.exe" must have file version 6.0.317.2).

I agree with you. We will discuss what can be done without breaking backward compatibility.

Andrew, try the attached fix.
Unzip the file to an empty directory and run Fix.cmd as Administrator.

Revert the C# demo source to its original state.

Hello andrewb,

The issue with events has been fixed and will be available in the next release.

In your case WaitForPrintEvent() fails due to used timeout (1 second). I agree the reported error is obscure, it will be more specific in the next release.

Hello omascia, Actually we use const strings wherever possible in our COM API internal definition. The problem is that we publish our COM API in the form of MS type library (TLB). It is universal and makes COM API available for most development environment at the expense of losing some information, ...

Hi Carsten, It is unlikely that the crashing process is csrss.exe. csrss.exe is a critical system process and Windows deliberately raises BSOD when it is crashed. I think Windows just reused process id of the crashed process for csrss.exe. I think it is also unlikely that the problem is caused by PD...

Search found 306 matches