I cannot really quantify, but it seems to me that since UL went to .NET-based server tools, I have seen much more error messages, and longer response periods.
Cannot provide any insight into the stack trace (error) messages that the UL site frequently emits (no longer do corporate windoze development). Perhaps this would be a good time for their web developers to read UL 1998 and IEC 61508 -- if a product safety engineer is dependent on their software, then it is safety-critical code (he said ducking and running). luck, Brian From: [email protected] [mailto:[email protected]]On Behalf Of Georgerian, Richard Sent: Wednesday, September 06, 2006 2:10 PM To: McInturff Gary Cc: [email protected] Subject: RE: [EMC-PSTC] UL wire styles Gary, This is the link to the UL wire style page: http://database.ul.com/cgi-bin/XYV/template/LISEXT/1FRAME/cawmsrch.html Best regards, Richard ===== Richard Georgerian Carrier Access Compliance Engineer 5395 Pearl Parkway Boulder, CO 80301 U.S.A. email: mailto:[email protected] tel: 303-218-5748 fax: 303-218-5503 ________________________________ From: McInturff Gary [mailto:[email protected]] Sent: Wednesday, September 06, 2006 2:57 PM To: [email protected] Subject: [EMC-PSTC] UL wire styles Where the heck did they put the descriptive breakdown of the wire styles. I was just trying the online directory but it is running at a snail's pace? - This message is from the IEEE Product Safety Engineering Society emc-pstc discussion list. Website: http://www.ieee-pses.org/ To post a message to the list, send your e-mail to [email protected] Instructions: http://listserv.ieee.org/request/user-guide.html List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the list administrators: Scott Douglas [email protected] Mike Cantwell [email protected] For policy questions, send mail to: Jim Bacher: [email protected] David Heald: [email protected] All emc-pstc postings are archived and searchable on the web at: http://www.ieeecommunities.org/emc-pstc ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
