Bug 690277 - PDF Creator + GS // Error
Summary: PDF Creator + GS // Error
Status: RESOLVED INVALID
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: PDF Interpreter (show other bugs)
Version: 8.64
Hardware: PC Windows XP
: P4 normal
Assignee: Alex Cherepanov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-09 00:05 UTC by Clive Sabey
Modified: 2009-02-09 06:54 UTC (History)
0 users

See Also:
Customer:
Word Size: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Clive Sabey 2009-02-09 00:05:14 UTC
Tow queries: Why a reg entry for Resources when no directory present?
Also, PDF Creator complains about a file called which is in 8.63 but not 8.64. 
Where has this file gone? gs_res.ps
Comment 1 Ken Sharp 2009-02-09 00:37:29 UTC
> Why a reg entry for Resources when no directory present?

I've just downloaded the Windows binary installer from SoureForge and installed
it. Checking the Registry I cannot find any reference for Resources in the 8.64
tree. I see that in HKLM\SOFTWARE\GPL Ghostscript there is an entry for 8.64
which contains three sub-keys; (Default), GS_DLL and GS_LIB. In 8.63 and earlier
the GS_LIB key would have contained a path for Resources, I don't see it in 8.64.

Please state exactly where you see the entry, and also please state where you
got the installer for Ghostscript 8.64.

> Also, PDF Creator complains about a file called which is in 8.63 but not 8.64. 

I think you will need to take this up with the developers of 'PDF Creator', but
see below.

> Where has this file gone? gs_res.ps

All the resources are now built into the Windows executable, as a ROM file
system, by default which matches the behaviour on other platforms. As a result
all files which used to be in the Resources directory are now contained in the
executable.

Note that if a specific Resources folder is specified on the command line with
the -I switch this will force the use of a different directory.

Possibly this is related to your problem with PDF Creator, and indeed possibly
also your registry entry, it may be specifying a non-existent directory on the
command line. Though I would have expected a different error.
Comment 2 Clive Sabey 2009-02-09 02:00:10 UTC
Thank you - I'll pass on the information to the developer.
Comment 3 Ray Johnston 2009-02-09 06:54:30 UTC
Closing since third party programs that rely on specific files or file locations
within Ghostscript are poorly designed, and not a valid Ghostscript issue.