LPR print problem

[Cojafoji]

So, we've been demoing this shitty print software where I work, and I've really just about had it. So, for reasons that are absofuckinglutely beyond me, these schmucks have seen fit to totally avoid designing a standard print server. So you know with a standard print server set up, you'd have a server, which listens for jobs sent from the client computers via installed lpr printers (sloppy definition, i know). Anyway, instead of doing that, they actually pause a printer, copy the spooler file from the client to the server, which can then release, cancel etc the job, just like any other server. When you go to print it, is uses the command "lpr -S 192.168.17.200 -P Raw "C:\folder\file.spl" to print the job. Problem is, half of the print jobs with spooler files > 5mbs print half of the job, and return a "failed to send to server message." Does the same thing on XP, Vista, and Win7. I don't have the knowledge to figure this out, and I figured one of you might.

[sleepy1212]

Idiotic printer settings are part of all workplaces. we're cursed with "local downlevel document" bullshit, or at least i have been ever since they sprang for a few new computers. All our files are located on a server along with all the printers, not sure how that works out. where are the drivers? could you load them on the desktop instead of the server and connect to the printer from there?

[Cojafoji]

where are the drivers? could you load them on the desktop instead of the server and connect to the printer from there?
Every client has the printer installed locally. Then the printer is paused, and when someone tries to print, it prompts them for their name and barcode and tells them it charges $.15 etc. After confirming that they in fact do want to print, the program copies the spooler file from C:\Windows\System32\spool\PRINTERS, to the server, where it is released/deleted by the management console. If it's released, it dumps the cost info via a sip2 server to a transaction db, then it prints the file via the command line with "lpr -S 192.168.17.200 -P Raw "C:\folder\file.spl".

Figured I'd explain it in better detail. Anyway, yeah, the drivers are all on the client, and the printer is also installed on the server as well. Why they didn't just set up a program that listen on the LPD port, and then release it, like a normal print server is beyond me. Fuck I'm rambling. Been a long day with too much coffee.