That will let me capture it as I asked, but I'm still looking for a bit broader answer. Sorry Foulc your answer is a little vague, are you saying that as a capture setting.Īs in the windows printer port to file: instead of lpt1: Any other driver I can get? Patch? redirection program? It seems to be a driver or software problem not with the DOS program, (since it will print from all the workstations if physically connected to the server.) But more so the intervention of the Win98 driver. The Hardware on the NT server is identical to that of the Win98 workstation. It's almost as though whatever it sends to initialize the printer freezes it, then by turning it off you are resetting it, and when turned back on it receives the DATA as though nothing were wrong.But what is wrong? The DOS program is set up to send an ESCape sequence to initialize the printer (27, 120, 48) I think.
But when you print from the DOS program it doesn't do anything, the printer light goes off, and the print cue says there are 17 bytes printing (which is about all the print job is.) If you turn the printer off and on again it prints that print job, but then the same thing happens if you print again.
This works fine, but when the client moves to the new building they need the Printer (LX300) connected to one of the workstations and shared from there. Which at this time is physically connected to the Server, shared and captured to all the workstations LPT2. The problem is that the program prints to two different printers, HP 2100 on LPT1 (physically on one computer, and captured to the network path on the others). I am doing a job for one of my clients, they use a DOS based program on a LAN, I have changed the LAN freom being NOVELL 3.12 with diskless DOS workstations,to NT 4.0 and Win98 workstations.
0 kommentar(er)
