TJPing/TJPingPro FAQ
Q. Resetting the Graphical User Interface (GUI). I am using TJPingPro 2.0 or
TJPing 3.0, and they won't even start, or I need to reset the GUI and I can't
find the option to do so.
A. Try resetting the GUI with the GUI
Reset Utility
. First, close TJPingPro or TJPing. Run the GUI Reset utility, select either
TJPing or TJPingPro, and click the "Reset GUI" button. Then click the "OK"
button. Then restart TJPing or TJPingPro...your GUI should be reset.
Q. Accessibility. Are TJPing and TJPingPro compliant with Section 508?
A. Yes. TJPing and TJPingPro are compliant with Section 508.
Q. TJPing 2.0 crashes when trying to do
Lookups under Windows XP SP2.
A. This has been fixed for TJPing v. 3. For TJPing 2.0, if you
right click on the file tjping.exe in Windows Explorer, select the
"Compatibility" tab, and choose Windows 95/Windows ME, and hit OK, the program
should work w/o crashing.
Q: Are TJPingPro and TJPing Y2K compliant?
A: Yes! TJPing and TJPingPro are not reliant on dates for any of their
functionality, so they are not affected by the Y2K issue.
Q: Will TJPing or TJPingPro operate behind a proxy server or firewall?
A: Yes. However, your firewall must be set to allow ICMP traffic.
Q: How can I export my TJPingPro settings and host lists to another computer?
A: In TJPingPro 2.0 and TJPing 3.0, go to the "Other Options" tab. Click
the "Export Settings" buttons to create an export file. Click the "Import
Settings" buttons to import those settings. For earlier versions of
TJPingPro/TJPing, you'll need to export the Registry settings from the first computer and
merge the settings into the Registry on the second computer. See the TJPingPro Export page for more details.
Q: When I try to start TJPing, I get an 'Error starting program' error box saying :
"The TJPING.EXE file is linked to missing export OLEAUT32.DLL:420."
A: Your Automation libraries, including oleaut32.dll, are too old.
Download MSVBVM50.EXE from
the Microsoft Server and run it to update your libraries.
Q: I am not able to set the "Packet Data Size (bytes):" number in the
"Set Options" dialog box - the field is grayed out.
A: The "Packet Data Size (bytes):" number is tied to the
"Packet Data To Send:" data. You cannot change the packet size directly, it
changes automatically as you enter or remove data from the "Packet Data To
Send:" edit box.
Q: If my ICMP.DLL is not located in c:\windows\system (for instance, it's actually on
d:\windows\system) TJPing gives me an error message about not finding ICMP.DLL. What can I
do?
A: Put a copy of ICMP.DLL in the same directory that TJPing is in,
usually x:\Program Files\TJPing, where "x" is the drive letter. You may not be
able to copy ICMP.DLL while Windows is running. You can download a copy of it from the Top
Jimmy Homepage into your TJPing directory, if you don't want to shut down Windows to do
the ICMP.DLL copy.
Q: What is the "Don't Fragment" option. Why would I want to use it?
A: This option allows a user to specify that a packet be kept together
and not fragmented. Some people want this option so they can tell the maximum packet size
on a host they are pinging. However, if you specify this option, the total packet size
must be below the Maximum Transmission Unit (MTU) set for your computer. For Win 95 this
is usually 1500 bytes. If your packet size is larger than this, and you try to ping with
the "Don't Fragment" option set, you will get an error message telling you to
uncheck this option.
Note: With WinSock 1.1, if a lookup is done on a host, and
then one is done on a host with multiple IP addresses (such as www.microsoft.com), and
then a subsequent lookup is done on the first host again, the result will contain the
correct information, but also extra, erroneous IP addresses. This is a problem with the
way WinSock 1.1 buffers information, and is not a problem with TJPing. Everything works
correctly with v. 2.2 of wsock32.dll.
-Jim (May 20, 1997)
Back
Updated
March 18, 2011