PDF XChange Forum

I'm not sure if this is the right forum, but since I am an Network Administrator and this is an issue with a network shared printer installed installed on a print server, I figured I would post here.

We are starting to deploy Windows 10 workstations and I receive an error in PDF-XChange Editor v5.5 and v6.0 when trying to set printer properties for our Oce TDS600 large format plotter. I can send a print with no error, but as soon as I click the "Properties" button to change a setting it crashes. Everything worked fine on Windows 7, and the old version of PDF-XChange Viewer (v2.5.0315.0000) works fine on Windows 10.

The error from the event viewer is:

Faulting application name: PDFXEdit.exe, version: 6.0.317.0, time stamp: 0x56f2e254
Faulting module name: ocewpdoci.dll, version: 2.1.0.0, time stamp: 0x47f4ce59
Exception code: 0xc0000005
Fault offset: 0x000000000001649e
Faulting process id: 0x3634
Faulting application start time: 0x01d190ce3eef49df
Faulting application path: C:\Program Files\Tracker Software\PDF Editor\PDFXEdit.exe
Faulting module path: c:\windows\system32\spool\drivers\x64\3\ocewpdoci.dll
Report Id: a971533a-f230-474c-be2a-f199c2774c07


And as I said, this same error is produced when using PDF-XChange Editor v5.5. Here is that error:

Faulting application name: PDFXEdit.exe, version: 5.5.316.1, time stamp: 0x569d2cee
Faulting module name: ocewpdoci.dll, version: 2.1.0.0, time stamp: 0x47f4ce59
Exception code: 0xc0000005
Fault offset: 0x000000000001649e
Faulting process id: 0xfc4
Faulting application start time: 0x01d190cbda5889ed
Faulting application path: C:\Program Files\Tracker Software\PDF Editor\PDFXEdit.exe
Faulting module path: c:\windows\system32\spool\drivers\x64\3\ocewpdoci.dll
Report Id: 5fe1b878-3f45-40ac-be77-834068501a8a


It would be nice if this can be corrected because the TDS600 is our main large format plotter.

Hi pcchenard,

Thanks for the post - can you please take a look at this KB and advise if it appears to be the issue?
https://www.pdf-xchange.com/knowled ... properties

Thanks,

Yes, it does in fact error out if I try to access the printer properties from Notepad. Since there are no newer print drivers for the Oce printer (and probably never will be) would you recommend installing the 32bit version of PDF-XChange Editor on a 64bit OS?

Just for info...

Did you check the drivers on this page:
http://downloads.oce.com/ProductDownloads/Index/281

There is choice for Type = Drivers, Operating System = Windows 10 64-bit, Language = English UK

This offers an "Océ Adobe PostScript 3 driver" v1.26. Is that an old driver and/or not a 64-bit one OR is it a good one ?

I can not check this for myself (I have no Windows 10 64-bit, nor an Océ printer).

Best regards.

Yes, I have checked there. Our printer is not postscript capable. We are running the latest driver available.

Hello pcchenard,

Yes, it does in fact error out if I try to access the printer properties from Notepad. Since there are no newer print drivers for the Oce printer (and probably never will be) would you recommend installing the 32bit version of PDF-XChange Editor on a 64bit OS?

There is no problem in using the 32-bit Editor on a 64-bit OS. You can install it on a test machine and check if you are able to print with it.
You can also try with our portable version of the Editor, which is also a 32-bit application:
https://www.pdf-xchange.com/downlo ... rtable.zip

Regards,
Radi

I did try the 32-bit version and it works fine. Thanks.

Hi pcchenard,

It seems like the problem is indeed in the drivers of your plotter.

Please use our .msi installer when distributing the 32-bit version of the Editor as our .exe installer will always install the appropriate version (32/64-bit) according to your OS:
https://www.pdf-xchange.com/downlo ... V6.x86.msi

Regards,
Radi

I will.

I guess my only remaining question is why is this an issue with Windows 10 64-bit but not Windows 7 64-bit? At this point it doesn't really matter, I'll just deploy the 32-bit version of PDF-XChange Editor, but I am curious why it worked fine on one 64-bit OS and not the other.

Hello pcchenard,

Probably the drivers for the two OS are different (even if it's the same installation package - the drivers inside could be different), and one of them is working better than the other.

Regards,
Stefan

Hi guys,

Just to clarify something - what Radi said about the 32-bit Editor isn't strictly true: the 32-bit MSI should not actually install on a 64-bit operating system. While the Editor seems to, we cannot guarantee that it will work 100% correctly.

Thanks,