Bug 693431 - gs32winc.exe has stopped working
Summary: gs32winc.exe has stopped working
Status: RESOLVED INVALID
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: General (show other bugs)
Version: 8.60
Hardware: PC Windows 7
: P4 normal
Assignee: Default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-06 16:09 UTC by georgiosgogas
Modified: 2012-11-08 12:26 UTC (History)
0 users

See Also:
Customer:
Word Size: ---


Attachments
message that shows when PDF is created (31.27 KB, image/png)
2012-11-06 16:09 UTC, georgiosgogas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description georgiosgogas 2012-11-06 16:09:20 UTC
Created attachment 9058 [details]
message that shows when PDF is created

Using Powerbuilder 12.5 and trying to save a report as PDF. This functionality works fine in windows Vista but not in Windows 7.

What happens is when running the process of creating the PDF the actual PDF is created but a message shows (se attachment). To continue creating more PDF's user has to close the message to continue.
Comment 1 Ken Sharp 2012-11-06 17:48:19 UTC
(In reply to comment #0)
> Created an attachment (id=9058) [details]
> message that shows when PDF is created
> 
> Using Powerbuilder 12.5 and trying to save a report as PDF. This functionality
> works fine in windows Vista but not in Windows 7.

We don't have anything to do with Powerbuilder or Sybase, did this functionality get shipped with the product, or did you add Ghostscript separately ?

8.60 is extremely old, the current shipping version of Ghostscript is 9.06. However, it seems likely that your 'save as' functionality is actually printing to a PostScript virtual printer, and using RedMon to redirect that to Ghsotscript, which is configured to use the pdfwrite device, and converts the PostScript to PDF.

I know that current versions of Ghostscript support Windows 7 (as I'm using Windows 7 here) but I believe that old versions of RedMon do not, as Microsoft changed the printing architecture. You could try upgrading Ghostscript and see if that cures your problem.

If Sybase supplied you with this functionality we would be interested to hear of it, though in this case we would probably suggest that you contact them directly for support with this feature.

As it stands we are unlikely to be able to help you as you would need to be able to supply us with the PostScript file being used as input to Ghostscript, and the configuration parameters, which you probably won't be able to do if the facility is buried inside another application (Powerbuilder).
Comment 2 georgiosgogas 2012-11-07 17:06:20 UTC
(In reply to comment #1)
> (In reply to comment #0)
> > Created an attachment (id=9058) [details] [details]
> > message that shows when PDF is created
> > 
> > Using Powerbuilder 12.5 and trying to save a report as PDF. This functionality
> > works fine in windows Vista but not in Windows 7.
> 
> We don't have anything to do with Powerbuilder or Sybase, did this
> functionality get shipped with the product, or did you add Ghostscript
> separately ?
> 
> 8.60 is extremely old, the current shipping version of Ghostscript is 9.06.
> However, it seems likely that your 'save as' functionality is actually printing
> to a PostScript virtual printer, and using RedMon to redirect that to
> Ghsotscript, which is configured to use the pdfwrite device, and converts the
> PostScript to PDF.
> 
> I know that current versions of Ghostscript support Windows 7 (as I'm using
> Windows 7 here) but I believe that old versions of RedMon do not, as Microsoft
> changed the printing architecture. You could try upgrading Ghostscript and see
> if that cures your problem.
> 
> If Sybase supplied you with this functionality we would be interested to hear
> of it, though in this case we would probably suggest that you contact them
> directly for support with this feature.
> 
> As it stands we are unlikely to be able to help you as you would need to be
> able to supply us with the PostScript file being used as input to Ghostscript,
> and the configuration parameters, which you probably won't be able to do if the
> facility is buried inside another application (Powerbuilder).

Hi

I managed to test this case separately and got the same result.

From cmd prompt i used the following parameters:

"gswin32c.exe" -q -dNOPAUSE -dBATCH -dSAFER -sDEVICE=pdfwrite -sOutputFile="C:\Users\sew-ggogas\Documents\test.pdf" -c .setpdfwrite -f "GGGGGGG"

What I´m doing is executing the same command a couple of times. After some iterations the program crashes and the same message (that I attouched) shows up.

No access from Powerbuilder at all. I run on a windows 7 32-bit
Comment 3 Ken Sharp 2012-11-07 17:26:16 UTC
(In reply to comment #2)
 
> What I´m doing is executing the same command a couple of times. After some
> iterations the program crashes and the same message (that I attouched) shows
> up.
> 
> No access from Powerbuilder at all. I run on a windows 7 32-bit

We would still be interested to know if this facility was supplied with Powerbuilder or if you installed Ghostscript yourself.

If you are genuinely using Ghostscript 8.60 then my advice remains the same, upgrade to a version somewhat less elderly (current version is 9.06). Version 8.60 is 5 years old now, the pdfwrite device has changed dramatically in that time.

If the problem persists with the current version then you will need to supply us with an example file and command line to execute that will exhibit the problem (as noted in comment #1).

The attachment basically says 'program stopped working', which isn't actually very useful.
Comment 4 georgiosgogas 2012-11-07 17:40:11 UTC
(In reply to comment #3)
> (In reply to comment #2)
> 
> > What I´m doing is executing the same command a couple of times. After some
> > iterations the program crashes and the same message (that I attouched) shows
> > up.
> > 
> > No access from Powerbuilder at all. I run on a windows 7 32-bit
> 
> We would still be interested to know if this facility was supplied with
> Powerbuilder or if you installed Ghostscript yourself.
> 
> If you are genuinely using Ghostscript 8.60 then my advice remains the same,
> upgrade to a version somewhat less elderly (current version is 9.06). Version
> 8.60 is 5 years old now, the pdfwrite device has changed dramatically in that
> time.
> 
> If the problem persists with the current version then you will need to supply
> us with an example file and command line to execute that will exhibit the
> problem (as noted in comment #1).
> 
> The attachment basically says 'program stopped working', which isn't actually
> very useful.

I Installed the ghostscript by myself. I even tried with version 9.06. Same message.

Here is the scenario:

Start a cmd prompt and try to create a PDF-file with the following parameters:

"gswin32c.exe" -q -dNOPAUSE -dBATCH -dSAFER -sDEVICE=pdfwrite
-sOutputFile="C:\Users\sew-ggogas\Documents\test.pdf" -c .setpdfwrite -f
"postscriptfile.ps"
Comment 5 Ken Sharp 2012-11-07 19:51:21 UTC
(In reply to comment #4)

> I Installed the ghostscript by myself. I even tried with version 9.06. Same
> message.
> 
> Here is the scenario:
> 
> Start a cmd prompt and try to create a PDF-file with the following parameters:
> 
> "gswin32c.exe" -q -dNOPAUSE -dBATCH -dSAFER -sDEVICE=pdfwrite
> -sOutputFile="C:\Users\sew-ggogas\Documents\test.pdf" -c .setpdfwrite -f
> "postscriptfile.ps"

You still haven't supplied a file which will reproduce the problem. As the maintainer of the pdfwrite device I do this a lot, and on a Windows 7 system too, and I don't have a problem.

Our regression system runs thousands of files (on Linux systems of various flavours) without a problem.

If we can't reproduce the problem, we will not be able to address it....
Comment 6 Ken Sharp 2012-11-08 12:26:41 UTC
Georgios Gogas appears to be a developer at Sybase.

While Sybase's use of Ghostscript in this fashion is legal, we can hardly be expected to approve of it, and I'm amazed that the *Enterprise* version of Powerbuilder requires its users to install an open source application for such functionality.

I don't think we want to extend any support to covert Sybase employees, if Sybase want support then they can at the very least pay for a support contract, if not a full commercial licence for Ghostscript.

With this additional information, the lack of a specimen file, and an inability for us to reproduce any problem, I'm closing this as invalid.