My sentiments exactly. It's the same as how Windows users tolerate rebooting all the time (we've all seen the analogy of PCs to automobiles basically underscoring how much more crap we put up with from the former). I don't have 8.6, nor have I read that HH. But for better or worse on the Windows platform, the I/A core is still largely based on Unix. Which means of course it's hackable :) It should be straightforward to write a program in VB or whatever to monitor /usr/tmp for files that look like *print and send them to the default printer. As Andreas said, the /etc/printers file is sensitive (from some aforementioned hacking I have it documented for my personal use somewhere). One thing I've done lately that made printing more reliable (on Unix) is limit the printer names to 5 characters; even though it will appear to work with six, I had occasional prints showing up on the other side of the wormhole until I made them all 5 characters or less. Corey From: "Easley, Jack" <Jack.Easley@xxxxxxxxxxxx> To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx> Date: 10/11/2011 07:59 AM Subject: Re: [foxboro] printing from ICC (windows) Sent by: foxboro-bounce@xxxxxxxxxxxxx Many years of living with "This product enhancement (ie bug) will be fixed by upgrading to Fox Version 9999.9999" have made many of us submissive, I mean tolerant. Boy, did I ever wake up on the cynical side of the bed this morning! In reality Fox is good at controlling the process and is very complex software. Just wish sometimes we could get a better response to minor bug fixes). Jack Easley Sr. I&C Technician Luminant Power, Martin Lake Plant Phone 903.836.6290 jack.easley@xxxxxxxxxxxx -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of andreas.weiss@xxxxxxxxx Sent: Tuesday, October 11, 2011 7:20 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] printing from ICC (windows) Hi, thanks a lot for the hint with the ascii file. It is really impressive how tolerant I/A users are ... They accept it to loose a build in function like print. I still hope on a solution because my users do not accept the described way with printing manually /usr/temp/<letterbug>print. Regards, Andreas _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave