Post by ivanI am not even sure you can view anything with GS
FWIW, I have two PM objects. GSview, and a GSPM.CMD file which is a
drop target. It's documented in 8.14's INSTALL.HTM file. It's not
(fully) documented anymore, including 9.15's README.OS2.
Post by ivanHere we have the following directory structure
I'm not using e:\tools\GS\fonts and e:\tools\GS\gs9.15\bin, because I
have only one version of GS installed, GS isn't my prefered name, we
don't have Unix' links to point to a single version.
FWIW/2, using your structure and names, I have repackaged 8.14 to move
the fonts directory to e:\tools\GS\gs8.14\fonts, removed the unneeded
8.14 layer and renamed GS to Ghostscript.
This requires a change of a GSPM.CMD directory parameter, which
assumes e:\tools\GS\fonts. The 8.14 (not 9.15) GSPM.CMD file would
be:
@E:\TOOLS\GHOSTSCRIPT\BIN\GSOS2.EXE
-IE:/TOOLS/GHOSTSCRIPT/LIB;E:/TOOLS/GHOSTSCRIPT/FONTS;C:/PSFONTS
-sDEVICE=os2pm -dBitsPerPixel=24 -sPAPERSIZE=a4 %1 %2 %3 %4 %5 %6 %7
%8
I'm also using GSview (in a mix-cased e:\tools\GSview2). IIRC I told
the GSview installer that my GS directory is e:\tools, and I had to
change (advanced) e:\tools\fonts in e:\tools\Ghostscript\fonts.
So 8.14 works (drop target, GSview) and I can apply 9.15's README.OS2
to my simplified or OS/2'ified directory structure, but one of the
undocumented changes was that "os2pm" no longer is a recognized
device.
FYI: 8.14's GSPM.CMD (object name Ghostscript 8.14, with a matching
icon) can display both PDF and PS files. There is no GUI. Just a
frame. If you want to view a PDF file with two pages, then the
text-mode UI of GSOS2.EXE will ask you to press <Enter> after each
page and it will display a new frame per page. The use of GSview may
be recommended, but GSview and its added value isn't required. The
text-mode GSOS2.EXE can be used too, at least with 8.14.
Post by ivanthere is an installer in that zip file but we
have not found the need to use it.
Same here. The GSview installer accepted e:\tools as the GS directory,
so it doesn't (and shouldn't) check paths. Apparently it copies the
files and assumes the (adjustable) parameters.
Post by ivanYou do need to read Paul's readme.os2 to know how to
setup gsview.
This was about GSOS2.EXE. I added and/or adjusted the directories,
a.o. the fonts directory ( e:\tools\Ghostscript\fonts), e.g. the
device-parameter isn't documented.
Post by ivanjust make sure you list the directories correctly and
you should not have any problems
Indeed. So far GS doesn't assume a fixed directory structure, and it
(including the GSview GUI) uses parameters. Excellent.
I could have used ...\Ghostscript\gs9.15\..., but then the empty 9.15
directory has no use. Now e:\tools or e:\tools\Ghostscript is a
backup-layer. So is e:\tools\GSview2. The only unusual problem is that
the e:\tools\Ghostscript\fonts directory can be reused, so I
shouldn't execute DELTREE e:\tools\Ghostscript\* to install a new
version. I didn't know that the fonts would be reused, but I haven't
resimplified that.
FWIW/3, my Ghostscript directory looks like this:
Directory of E:\tools\Ghostscript
[.] [..] [bin] [doc] [examples] [fonts]
[lib] [Resource]
8 file(s) 0 bytes used
In Unix I may have used the original structure, but we don't have a
clear "Ghostscript" link or shortcut to point to the right, current
directories. Hence the (off-topic) attempts to get rid of unneeded,
possibly unclear directories.
I'll (adjust, due to the different directories, and) try Dave's CLI
GSOS2.EXE-command to create a new, working 9.15 GSPM.CMD. In general
the use of GSview v5.0 is recommended, but this was about a GSOS2.EXE
drop target, ignoring GSview and whatever parameters GSview would use.
The old GSPM.CMD I've included above won't work with 9.15 and the
suggested changes of 9.15's README.OS2. GSOS2.EXE will produce at
least one remaining error message, because it rejects "os2pm" as a
device. If I'm right, then (coming from 8.14) that change wasn't
documented nor obvious. The error messages of GSOS2.EXE aren't that
clear too.
--
