Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
Moderator: | NETCAD::COLELLA DT |
Created: | Wed Nov 13 1991 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4455 |
Total number of notes: | 16761 |
Hi, My customer has a problem using the PacketProbe90 (V2.7) with the "Traffic Monitor" of ProbeWatch (3.3.0. Serial#0): If he starts the traffic monitor he gets an error "Floting point error: invalid" and you have to close the window. It has been seen with WNT 3.51, WNT4.0 and ClearVISN 1 and 1.1a (although ProbeWatch is allways 3.3.0) The problem occurs at an estimated failure rate of 80% on PacketProbes that have a long uptime, i.e. 7 days is o.k. but 97 days and more exhibit the problem. Is anything known ? Will this be fixed with the next release of PacketProbe/ProbeWatch ? Thomas
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
4444.1 | Me too (Floating point error) | ROM01::GALLANA | Francesco Gallana | Thu May 29 1997 12:38 | 7 |
Hello, I have the same problem.. WNT Worstation V4.0 and RMON manager V3.3.0 No problems with W95 Francesco | |||||
4444.2 | This is a known problem | NNTPD::"[email protected]" | Kerr Glen | Mon Jun 02 1997 13:20 | 12 |
This is a known problem. We have had many customers reporting this problem to us. The TAC case number is N13491. We have been pushing Engineering for a fix now for a while, because a Third party, Frontier, write the software they appear to having some problems in getting a fix. Will post another note if we ever get anywhere. Kerr Glen NPB Technical Support. [Posted by WWW Notes gateway] |