Can print PS file but not make PDF

Question

Printing to a PostScript printer with a customized PostScript driver in WordPerfect 5.1 for DOS is what we do every day, but when we print the same job to a PS file we can't make a PDF in Adobe Acrobat Pro 9.4. What can we do to make a PDF? Here is the error message from Distiller:
Processing prologue.ps...
Done processing prologue.ps.
%%[ Error: rangecheck; OffendingCommand: setpagedevice; ErrorInfo: InputAttributes --nostringval-- ]%%
Stack:
-dict-
-save-
%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%
If I knew what to edit in the PS file to make it print a PDF, that would be one workaround. But I'm very curious why our printer (HP LaserJet 4050 with a Level 2 PostScript emulator) will print a file that Distiller won't process. Here is the only place in the PS file that mentions setpagedevice:
/manualfeed true put usertime 5000 add {dup usertime lt {pop exit} if} loop <</InputAttributes <<31<< /PageSize [612 792] /MediaType (Standard) >>/Priority []>> >>setpagedevice << /PageSize [612 792] /MediaType (Standard) >> setpagedevice _bp 0 13200 10200 _ornt /PlantinR 400 _ff
0 13200 10200 _ornt
"612 792" is, of course, the page size in points
Trying to make the PDF from the the PS file that was meant for another PostScript printer (HP LaserJet 2200D), we get the same Distiller error message. This time the PS file contains:
letter <</InputAttributes <<-1<< /PageSize [612 792]  /MediaType (Standard) >>/Priority []>> >>setpagedevice << /PageSize [612 792]  /MediaType (Standard) >> setpagedevice _bp 0 13200 10200 _ornt /PlantinR 400 _ff
0 13200 10200 _ornt
This passage from the 2nd attempt has much in common with the first PS attempt. What does Distiller mean by the InputAttributes having "nostringval"? What stringval would work?
By substituting this from an uncustomized driver that does work,
letter statusdict begin true setduplexmode false settumble end _bp 0 13200 10200 _ornt /PlantinR 400 _ff
0 13200 10200 _ornt
and by removing an offending command BRst, a PDF is created. But it doesn't have any of the special fonts that were downloaded. Still, that's progress.

Answer 1

Thank you. The first line of the PS file is "%!PS-Adobe", so I conclude that the origin of the uncustomized PostScript driver was Adobe; WordPerfect Corp. supplied it to purchasers of their software. Uncustomized (except for new Type 3 fonts), the PostScript driver still works splendidly for creating PS files that are easily distilled into PDFs. We only use Adobe software for this purpose.
By editing parts of the problem PS file I am just now able to get the PDF. But it requires replacing the following on every page:
letter <</InputAttributes <<-1<< /PageSize [612 792]  /MediaType (Standard) >>/Priority []>> >>setpagedevice << /PageSize [612 792]  /MediaType (Standard) >> setpagedevice _bp 0 13200 10200 _ornt /PlantinR 400 _ff0 13200 10200 _ornt
with this:
letter statusdict begin true setduplexmode false settumble end _bp 0 13200 10200 _ornt /PlantinR 400 _ff0 13200 10200 _ornt
I will continue working these codes. It ought to be possible to get paging codes that are less laborious to replace or otherwise get working, and obviously some of the codes can be eliminated.
We're not in a position to give up our highly customized driver for mathematical logic printing on paper until a volume of historical text is finished. Smoother produced PDFs must be possible for an electronic edition.
The other snag I mentioned, "BRst", came from a text file of "pskeys" that was to be downloaded with the job. It works when I simply insert pskeys.txt into the PS file.