...However....somewhat strangely enough, I am getting the following error out of PIN.EXE:
=== START ===
[G:\TEST\PSCRIPT]pin ppd \test\pscript\5470 \test\pscript\5470
PostScript resource packaging utility version 1.00
Copyright (c) IBM Corp. 2000,2001. All rights reserved.
Producing Printer Device PAK
reading driver extended attributes
fail
SYS0005: Access is denied.
fail
=== END ===...
Well, this is embarrasing...notice my "pin" command above, for some reason my problem was the fact that the last parameter is a fully qualified reference to the PSCRIPT.DRV file, that means, it needed to be stated as "\test\pscript\5470\pscript.drv", I simply left out the actual printer driver filename...duh....
OK, having overcome that obstacle I must report on some findings.
The as-is Brother PPD, where the print quality is left in the "Features" section does not appear to actually impact print quality in our OS/2 driver. So, in other words, when the default resolution is 600dpi, no matter what I select in the Features section of the driver I still ONLY get 600dpi output. Yeah...you bet, that's lousy!!!
So as it turns out the only way to make this work is by moving the whole Features print quality section over to the Output tab under Resolution. However, as I did that and as I preserved the Brother device controls I found out that the HQ1200 mode consistently crashes the driver. So whatever app I'm actually trying to print for, if I select HQ1200 Resolution the app will crash.
Since both 1200 and HQ1200 appear to be coded using the same HWResolution parameters but different statusdict settings it appears that I can only use the 1200dpi (highest-resolution) settings reliably.
*CAPT SFine/1200 dpi: "<</HWResolution [1200 1200] >> setpagedevice
statusdict/true1200 known{statusdict begin true true1200 end}if"
*CAPT Fine/HQ 1200: "<</HWResolution [1200 1200] >> setpagedevice
statusdict/true1200 known{statusdict begin false true1200 end}if"
Anyways...I will experiment with a few more configurations, but for now at least I have no way to understand why HQ1200 crashes the driver.