Thanks.
We have used sysdef 2.1 for the expansion of our existing sysdef which was
developed earlier in 1.1, than revised in 2.0 as our sysdef being a very large
contains more than 600 letterbugs it was not possible to start from scratch.
This was also analysed by Foxboro, experts from USA, and local office. We have
also tested this in our off-line set-up before committal.
Further to add in a problem, this printer (LP03) is configured as a back up
printer to process alarm printer (LP04) and by failing LP04 process alarms are
getting directed to LP03.
So the problem due to device monitor also is ruled out, We have also installed
QF for Device Monitor in all workstations.
What I believe is problem has to do some thing with the print service and
network port (tcp). Meaning some how print request from any of the workstation
is not getting accepted on network. I have checked the "tcp" port activity for
"lp" services on host AW & WPs and is showing ENABLED.
Best regards
Harshad
"Daren Bishop" <[EMAIL PROTECTED]> on 08/28/2001 09:30:43 PM
Please respond to "Foxboro DCS Mail List"
<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (bcc: Harshad Viradia/JAMNAGAR/RIL)
Subject: Re[2]: Dot Matrix Printer
Harshad,
Question: Did you use a newer or different version of SysDef to create
the new commit??
Answer: If so, it is always a good idea to rebuild the SysDef from
scratch when using a new version of Sysdef. I know this is a major
hassle, but I have had major "unexplainable" problems updating a
SysDef configuration with a newer version of SysDef.
Daren Bishop
ASC. Inc.
______________________________ Reply Separator _________________________________
Subject: Re: Dot Matrix Printer
Author: "Foxboro DCS Mail List" <[EMAIL PROTECTED]> at
INTERNET-MAIL
Date: 8/28/01 8:46 AM
Hi,
You might get some help from HH832 and HH843 on the Device Monitor. This has ca
used us problems before. Also there is good printer help on Angel Corbera's web
site: http://www.geocities.com/SiliconValley/Peaks/5825/contents.htm
Hope this helps.
Jim Kahlden
[EMAIL PROTECTED]
>>> [EMAIL PROTECTED] 08/28/01 05:20AM >>>
Hi all,
I am facing strange problem in one of the three dot matrix printers connected to
one COMM10.
Two printers are working normally meaning printing file, alarms etc.
One printer which is connected to first port is meant for system alarm messages
is not printing system alarms as well as text file. The printing of text file
from any of the workstations in the system is not working and while trying
giving error message "failed to open the printer port (transport endpoint not
connected)"
I have tried all possible ways like delete and adding again, reinstallation of
OS1CS, changing all the possible h/w and cables, but result is same.
This printer stopped working after recommittal of new sysdef.
We restored the recent dump tapes to our off-line set-up for further analysis
and found printer is working in off-line set-up (printing all system alarms,
files).
Same disks we took to on-line system and found that same printer is still not
working.
We have more than 30 dot matrix printers (all are replaced with Imac PCs) and
are working fine.
Are there anything more to try other than helpful hint #694 ?
Best regards
Harshad Viradia
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postingsfrom this list are the work of list subscribers and no warranty is made
or implied as to the accuracy of any information disseminated through this
medium. By su bscribing to this list you agree to hold the list sponsor(s)
blameless for any a nd all mishaps which might occur due to your application of
information receivedfrom this mailing list.
To be removed from this list, send mail to [EMAIL PROTECTED]
g
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
