/* --- Script © 2005 EC Software --- */ var ua = navigator.userAgent; var dom = (document.getElementById) ? true : false; var ie4 = (document.all && !dom) ? true : false; var ie5_5 = ((ua.indexOf("MSIE 5.5")>=0 || ua.indexOf("MSIE 6")>=0) && ua.indexOf("Opera")<0) ? true : false; var ns4 = (document.layers && !dom) ? true : false; var offsxy = 6; function hmshowPopup(e, txt, stick) { var tip = '

'+ txt + '<\/td><\/tr><\/table>'; var tooltip = atooltip(); e = e?e:window.event; var mx = ns4 ? e.PageX : e.clientX; var my = ns4 ? e.PageY : e.clientY; var bodyl = (window.pageXOffset) ? window.pageXOffset : document.body.scrollLeft; var bodyt = (window.pageYOffset) ? window.pageYOffset : document.body.scrollTop; var bodyw = (window.innerWidth) ? window.innerWidth : document.body.offsetWidth; if (ns4) { tooltip.document.write(tip); tooltip.document.close(); if ((mx + offsxy + bodyl + tooltip.width) > bodyw) { mx = bodyw - offsxy - bodyl - tooltip.width; if (mx < 0) mx = 0; } tooltip.left = mx + offsxy + bodyl; tooltip.top = my + offsxy + bodyt; } else { tooltip.innerHTML = tip; if (tooltip.offsetWidth) if ((mx + offsxy + bodyl + tooltip.offsetWidth) > bodyw) { mx = bodyw - offsxy - bodyl - tooltip.offsetWidth; if (mx < 0) mx = 0; } tooltip.style.left = (mx + offsxy + bodyl)+"px"; tooltip.style.top = (my + offsxy + bodyt)+"px"; if (ie5_5) { tooltip.style.filter = "progid:DXImageTransform.Microsoft.Shadow(color='B0B0B0', Direction=135, Strength=4)"; for (i = 0; i <= 0; i++) { tooltip.filters[i].Apply(); tooltip.filters[i].Play();} } } with(tooltip) { ns4 ? visibility="show" : style.visibility="visible" } if (stick) document.onmouseup = hmhidePopup; } function hmhidePopup() { var tooltip = atooltip(); ns4 ? tooltip.visibility="hide" : tooltip.style.visibility="hidden"; } function atooltip(){ return ns4 ? document.hmpopupDiv : ie4 ? document.all.hmpopupDiv : document.getElementById('hmpopupDiv') } popid_1656071030="

This help file is used for popup help only. There is no content in this help that can be browsed or searched.<\/p>\n\r

The HTML-based help file can be viewed by clicking here<\/a>.<\/p>\n\r" popid_1440920797X="

\n\r<\/p>\n\r

\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r

\$host<\/span><\/p>\n\r<\/td>\n\r	Host name (or IP address, if no name exists). <\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r
\$hostip<\/span><\/p>\n\r<\/td>\n\r	The host IP address<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r
\$hostdnsname<\/span><\/p>\n\r<\/td>\n\r	The resolved DNS name for the host<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r
\$year<\/span><\/p>\n\r<\/td>\n\r	Current Year<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r
\$month<\/span><\/p>\n\r<\/td>\n\r	Current Month<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r
\$day<\/span><\/p>\n\r<\/td>\n\r	Current day of month<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r
\$hour<\/span><\/p>\n\r<\/td>\n\r	Current hour<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r
\$minute<\/span><\/p>\n\r<\/td>\n\r	Current minute<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r
\$second<\/span><\/p>\n\r<\/td>\n\r	Current second<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r
\$date<\/span><\/p>\n\r<\/td>\n\r	Same as \$year-\$month-\$day.<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r
\$time<\/span><\/p>\n\r<\/td>\n\r	The same as \$hour\$minute - note the absence of any punctuation - that\'s to make sure the file name is valid, if this mask is being used in a file name.<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<\/table>\n\r<\/div>\n\r <\/div\n\r<\/p>\n\r" popid_158339515X=" Any alert can fire one or more \"Events\" based on the conditions of the alert. Each of these events have different parameters and options. The possible event types are: Send an email<\/a>, Play a sound<\/a>, Log to a file<\/a>, Change the tray icon<\/a>, and Launch an executable<\/a>.<\/span><\/p>\n\r" popid_1303430951X=" The alert name is used to identify the alert when attaching to a host. Make sure you name this something besides \"New Alert 7\" or it\'s going to be hard to figure out what it does later... :) Of course you can always change the name later, too...<\/span><\/p>\n\r" popid_1426687546X=" Select how many out of range samples you want to have to happen before the alert fires. Also, select here what \"out of range\" means. Note that a <\/span>timeout<\/span> is always out of range, so you can select any reasonably high number (ie: 9999) to mean timeouts.<\/span><\/p>\n\r" popid_364813200X=" This specifies the number of samples to examine. This does NOT have to match the \"number of samples to include\" from the main screen - so you can set up whatever conditions you want. Ping Plotter uses this number when determining if the alert should fire.<\/span><\/p>\n\r" popid_1918435608=" If you access the internet through a proxy server, you can set up this server here. This is used by MultiPing to check for new software versions, but setting this up isn<\/span>’<\/span>t required.<\/span><\/p>\n\r MultiPing functionality does not depend on the ability to access through a proxy server. These settings are used only for accessing <\/span>www.multiping.com<\/span> to check for version updates.<\/span><\/p>\n\r Any password you enter here is encrypted in the configuration file.<\/span><\/p>\n\r" popid_1484313155X=" Use the \"Enter New Target\" field to add a new ping target. <\/span><\/p>\n\r This field will accept entry in the form of an IP Address, or a name that can be resolved by your system. MultiPing ignores any protocol specifier, and any path information that you may enter, so just enter the domain name. Hit \"Enter\", or click the \"Add to Ping List\" button, to move this target to the active ping list.<\/span><\/p>\n\r You can also enter an IP Address followed by a friendlier name. MultiPing will use this name in all fields. Example:<\/span><\/p>\n\r 192.168.10.223 My Server Name<\/span><\/p>\n\r MultiPing will then use \"My Server Name\" as the DNS Name for this IP.<\/span><\/p>\n\r" popid_826819508X=" The \"Load from file\" area allows you to pick from several files formats to load.<\/span><\/p>\n\r Any file that is loaded will be listed in history here to make it easy to act on these files again later.<\/span><\/p>\n\r Double-click the \"Browse for file…\" entry to open a file open dialog, or double-click on file name to load that file.<\/span><\/p>\n\r You can right-click on a file to delete it from the list, or move the lists of targets from that file into the \"target list history window\" by double-clicking it.<\/span><\/p>\n\r For more details about valid files to load, see the \"Loading targets from a file\" help topic.<\/span><\/p>\n\r" popid_1916557361X=" The Ping Interval is the amount of time MultiPing will wait between each ping <\/span>set<\/span>. All targets are pinged at this interval (separated by a tiny bit of time so the pings don<\/span>’<\/span>t impact each other).<\/span><\/p>\n\r If you\'re doing a long term monitoring project, you may want to set this to 1 minute (you can set it for more if you like). If you\'re just doing a quick set, you might want to set this to something lower (1, 5, or 10 seconds). If the up\/down arrow doesn\'t have the unit of time you want, just type in the time interval you want (e.g. 3.5 seconds, or 0.10 seconds).<\/span><\/p>\n\r" popid_1303236156X=" The \"Samples to include\" setting sets the number of samples that are used in the upper graph<\/span>’<\/span>s numbers (average, min\/max, packet loss, etc.). This allows you to see current trending information (i.e.: last 10 samples or all the samples since you started collecting data). Using \"0\" in this field means you want to include \"ALL\" samples.<\/span><\/p>\n\r This is an important setting for analyzing historical information as well, because you can focus the upper graph on a period of time by double-clicking that time period in one of the timeline graphs. If you have this set to \"ALL\", then you won<\/span>’<\/span>t be able to zoom in the time-graph, so it<\/span>’<\/span>s important to have this set to a reasonable number when looking back in history.<\/span><\/p>\n\r" popid_429658019X=" The \"History\" panel lists all the targets you<\/span>’<\/span>ve manually entered addresses for in the order in which you<\/span>’<\/span>ve entered them. The newest entries go on the top of the list.<\/span><\/p>\n\r You can remove entries from the history window by right-clicking and \"Deleting from history\", or sort the list alphabetically by right-clicking and selecting that option from the menu. Note that all sorting is alphabetical – even if you<\/span>’<\/span>ve entered IP Addresses – so IP Addresses will sort alphabetically, rather than numerically, in this list.<\/span><\/p>\n\r" popid_1636402584X=" This controls the display of the legend on the main screen (Green \/ Yellow \/ Red). If there isn<\/span>’<\/span>t enough room to display the legend, then the legend will automatically turn off so it doesn<\/span>’<\/span>t obscure the settings available there (Ping Interval, Samples to Include).<\/span><\/p>\n\r" popid_639661115X=" These boxes control the point at which the colors change. By default, all response 200 ms and below will paint green. From 201 to 500 will paint yellow, and over 500 will paint red. These numbers apply to both the left graph column and also the graph background. In addition, the legend on the graph screen will be updated with these numbers.<\/span><\/p>\n\r You\'ll probably want to change the numbers based on your internet connection speed. If you have a T1 or a cable modem, the listed numbers are probably pretty good (you might move them down a little if you\'re pinging a bunch of fast sites). If you have a modem, you probably want to crank these numbers up a bit.<\/span><\/p>\n\r A reasonable number for a modem would be 350 for Warning and 600 for Critical. You might want to play around a little with these, though.<\/span><\/p>\n\r" popid_1920570605X=" The blue X on the upper graph shows the current (or most recent) sample taken. You can decide to turn this setting on or off using the setting in the options screen, or by right-clicking the upper graph and turning off this option.<\/span><\/p>\n\r" popid_935485558X=" It<\/span>’<\/span>s often helpful to see the range of latencies you<\/span>’<\/span>ve received for a specific target. The Min\/Max line shows this range on the graph. While this is very helpful much of the time, occasionally it skews the range of the graph (especially when you get high response times just occasionally). Remember that the \"Samples to Include\" setting on the main screen controls the range of samples that is used for this setting – the Min\/Max values are only pulled from the number of samples in \"Samples to Include\".<\/span><\/p>\n\r" popid_1454337058=" By default, MultiPing will automatically adjust the scale of the graphs to fit the data you are collecting. Sometimes, if one of the targets in your trace has really bad performance, this can cause the graph to become almost unreadable. If this happens, you can fix the scale of the graph so it doesn\'t change. All graphs are affected by this setting – the upper graph, the lower (docked) time graphs, and the floating time graphs.<\/span><\/p>\n\r Note that any time graphs might use Pixel Averaging – which might affect the scale used.<\/span><\/p>\n\r" popid_1611404903X=" The red number on the right of each timeline graph is the scale of the packet loss numbers. This setting modifies that scale, which is used on all the graphs (upper graph and all time graphs), or removes the scale (which also stops graphing of packet loss).<\/span><\/p>\n\r Floating graphs can also have the scale removed while still graphing the packet loss. Go to the <\/span>floating graph view options<\/a><\/span> to change this setting.<\/span><\/p>\n\r Note that any time graph might use Pixel Averaging, which might affect the packet loss percentage shown.<\/span><\/p>\n\r" popid_1247796077X=" Normally, you want to have MultiPing automatically start pinging as soon as you add a target. If you want to have to manually hit the \"Start\" button before pinging begins, turn this option off.<\/span><\/p>\n\r" popid_880051617X=" This adjusts the size of the packet that MultiPing sends out to each destination. Packet size and latency have a very direct relationship, so be careful about making this too big. Sometimes routers will have problems with packets of a certain size, so you can manipulate this setting to help with those.<\/span><\/p>\n\r Having this number too high will HUGELY affect your performance. It\'s best to leave this pretty small. Valid ranges are from 10-512 bytes. Actually, anything up to 32K will be accepted, but using a packet size over 512 bytes is just asking for trouble Packets will fragment, which makes the latency number pretty meaningless).<\/span><\/p>\n\r" popid_2113552903X=" This option allows you to fine-tune your performance a little. By default, MultiPing will wait for 10 seconds (9999 ms) for any packet to return. If the packet doesn\'t return by then, it is counted as a lost packet. If patience isn\'t one of your virtues, you can turn this down somewhat.<\/span><\/p>\n\r Because of the performance enhancements offered by MultiPing, it\'s unlikely that this option needs to be changed. If it\'s set too low, it can cause misleading data to be generated. For best results, leave this at 9999.<\/span><\/p>\n\r One case where you might want to lower this number is if you<\/span>’<\/span>re running a <\/span>really<\/span> aggressive Ping Interval. In most cases, you probably don<\/span>’<\/span>t want your Timeout interval to exceed your trace interval.<\/span><\/p>\n\r Another case where you might want to lower this is if you occasionally get really high pings that throw off your graph scale. It might be better to count these as timeouts.<\/span><\/p>\n\r" popid_913912618X=" This can be an interesting number to manipulate. It\'s really meant for \"advanced\" users, so you don\'t NEED to change it.<\/span><\/p>\n\r MultiPing sends out each packet independently, not waiting for previous packets to return. This gives consistent timing, and means response times can be compared relatively well. All targets are added to the queue at the same time, and then a delay is introduced between each outgoing packet. This makes sure your connection isn<\/span>’<\/span>t saturated by MultiPing when you<\/span>’<\/span>re monitoring 50 targets.<\/span><\/p>\n\r This time interval is adjusted by this parameter. Most of the time, the default of 50 ms is more than adequate. This falls within the realm of what a 28.8 modem can easily handle. If you\'ve adjusted your packet size, or your connection to the internet is really slow, you might want to crank this number up a little. <\/span><\/p>\n\r If you have an excessive amount of bandwidth, you can crank it down a little. Be aware that to small of a number can adversely affect your data because each packet takes a bit of bandwidth. You need to make sure there is enough time for a packet to be completely sent before sending the next one.<\/span><\/p>\n\r" popid_697117985=" This is the maximum number of samples that will be held in memory at any one time. Older samples are purged from memory as the sample count exceeds the number of samples you specify here.<\/span><\/p>\n\r MultiPing uses 8 bytes of memory for each sample set, no matter how many targets. This is used to store the date and the time of the sample plus 2 bytes for each target you are pinging. This means 10 targets take 28 bytes per set, so holding 100,000 samples takes 2,800,000 bytes (or 2.8 megs) of RAM. In reality, this is the minimum. There is some additional dynamic working memory needed, but this gives you an idea of how much memory is in use, which is relatively little actually.<\/span><\/p>\n\r" popid_60772937=" Show the MultiPing icon in the tool tray. Also, minimize to the tray rather than the taskbar. If you have an alert event to change the tool tray icon, MultiPing might show up in the tray even with this option disabled.<\/p>\n\r" popid_1282987985X=" Hitting the \"X\" button on the upper right often closes an application. If you\'re collecting data, though, you might not want this behavior. Use this option to change what happens.<\/p>\n\r"