Picking up on Kari's observation (LPT1.asc holds the PS codes), there's an apparent solution for direct printing of PS files (no screen pdf), which involves a slight alteration to the pcl6 direct print method, courtesy of Edward Mendelson.
Download the Sumatra portable pdf reader and put the .exe file in the vdos directory. Then add one of these lines to the config.txt:
LPT1 = "pclprint.cmd" HIDE #LPT1.ASC [for the June 2016 vdos build]
Or
LPT1 = @pclprint.cmd #LPT1.ASC [for pre-2016 vdos and vdosxy3)
Then create the following batch file, pclprint.cmd, and move it into the vdos directory:
@echo off
cd /d %~dp0
GSWIN32C.exe -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=PCLPRINT.PDF "%1"
SumatraPDF.exe -print-to-default PCLPRINT.PDF
del PCLPRINT.PDF
PS print jobs will now go directly to the printer. In brief testing, it worked without incident.
From: Kari Eveli
To: xywrite@xxxxxxxx
Sent: Monday, August 22, 2016 10:10 AM
Subject: Re: concept of a Xy PCL driver for producing standard Postscript
There is more: In Xy3 using the PS driver, TY command produces a
#LPT1.asc file that can be distilled, and a #LPT1.txt file that causes
the DOSPrinter dialog to show. The #LPT1.txt file has a FF FE Byte Order
Mark at the beginning and the file is not a PS text file, it is UTF-16,
little-endian.
Can the ASC file be directed as input for the GhostPCL process?