pdfview lister plugin

[CharlesF]

I've moved my TC installation to a new notebook and everything works except Florian's pdfview.wlx plugin. This worked on the old notebook and still does.

The only difference between the two installations is that on the old system the TC folder is in C:\. In the new notebook the TC folder is in C:\Tools.

I've made the changes in all the relevant .INI files to account for the folder change.

Anyone have any thoughts as to why pdfview.wlx will not work on the new notebook? (The error message generated is "Ghostscript could not convert document").

Regards,
Charles

[Wilhelm M.]

Do you have the UseIniInProgramDir=7 in your wincmd.ini? If so than TC uses the ini in the program directory. Otherwise just moving the TC installation to another directory or drive will always cause problems.
Another thought - where is ghostcript on the new computer? Are you sure that the plugin can find ghostscript?
"I've made the changes in all the relevant .INI files to account for the folder change. "
Has pdfview it's own ini file? Have you also looked there for required path changes?

[sqa_wizard]

You may compare the installed versions of Ghostscript.

I know about problems of Ghostscript 9 with 64-bit.
Workaround was a downgrade to Ghostscript 8.71.

[CharlesF]

Do you have the UseIniInProgramDir=7 in your wincmd.ini? If so than TC uses the ini in the program directory. Otherwise just moving the TC installation to another directory or drive will always cause problems.
Another thought - where is ghostcript on the new computer? Are you sure that the plugin can find ghostscript?
"I've made the changes in all the relevant .INI files to account for the folder change. "
Has pdfview it's own ini file? Have you also looked there for required path changes?

I don't have UseIniInProgramDir in wincmd.ini. I am starting TC with the /i switch pointing to the correct wincmd.ini file. All paths in the .INI file or correct.

Ghostscript is in C:\GS

pdfview does not have it's own .INI file (as far as I can tell).

Regards,
Charles

[CharlesF]

You may compare the installed versions of Ghostscript.

I know about problems of Ghostscript 9 with 64-bit.
Workaround was a downgrade to Ghostscript 8.71.

I'm running Ghostscript 8.51 on both new and old notebooks.

I may just move the TC folder back to the root if I can't find a fix.

Regards,
Charles

[Wilhelm M.]

All I can offer is this:
The readme.txt of pdfview says that in the lsplugin.ini there are stored some settings. The switch
exepath=<path to gswin32c.exe>
could be important in your case. Perhaps it points to a wrong location?

And there is always the possibility that ghostscript has problems with certain files. Does the error occur with all files?

[CharlesF]

All I can offer is this:
The readme.txt of pdfview says that in the lsplugin.ini there are stored some settings. The switch
exepath=<path to gswin32c.exe>
could be important in your case. Perhaps it points to a wrong location?

And there is always the possibility that ghostscript has problems with certain files. Does the error occur with all files?

Problem happens with all files on the new notebook. The same files are successfully "listed" on the old notebook.

I'll try adding the exepath line to lsplugin.ini.

Thanks.

[rschalie]

Could anyone provide me with an example ini file? For me it isn't created automatically during installation, and the readme file is not sufficient to create a complete ini-file.

Thanks in advance

[tuska]

Could anyone provide me with an example ini file? ...

%COMMANDER_PATH%\lsplugin.ini

Code: Select all

[pdfview]
command=-dSAFER -dBATCH -dNOPAUSE -sDEVICE=bmp256 -r%3 -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -sOutputFile=%2 -dFirstPage=%4 -dLastPage=%4 "%1"
exepath=C:\Program Files (x86)\gs\gs9.56.1\bin\gswin32.exe
resolution=210
;
; Source: https://ghisler.ch/board/viewtopic.php?p=408438#p408438 | Ghostscript: https://ghostscript.readthedocs.io/en/latest/
; EN: %COMMANDER_PATH% is the location where the TOTALCMD.EXE and/or TOTALCMD64.EXE file(s) are located.
; DE: %COMMANDER_PATH% ist der Ort an dem sich auch die Datei(en) TOTALCMD.EXE und/oder TOTALCMD64.EXE befinden.
; exepath= ... Customize this path ...
;
; command=-dSAFER -dBATCH -dNOPAUSE -sDEVICE=bmp256 -r%3 -sOutputFile=%2 -dFirstPage=%4 -dLastPage=%4 "%1" -l
; exepath=C:\Program Files\gs\gs9.56.1\bin\gswin64c.exe
; resolution=144
;
; Ghostscript - Command line options
; https://ghostscript.readthedocs.io/en/latest/Use.html#command-line-options
; [url=https://ghostscript.readthedocs.io/en/latest/Use.html#command-line-options]Ghostscript - Command line options[/url]

---

Ghostscript - Command line options