If it doesn’t recognize the datastream as ASCII PCL, you can start the datastream with chr(27)+ "E".Īny Windows driver other than Generic Text Only in between, will mess thing up since the driver itself doesn’t expect, nor can handle ASCII data. If the printer receives the unmodified ASCII data, it should just work fine since the printer supports PCL directly. If another driver came with a list of different printer codes to use, that could be solution. Is there not a basic driver that will serve us? Installing a 64-bit driver on the server failed to allow Fox to recognize the printer at all, though I could print from a Windows Command window. Windows 7-32 has worked fine with the "HP LaseJet 8150 Series PCL6" driver, which is 32-bit, but the one compatible with Wndows 10 of the same name is 64-bit and would not install on the 32-bit Win 10 station. "HP Universal Print Driver for Windows PCL6 (32-bit)" seemed to reverse the cpi 10 and 12 output and did not print bold. I use fairly basic commands: Reset, Portrait/Landscape, 10cpi, 12 pci, Bold, 4/8 line feed, 7/8 line feed. The driver can be on either the server or the station. The printer is a networked LaserJet 8150N. Having upgraded from Win7-32 to Win10-32, I can no longer find a driver that properly formats the output. I am running a custom 16-bit FoxPro for DOS 2.6 application that sends old-style DOS/PCL printer control codes directly to the printer.
0 kommentar(er)
